[
http://jira.jboss.com/jira/browse/JBBUILD-437?page=comments#action_12390739 ]
Paul Gier commented on JBBUILD-437:
-----------------------------------
I thought about adding this option when I added the groupId one. But it seemed like it
could lead to confusion about where matching artifacts are. Can we just change the build
scripts that depend on the old name? Or will that cause too many problems?
It's not a big deal to add this, I just want to make sure it is the right behaviour.
Allow for thirdparty artifact name to differ from maven artifactId
------------------------------------------------------------------
Key: JBBUILD-437
URL:
http://jira.jboss.com/jira/browse/JBBUILD-437
Project: JBoss Build System
Issue Type: Feature Request
Affects Versions: maven-jboss-deploy-plugin-1.5
Reporter: Andrew Lee Rubinger
Assigned To: Paul Gier
Defining case for this is jbossas/projects/metadata
Maven Artifact ID is "jboss-metadata", but in
repository.jboss.org this is
placed into "jboss/metadata/", not "jboss/jboss-metadata".
Please provide a hook for the override of the thirdparty artifact name.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira