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/06/13 03:36:12 UTC

[jira] Updated: (MNG-3516) Make dependencies on javaee artifacts such as war, ear, rar get the contents into the classpath.

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

Brett Porter updated MNG-3516:
------------------------------

    Fix Version/s: 2.x

> Make dependencies on javaee artifacts such as war, ear, rar get the contents into the classpath.
> ------------------------------------------------------------------------------------------------
>
>                 Key: MNG-3516
>                 URL: http://jira.codehaus.org/browse/MNG-3516
>             Project: Maven 2
>          Issue Type: New Feature
>            Reporter: David Jencks
>             Fix For: 2.x
>
>
> Some javaee servers such as geronimo and IIRC jboss let you construct classloader hierarchies where the classes from one javaee app can be available in another javaee app's classloader.  Maven ought to be able to support stuff like this by having a more flexible model of how to get the classes from something more complicated than a jar into a classpath.
> This is most important for war files where the WEB-INF/classes directory generally contains stuff that won't be available anywhere else in a maven repo.  For ear libs and rars presumably the contents are available as independent artifacts in a repo.

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