[jboss-dev-forums] [Design of JBoss Build System] - Re: Shared Parent POM for dependencyManagement
pgier
do-not-reply at jboss.com
Wed Mar 19 10:43:18 EDT 2008
"pgier" wrote : "ALRubinger" wrote : I have committed org.jboss.jbossas:jboss-as-dependency:
| |
| | http://jira.jboss.com/jira/browse/JBAS-5324
| |
| | Looking to avoid being too invasive here. The shared POM is now committed and deployed for review, though I'm holding the commit for org.jboss.jbossas:jboss-as-parent until we can verify that all looks allright. Once Paul gives me the nod, I'll commit that change.
| |
| | The patch up for review is attached to the JIRA, as is the commit of the new project.
| |
| | Paul, let's look over this together.
| |
| | S,
| | ALR
|
| Hey Andrew, I think it's fine to commit this, except for the prerequisites section (maven 2.0.8). I think that should stay in the jbossas parent because it doesn't get inherited. If ejb also requires 2.0.8 you'll have to define it in that parent also.
|
| Also, I must have committed the 2.2-beta-3-SNAPSHOT version of the assembly plugin by mistake. I was working with that locally, but the one in the pom should be 2.2-beta-2.
|
|
One more thing I realized, is that the jbossas intermodule dependencies (deps with groupid "org.jboss.jbossas") will probably have to remain in the as parent, and not in the new super parent. Otherwise we could have a chicken/egg problem when trying to release.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137787#4137787
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137787
More information about the jboss-dev-forums
mailing list