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

"scott.stark(a)jboss.org" wrote : "pgier" wrote : 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. | | | Right, I was just reproducing the dependency info in the plugin config to allow the mapping to be clear. | Oh yeah, sorry, I didn't read your earlier post very carefully. It will look very similar to what you put above. "scott.stark(a)jboss.org" wrote : | "pgier" wrote : | | 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. | | | Remember we really don't need the component-info.xml in the local thirdparty contents as we would not be using the jbossbuild repository mechanism any longer. | It's not a big deal since I already had some small code for it from the jboss-deploy plugin. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132220#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...