DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to. DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued
Issue Details (XML | Word | Printable)

Type: Bug Bug
Status: Closed Closed
Resolution: Won't Fix
Priority: Major Major
Assignee: Unassigned
Reporter: Chris
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
DataNucleus Tools : Maven plugin

Maven build failure, missing dependency javax.jdo:jdo-api:jar:3.1-SNAPSHOT-20110926

Created: 28/Feb/12 04:29 PM   Updated: 14/Jun/12 01:28 PM   Resolved: 01/Mar/12 04:55 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

VM with SL5 x86_64
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_29

Severity: Production

 Description  « Hide
You have for org.datanucleus:maven-datanucleus-plugin:maven-plugin:2.2.1 a dependency on the latest jdo-api.

cat ~/.m2/repository/org/datanucleus/maven-datanucleus-plugin/2.2.1/maven-datanucleus-plugin-2.2.1.pom

            <version>[3.0, )</version>



We get when building:
========Maven build error========================

[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

1) javax.jdo:jdo-api:jar:3.1-SNAPSHOT-20110926

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=javax.jdo -DartifactId=jdo-api -Dversion=3.1-SNAPSHOT-20110926 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=javax.jdo -DartifactId=jdo-api -Dversion=3.1-SNAPSHOT-20110926 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
   1) org.datanucleus:maven-datanucleus-plugin:maven-plugin:2.2.1
   2) javax.jdo:jdo-api:jar:3.1-SNAPSHOT-20110926

1 required artifact is missing.

for artifact:

from the specified remote repositories: (,
  central (,
  DN_M2_Repo (,
  freehep-maven (,
  dcache.repository (

===End=====Maven build error========================

While the has:
[ ] jdo-api-3.1-SNAPSHOT-20110926.jar 27-Sep-2011 19:41 204K
[ ] jdo-api-3.1-SNAPSHOT-20110926.pom 27-Sep-2011 19:41 5.6K

We are building against a tag which should prevent using SNAPSHOT version of dependencies, but still it is trying to pull a snapshot.
The same problem is described somewhere else: and was fixed on there side. So maybe it is fixable on our side, but I can not find how. Please help in this case

I see the problem in the version interval definition and the fact that we have no control
            !!!!! <version>[3.0, )</version> !!!!!!

I must admit, I do not completely understand what exactly the problem is, but this is my interpretation:
Since I am building against a tag, there should be no use of snapshots anywhere. This is a fact.

Question1: Why is it still pulling snapshots? This might then be a problem on our side, which I could not identify or on your side that the repo contains snapshots and I do not have control over what is pulled as a dependency on your side.

Question2: It is trying to pull a snapshot jar that is there, but is not able to download it, which is strange.

Kind regards. Christian

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 28/Feb/12 04:59 PM
Presumably Maven, being decidedly substandard wrt separating SNAPSHOT and other artifacts, has a problem with SNAPSHOT jars being in the DN repo (even though they are all referenced in all of the necessary files). The problem stems from Apache JDO being incredibly slow at doing releases, hence we have to provide snapshots of JDO jars. You could easily restrict the jdo-api jar to 3.0.1 if you don't want SNAPSHOTs.

Chris added a comment - 01/Mar/12 04:39 PM
Hi Andy,

thank you for the quick response. Adding the static dependency to our pom.xml actually solved the issue for us. I post the whole plugin conf for others to be quicker at solving such an issue than I was.

Thanks again. Christian