I've been working on a maven plugin to create extra modules for tests, so what you
describe would certainly be possible. The maven plugin/dependency api is pretty nice to
work with. Once I've got my forked surefire plugin working, I can take a look if the
general consensus is that we should go with something like this
On 17 Dec 2010, at 12:47, David Bosschaert wrote:
Hi all,
Today I was looking at a module.xml somewhere down
http://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/m...
and found out that a problem I was facing was caused by a dependency in
there being out of sync with the dependencies of the pom that defines
the original module.
So I was thinking, since there is a 1-1 mapping between the poms and
modules would it make sense to automatically generate the module.xml
files from the poms rather then having them in git. I realize that there
is extra information in some cases that needs to go into the module.xml
file but that information could be added to the pom in some form [1].
Otherwise this might become a bit of a maintenance nightmare IMHO...
Or is this already happening somewhere in a way that I'm not aware of?
Cheers,
David
[1] The maven-bundle-plugin does something similar for OSGi bundles:
http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev