You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "manuel aldana (JIRA)" <ji...@codehaus.org> on 2008/05/14 11:13:29 UTC
[jira] Created: (MNG-3573) Customization of jar-name pattern of
classpath-entries inside MANIFEST.MF
Customization of jar-name pattern of classpath-entries inside MANIFEST.MF
-------------------------------------------------------------------------
Key: MNG-3573
URL: http://jira.codehaus.org/browse/MNG-3573
Project: Maven 2
Issue Type: New Feature
Components: maven-archiver
Affects Versions: 2.0.8
Reporter: manuel aldana
Priority: Critical
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 .
--
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
[jira] Moved: (MSHARED-32) Customization of jar-name pattern of
classpath-entries inside MANIFEST.MF
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MNG-3573 to MSHARED-32:
------------------------------------------
Affects Version/s: (was: 2.0.8)
Component/s: (was: maven-archiver)
maven-archiver
Key: MSHARED-32 (was: MNG-3573)
Project: Maven Shared Components (was: Maven 2)
> Customization of jar-name pattern of classpath-entries inside MANIFEST.MF
> -------------------------------------------------------------------------
>
> Key: MSHARED-32
> URL: http://jira.codehaus.org/browse/MSHARED-32
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-archiver
> Reporter: manuel aldana
> Priority: Critical
>
> 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 .
--
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
[jira] Closed: (MSHARED-32) Customization of jar-name pattern of
classpath-entries inside MANIFEST.MF
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MSHARED-32.
-----------------------------
Resolution: Fixed
Fix Version/s: maven-archiver-2.4
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:
{code:xml}
<classpathLayoutType>custom</classpathLayoutType>
<customClasspathLayout>${artifact.artifactId}-${artifact.baseVersion}${dashClassifier?}.${artifact.extension}</customClasspathLayout>
{code}
The configuration for this should show up in the classpath examples page on the maven-archiver website once the release is done.
> Customization of jar-name pattern of classpath-entries inside MANIFEST.MF
> -------------------------------------------------------------------------
>
> Key: MSHARED-32
> URL: http://jira.codehaus.org/browse/MSHARED-32
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-archiver
> Reporter: manuel aldana
> Assignee: John Casey
> Priority: Critical
> Fix For: maven-archiver-2.4
>
>
> 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 .
--
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