Deploying maven built artifacts to the ant repository.

[pgier]

Andrew created this issue http://jira.jboss.com/jira/browse/JBBUILD-437

This would allow a maven built project to deploy to the maven repository with it's normal artifactId, but deploy to the ant/buildmagic repository with a different artifactId. Specifically it could apply to the jboss metadata project which in maven looks like:

/org/jboss/jboss-metadata

But would be able to deploy to the ant repository as

/jboss/metadata

My only concern with this is that it becomes more difficult to track corresponding artifacts if artifactIds are different.

Would it be better to just change the ant build dependencies on metadata so that they use the same artifactId that maven projects are using? In other words, change the references in any build-thirdparty.xml files to use the same name as maven is using.

[alrubinger]

I'm in favor of using the proposed feature enhancement for legacy projects only, in order to avoid regression that may be a side effect of altering the ant build dependencies.

Seems eventually, all projects for 3rdparty and Maven artifactIds should match. I'd consider this a migration path to avoid manual editing of component-info.xml and directory structures for repository.jboss.org.

S,
ALR

[alrubinger]

Thank you for this enhancement, Paul.

Where can I look for examples of using the new override? (I assume it's a new node in the POM under the configuration for the jboss-deploy mojo).

S,
ALR

[pgier]

If you use the snapshot version, you can add an something to the configuration. I'm planning to release the plugin tomorrow, and I'll update the plugin site (http://labs.jboss.org/maven-jboss-deploy-plugin) when I do that.

[pgier]

Oops, I forgot to escape my tags. You can use

<artifactId>new-name</artifactId>