[
http://jira.codehaus.org/browse/MNG-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=182102#action_182102
]
Benjamin Bentmann commented on MNG-4225:
----------------------------------------
bq. Why do we see different behaviour between Different JDK vendors?
I repeat: "The activators are looked up from the Plexus container with a
non-deterministic order." And before MNG-3106, the activation of a profile was
sensitive to the order of the activators. That it works with IBM JDK 1.5 SR4
and Sun JDK 1.6 is a mere coincident.
> Plugin dependencies are incorrectly included as needed artifacts in IBM JDK
> 1.5 sr8 and IBM JDK 1.6
> ----------------------------------------------------------------------------------------------------
>
> Key: MNG-4225
> URL: http://jira.codehaus.org/browse/MNG-4225
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.9
> Environment: OS : Windows Server 2003
> JDK: IBM JDK 1.5 sr8 edition and IBM JDK 1.6
> Reporter: Baback Nemazie
> Priority: Blocker
> Attachments: JavaMavenTest.zip
>
>
> We have been using a "parent pom" that specifies the plugin dependencies for
> our projects. This parent pom has been in use for more than a year. We have
> been using IBM JDK 1.5 sr4 until recently, and we had no problems building
> the parent pom. However for the upcoming release we upgraded to IBM JDK 1.5
> sr8. Upon upgrade to the sr8 edition, when we tried to build the parent pom,
> the build process incorrectly tried to search for specified plugin
> dependencies, and since these specified plugin dependencies are built AFTER
> the parent pom is built the build process fails with the error message that
> it could not find the plugin-dependencies in order to proceed with building
> the parent pom.
> We encountered the same issue with IBM JDK 1.6 as well. Since many of the
> developers who use our product will be using IBM JDK 1.6, we need to resolve
> this issue for both IBM JDK1.5 sr8 and IBM JDK 1.6.
> We did NOT encounter this issue with the Sun JDK 1.6. This led us to approach
> IBM to investigate the issue as it appeared that this maybe an IBM JDK
> specific issue. We sent our test case to them, and they reported to us that
> suspect that maven code could be depending on the hashmap ordering, which is
> breaking the dependency check.
> They instructed us to post this issue to the maven issue tracking and they
> will follow up with the maven folks.
> Attached is the test case to reproduce the problem. Please read the file
> how_to_reproduce.txt in the attached. IBM folks will provide you with the
> needed JDK's.
--
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
