You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/10/29 09:09:51 UTC

[jira] Closed: (MNG-3805) Ordering of extension class path is indeterministic

     [ http://jira.codehaus.org/browse/MNG-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MNG-3805.
-----------------------------

         Assignee: Brett Porter
       Resolution: Fixed
    Fix Version/s: 2.0.10

Applied and re-instated the IT

> Ordering of extension class path is indeterministic
> ---------------------------------------------------
>
>                 Key: MNG-3805
>                 URL: http://jira.codehaus.org/browse/MNG-3805
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies
>    Affects Versions: 2.0.9, 2.1.0-M1
>            Reporter: Benjamin Bentmann
>            Assignee: Brett Porter
>             Fix For: 2.0.10
>
>         Attachments: deterministic-dependency-ordering.patch, log-bad.txt, log-good.txt
>
>
> One part of Maven where class path ordering hasn't already been fixed in the past is the extension class path. Apart from a proposed patch, two logs from our IT testmng3599useHttpProxyForWebDAV are attached. Both were run against Maven 2.0.10-RC1, with the only difference being one using JDK 1.4 and the other one 1.6. Not only do these logs substantially differ, the build on JDK 1.6 even fails due to picking up the wrong extension classes.

-- 
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