[JBoss-dev] Updating jboss-common jars

[Scott M Stark]

Yes, and the build order is figured out based on the expressed 
dependencies when using the top level maven2 build project located under 
https://svn.jboss.org/repos/common/build/tags/2.0.0:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <groupId>org.jboss</groupId>
  <version>2.0.0</version>
  <artifactId>jboss-common</artifactId>
  <name>JBoss Common Build</name>
  <url>http://www.jboss.org</url>
  <description>Parent POM for the JBoss Common Classes Jars</description>
  <licenses>
   <license>
      <name>lgpl</name>
      <url>http://repository.jboss.com/licenses/lgpl.txt</url>
   </license>
  </licenses>
  <organization>
    <name>JBoss Inc.</name>
    <url>http://www.jboss.org</url>
  </organization>

  <packaging>pom</packaging>
  <modules>
    <module>../common-core</module>
    <module>../common-logging-spi</module>
    <module>../common-logging-log4j</module
    <module>../common-logging-jdk</module>
  </modules>
</project>

You would check this out into a structure like:
2.0.0/
  + build/pom.xml
  + common-core/pom.xml
  + common-logging-spi/pom.xml
  + common-logging-log4j/pom.xmljdk
  + common-logging-/pom.xml


You can create such a toplevel build pom for any projects you want to 
build collectively in the correct order.

Dimitris Andreadis wrote:
> Thanks, I corrected the page because it was pointing to the old
> locations (common/trunk/common-x rather than common/common-x/trunk)
>
> I've noticed also you need to build the modules in a certain order, is
> that expected?
>
> Finally, any idea how to change the location of the local repository
> (defaults to $HOME/.m2/repository) 
>
>