Maven Shared Components

Customization of jar-name pattern of classpath-entries inside MANIFEST.MF

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: maven-archiver-2.4
  • Component/s: maven-archiver
  • Labels:
    None
  • Number of attachments :
    0

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

is depended upon by

Bug - A problem which impairs or prevents the functions of the product. MASSEMBLY-211 assembly plugin and jar plugin disagree about whether to use uniqueVersion snapshot names

  • Blocker - Blocks development and/or testing work, production could not run
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. MJAR-28 Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Hide
Permalink
John Casey added a comment -

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:

<classpathLayoutType>custom</classpathLayoutType>
<customClasspathLayout>${artifact.artifactId}-${artifact.baseVersion}${dashClassifier?}.${artifact.extension}</customClasspathLayout>

The configuration for this should show up in the classpath examples page on the maven-archiver website once the release is done.

Show
John Casey added a comment - 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: <classpathLayoutType> custom </classpathLayoutType> <customClasspathLayout> ${artifact.artifactId}-${artifact.baseVersion}${dashClassifier?}.${artifact.extension} </customClasspathLayout> The configuration for this should show up in the classpath examples page on the maven-archiver website once the release is done.

People

  • Assignee:
    John Casey
    Reporter:
    manuel aldana
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: