[jira] Commented: (MNG-1412) dependency sorting in classpath

["nicolas de loof (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117443 ] 

nicolas de loof commented on MNG-1412:
--------------------------------------

I can understand this classpath ordering requirement for a command line application point of view, where the classpath variable is under control, but what in a JEE context where all jars are put in WEB-INF/lib and not ordering can be specified ?

Having a project to depend on classpath ordering is simply a nonsense for me. This sounds like a hack to bypass some architecture issues.

You have multiple log4j.properties in classpath ? Having multiple result for a resource lookup is a valid Java case (@see Classloader.getResources()) but IS NOT supported by log4j !

 - Why do those jars have a log4j.properties if they are not runnable artifacts ?
 - Why not setup log4j programmatically or using -Dlog4j.configuration ?

for testing purpose, the taget/classes and taget/test-classes are set prior to dependencies in classpath, like the WEB-INF/classes is on a JEE webapp.

You need to patch some 3d party jar ? Create a new project, use the dependency plugin to unpack it, add your custom patched classes and package your own modified artifact !



> dependency sorting in classpath
> -------------------------------
>
>                 Key: MNG-1412
>                 URL: http://jira.codehaus.org/browse/MNG-1412
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0
>            Reporter: Mark Hobson
>            Assignee: fabrizio giustina
>             Fix For: 2.1
>
>         Attachments: artifact-order_maven-artifact-manager.txt, artifact-order_maven-artifact.txt, artifact-order_maven-project.txt, MNG-1412-maven-2.0.x-r507746.patch
>
>
> The .classpath file entries should be ordered by nearest transitiveness (if that's a word).
> For example, I have project A that depends on B that depends on C.  The classpath for A is generated in the order C, B.  Ideally the classpath should be in order of how near they are to the project, i.e. B, C.

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