In maven terms the equivalent to doing this at the module level, I think would be having
different artifactIds. So you could have jbossws and jbossws-jdk14 as separate
artifactIds. Or at the groupId level, you would have something like org.jboss.jboss-test
and org.jboss-jdk14.jboss-test.
A couple of issues I see with this in terms of how maven does things:
You would have two separate sets of dependencies because maven would treat these as
completely separate projects. But it probably wouldn't be that difficult to do.
Another problem would be deploying the separate artifacts. Maven profiles do not allow
you to change the groupId or artifactId. So I think you would need to have a separate
pom.xml, so you would have some duplication of work there.
Having a separate pom.xml could be used in addition to having a separate repository. It
basically would replace the use of a profile to determine deployment location and whether
to run the retro-translation.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070323#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...