You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Matthew Beermann (JIRA)" <ji...@codehaus.org> on 2007/01/25 00:00:26 UTC
[jira] Created: (MNG-2792) When Maven runs Java 6,
maven-metadata.xml file is "corrupted"
When Maven runs Java 6, maven-metadata.xml file is "corrupted"
--------------------------------------------------------------
Key: MNG-2792
URL: http://jira.codehaus.org/browse/MNG-2792
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 2.0.4
Reporter: Matthew Beermann
Priority: Critical
Attachments: maven-metadata.xml
When you run Maven under Java 6, the "maven-metadata.xml" file that gets written to the remote repository is markedly different from the one generated under Java 5 and earlier. This file is "corrupted" in the sense that Maven reports errors about it, and might not be able to locate snapshots as a result. See attachment for an example file; you'd expect to see build numbers or -SNAPSHOTs, but not both at once.
This issue is described further at http://www.nabble.com/Maven-and-JDK-1.6-t3060866s177.html (originally message only, not the followups). This might be related to MNG-2709, but I don't think it's a duplicate, as it has nothing to do with testing or parents.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2792) When Maven runs Java 6,
maven-metadata.xml file is "corrupted"
Posted by "Jeremy Norris (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88932 ]
Jeremy Norris commented on MNG-2792:
------------------------------------
Are there any workarounds for this without reverting to java 5?
> When Maven runs Java 6, maven-metadata.xml file is "corrupted"
> --------------------------------------------------------------
>
> Key: MNG-2792
> URL: http://jira.codehaus.org/browse/MNG-2792
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Matthew Beermann
> Priority: Critical
> Attachments: maven-metadata.xml
>
>
> When you run Maven under Java 6, the "maven-metadata.xml" file that gets written to the remote repository is markedly different from the one generated under Java 5 and earlier. This file is "corrupted" in the sense that Maven reports errors about it, and might not be able to locate snapshots as a result. See attachment for an example file; you'd expect to see build numbers or -SNAPSHOTs, but not both at once.
> This issue is described further at http://www.nabble.com/Maven-and-JDK-1.6-t3060866s177.html (originally message only, not the followups). This might be related to MNG-2709, but I don't think it's a duplicate, as it has nothing to do with testing or parents.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2792) When Maven runs Java 6,
maven-metadata.xml file is "corrupted"
Posted by "Matthew Beermann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86001 ]
Matthew Beermann commented on MNG-2792:
---------------------------------------
Daniel Kulp adds:
No. It's really not corrupted despite the error. I've been tracing through
the maven code and there are a series of "transforms" (not xml transforms)
that an artifact goes through to be resolved. With Java 5, the order is:
org.apache.maven.artifact.transform.LatestArtifactTransformation
org.apache.maven.artifact.transform.ReleaseArtifactTransformation
org.apache.maven.artifact.transform.SnapshotTransformation
but with Java 6, for some reason, the order is:
org.apache.maven.artifact.transform.SnapshotTransformation
org.apache.maven.artifact.transform.LatestArtifactTransformation
org.apache.maven.artifact.transform.ReleaseArtifactTransformation
The LatestArtifactTransform is what uses to the metadata to determine
the "actual" version number (for the install plugin, 2.2-SNAPSHOT). The
SnapshotTransform then converts that to 2.2-20061118.060401-2 which is what
is then downloaded. However, in the java 6 case, the SnapshotTransform is
run first and since the version is not a "SNAPSHOT" version number, it
doesn't do any processing so then the downloading ends up looking for
2.2-SNAPSHOT, not the full version, which then fails.
I'm not sure why the order of the transforms is different yet.
Dan
> When Maven runs Java 6, maven-metadata.xml file is "corrupted"
> --------------------------------------------------------------
>
> Key: MNG-2792
> URL: http://jira.codehaus.org/browse/MNG-2792
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Matthew Beermann
> Priority: Critical
> Attachments: maven-metadata.xml
>
>
> When you run Maven under Java 6, the "maven-metadata.xml" file that gets written to the remote repository is markedly different from the one generated under Java 5 and earlier. This file is "corrupted" in the sense that Maven reports errors about it, and might not be able to locate snapshots as a result. See attachment for an example file; you'd expect to see build numbers or -SNAPSHOTs, but not both at once.
> This issue is described further at http://www.nabble.com/Maven-and-JDK-1.6-t3060866s177.html (originally message only, not the followups). This might be related to MNG-2709, but I don't think it's a duplicate, as it has nothing to do with testing or parents.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2792) When Maven runs Java 6,
maven-metadata.xml file is "corrupted"
Posted by "Matthew Beermann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew Beermann closed MNG-2792.
---------------------------------
Resolution: Duplicate
Fix Version/s: 2.0.6
Duplicate of MNG-2793.
> When Maven runs Java 6, maven-metadata.xml file is "corrupted"
> --------------------------------------------------------------
>
> Key: MNG-2792
> URL: http://jira.codehaus.org/browse/MNG-2792
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Matthew Beermann
> Priority: Critical
> Fix For: 2.0.6
>
> Attachments: maven-metadata.xml
>
>
> When you run Maven under Java 6, the "maven-metadata.xml" file that gets written to the remote repository is markedly different from the one generated under Java 5 and earlier. This file is "corrupted" in the sense that Maven reports errors about it, and might not be able to locate snapshots as a result. See attachment for an example file; you'd expect to see build numbers or -SNAPSHOTs, but not both at once.
> This issue is described further at http://www.nabble.com/Maven-and-JDK-1.6-t3060866s177.html (originally message only, not the followups). This might be related to MNG-2709, but I don't think it's a duplicate, as it has nothing to do with testing or parents.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira