[
https://issues.apache.org/jira/browse/MSHARED-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSHARED-190:
-----------------------------------
Labels: close-pending (was: )
> More flexible manifest classpath
> --------------------------------
>
> Key: MSHARED-190
> URL: https://issues.apache.org/jira/browse/MSHARED-190
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-archiver
> Affects Versions: maven-archiver-2.4.1
> Reporter: Yves Langisch
> Labels: close-pending
> Attachments: third_party_classpathPrefix.patch
>
>
> I'd like to see a more flexible way to adjust the classpath entries in the
> manifest file. For example with the ear-plugin I'm able to put third party
> libraries to a different folder (e.g. lib/) than project module artifacts
> (e.g. root folder). For ejb-modules I need to be able to specify classpath
> entries for both folders (e.g. lib/log4j.jar and a.b.c.project-common.jar).
> As you can only specify a general prefix this layout is currently not handled.
> Attached you find a patch against the trunk which introduces a new additional
> configuration option {{classpathPrefixThirdParty}}. Dependencies that have a
> different groupId from the project itself are prefixed with that option.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
