[ http://jira.codehaus.org/browse/MPARTIFACT-35?page=comments#action_79518 ] David Hay commented on MPARTIFACT-35: -------------------------------------
Why has this been marked "Won't Fix"? This is a serious and frustrating limitation, in my opinion. Please reconsider. > artifact goals should allow different names > ------------------------------------------- > > Key: MPARTIFACT-35 > URL: http://jira.codehaus.org/browse/MPARTIFACT-35 > Project: maven-artifact-plugin > Issue Type: Improvement > Affects Versions: 1.5 > Reporter: Felipe Leme > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > It would be nice it <artifact> tags allows us to change the name of the > artifact being installed/deployed. That wuold be really helpful when your > project has 'secondary artifacts', like javadoc, zip files or a simple war > with documents. > For instance, when you call javadoc:install, a jar file is created at target > (PROJECT-version_javadoc.jar) but that file is installed as a .javadoc, even > though the call to <artifact:install> uses the same name as the existing > article on target: > <artifact:install > artifact="${maven.javadoc.final.name}" > type="javadoc" > project="${pom}"/> > In other, it would be nice if artifact:install (and deploy, deploysnaspshot, > etc...) used the name passed on the artifact attribute (instead of always > using ${pom.artifactId}-version.${type}. > Felipe -- 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
