[jboss-dev-forums] [Design of JBoss Build System] - Re: Moving jbossas to a maven repo for thirdparty

[pgier]

Unfortunately the mapping part will be separate from the dependencies, because the mapping will have to be a parameter to the plugin.  I can't change the XML for the dependencies in the pom without hacking up and forking the maven code.  I'll post an example tomorrow of what it looks like once I get a couple more of the details figured out.  

I'm going to make this a new mojo (maven plugin class) in the current jboss-deploy plugin because they can share some code for writing component-info files and other stuff.  I'm thinking about renaming the plugin to something like jboss-thirdparty plugin, but that's low priority.

I'll post artifacts that aren't in the repository as I find them.  It shouldn't be too bad to add the ones that are missing.  They don't have to be built with maven, they can just have a basic auto-generated pom.  I had to add some stuff like that already when I was working on the app server poms that are there now.



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131851#4131851

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131851