[jira] Closed: (MNG-2479) add support for optional 'packagingName' element in dependency blocks
[ http://jira.codehaus.org/browse/MNG-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-2479. - Resolution: Won't Fix Fix Version/s: (was: Reviewed Pending Version Assignment) the call for this seems to have evaporated over the past couple of years as the EE plugins have become capable at naming their dependencies. It's unlikely we'll modify the dependency model significantly in the near future due to the implications for the repository. add support for optional 'packagingName' element in dependency blocks - Key: MNG-2479 URL: http://jira.codehaus.org/browse/MNG-2479 Project: Maven 2 Issue Type: New Feature Components: Dependencies Affects Versions: 2.0.4 Reporter: Ian Springer The various deployment artifact types (war, ear, sar, etc.) package their dependencies within the target archive during the package phase. For example, the war plugin includes jar dependencies within WEB-INF/lib, and the ear plugin includes jar and J2EE dependencies at the top level. Sometimes it is not desirable to package the dependencies with their full Maven-repo-style names (i.e. artifactName-version.xar). In particular, the version component is often not desired. Currently, some plugins provide a way to rename these dependency artifacts when they are packaged (e.g. the ear plugin), and others do not (e.g. the war plugin), making it necessary to use an antrun or dependency plugin hack to rename the artifacts as desired. I think it would be much nicer if there was a standard way to specify a packaging name (or whatever other name makes sense) for a dependency in its dependency block in the pom. Then all plugins that package their dependencies could leverage this standard setting. Here is an example of a war dependency declared in an ear pom: dependency groupIdorg.jboss.on/groupId artifactIdon-enterprise-gui-portal/artifactId version2.0-SNAPSHOT/version typewar/type packagingNameon-portal/packagingName /dependency This would cause the war to be bundled in the ear with the filename on-portal.war, instead of the default on-enterprise-gui-portal-2.0-SNAPSHOT.war. -- 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: (MNG-2479) add support for optional 'packagingName' element in dependency blocks
[ http://jira.codehaus.org/browse/MNG-2479?page=all ] Brett Porter closed MNG-2479. - Assignee: Brett Porter Resolution: Won't Fix this should be available as plugin configuration for the various packaging plugins already - if not it should be requested for each, both on an artifact by artifact basis and to be able to map all names using a mapper. A generic solution in the dependency element is not desired since it will not work with transitive dependencies (W, a WAR depends on B with depends on A - B's dependency on A doesn't know to specify this element because it doesn't know it will later be used in a WAR). add support for optional 'packagingName' element in dependency blocks - Key: MNG-2479 URL: http://jira.codehaus.org/browse/MNG-2479 Project: Maven 2 Issue Type: New Feature Components: Dependencies Affects Versions: 2.0.4 Reporter: Ian Springer Assigned To: Brett Porter The various deployment artifact types (war, ear, sar, etc.) package their dependencies within the target archive during the package phase. For example, the war plugin includes jar dependencies within WEB-INF/lib, and the ear plugin includes jar and J2EE dependencies at the top level. Sometimes it is not desirable to package the dependencies with their full Maven-repo-style names (i.e. artifactName-version.xar). In particular, the version component is often not desired. Currently, some plugins provide a way to rename these dependency artifacts when they are packaged (e.g. the ear plugin), and others do not (e.g. the war plugin), making it necessary to use an antrun or dependency plugin hack to rename the artifacts as desired. I think it would be much nicer if there was a standard way to specify a packaging name (or whatever other name makes sense) for a dependency in its dependency block in the pom. Then all plugins that package their dependencies could leverage this standard setting. Here is an example of a war dependency declared in an ear pom: dependency groupIdorg.jboss.on/groupId artifactIdon-enterprise-gui-portal/artifactId version2.0-SNAPSHOT/version typewar/type packagingNameon-portal/packagingName /dependency This would cause the war to be bundled in the ear with the filename on-portal.war, instead of the default on-enterprise-gui-portal-2.0-SNAPSHOT.war. -- 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
