Building 0.3-RCx

[Guillaume Yziquel]

Hi.

I've been trying to build the 0.3-RCx branch of the Aries git repo:

                git://git.apache.org/aries.git

Building with Maven, I get:

[ERROR]   The project org.apache.aries.spifly:spifly:0.3-SNAPSHOT
(/my/dir/aries/spi-fly/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Failure to find
org.apache.aries:java5-parent:pom:0.3-SNAPSHOT

I notice that the spi-fly pom is

    <parent>
        <groupId>org.apache.aries</groupId>
        <artifactId>java5-parent</artifactId>
        <version>0.3-SNAPSHOT</version>
        
<relativePath>../parent/default-parent/java5-parent/pom.xml</relativePath>
    </parent>

    <groupId>org.apache.aries.spifly</groupId>
    <artifactId>spifly</artifactId>
    <name>Apache Aries SPI Fly</name>
    <version>0.3-SNAPSHOT</version>
    <packaging>pom</packaging>

but that the java5-parent pom has version 0.3.1-SNAPSHOT:

    <artifactId>java5-parent</artifactId>
    <name>Aries :: Java 5 Parent POM</name>
    <version>0.3.1-SNAPSHOT</version>
    <packaging>pom</packaging>

So there is a mismatch. Looking at the trunk branch, I notice that,
often, the relativePath declaration item is empty.

Given that Aries seems to be a loosely coupled collection of modules,
I'm wondering to which extent these mismatchs are bugs, or not.
Basically, what are the build practices with respect to versioning of
submodules?

-- 
Guillaume Yziquel
Crossing-Tech
Parc Scientifique EPFL