Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: maven-archiver-2.4
-
Component/s: maven-archiver
-
Labels:None
-
Number of attachments :
Description
i followed manifest-customation as explained in:
http://maven.apache.org/shared/maven-archiver/index.html
what i really miss, is to configure the classpath pattern of the dependency jar-names. the only customization of classpath entries is possible by setting the classpath prefix (<addClasspath>) and (<classpathMavenRepositoryLayout/>). unfortunately it is not possible to set the jar-name pattern itself.
to avoid library name-clashes we got pattern $groupId-$artifactId-$version for jars which are put besides the main-jar. by default maven-archiver only sets $artifactId-$version. so it would be nice to have a possible configuration like <jarPattern> or similar inside maven archive-configuration .
Issue Links
| This issue relates to: | ||||
| MJAR-28 | Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions |
|
|
|
| This issue is depended upon by: | ||||
| MASSEMBLY-211 | assembly plugin and jar plugin disagree about whether to use uniqueVersion snapshot names |
|
|
|
Deprecated <classpathMavenRepositoryLayout> in favor of new <classpathLayoutType>, which uses a value of 'repository' to mimick the <classpathMavenRepositoryLayout>true</classpathMavenRepositoryLayout> setting. For a custom layout, try:
The configuration for this should show up in the classpath examples page on the maven-archiver website once the release is done.