[jboss-dev-forums] [Design of JBoss Build System] - Re: Move dependency management back into app server svn stru

[scott.stark@jboss.org]

Ah, I see, thanks. I think mvn tries to resolve parent poms locally if it can. I see to different versions in this:


  |   <properties>
  | ...
  |     <version.org.jboss.common-core>2.2.3.GA</version.org.jboss.common-core>
  | 
  | ...
  | 
  |       <dependency>
  |         <groupId>org.jboss</groupId>
  |         <artifactId>jboss-common-core</artifactId>
  |         <version>2.2.4.GA</version>
  |       </dependency>
  | 

I don't see the version.org.jboss.common-core used anywhere though. So the build-thirdparty.xml is not used at all any longer. I thought Paul had updated this, but the build/build.xml createthirdparty target is just calling maven with the thirdparty dir as the basedir.


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

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