You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2008/11/18 18:15:44 UTC

[jira] Reopened: (GERONIMO-4417) Enhance manifest classpath generation in ArchiveCarMojo

     [ https://issues.apache.org/jira/browse/GERONIMO-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks reopened GERONIMO-4417:
------------------------------------


I think this is a very bad idea as it lets the details of our particular repository layout leak into plugins.  I am -1 on this at least without some very strong justification well beyond convenience.

> Enhance manifest classpath generation in ArchiveCarMojo
> -------------------------------------------------------
>
>                 Key: GERONIMO-4417
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4417
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: car-maven-plugin
>    Affects Versions: 2.2
>            Reporter: Jarek Gawor
>            Assignee: Jarek Gawor
>             Fix For: 2.2
>
>
> Add an option to ArchiveCarMojo to automatically generate classpath entries in the manifest file so that it uses the jar files under the "repository" directory of Geronimo installation. Right now, the jar file locations can be specified in the <classpath> entry but that is hard to maintain. With these feature, the jar file locations would be automatically generated (if enabled). Also, with this feature we should be able to get rid off some of the duplicated jar files under the "lib" directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.