[m2] Minimize project version occurence in multiproject configuration

[Geoffrey]

I have a parent pom.xml like this:

    <groupId>y</groupId>
    <artifactId>x</artifactId>
    <packaging>pom</packaging>
    <version>0.0.1-SNAPSHOT</version>
    <modules>
        <module>thot-model</module>
        <module>thot-serviceapi</module>
    </modules>

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>y</groupId>
                <artifactId>x-model</artifactId>
                <version>0.0.1-SNAPSHOT</version>
            </dependency>
            <dependency>
                <groupId>y</groupId>
                <artifactId>x-serviceapi</artifactId>
                <version>0.0.1-SNAPSHOT</version>
            </dependency>
        </dependencies>
    </dependencyManagement>

And each child pom.xml like:

    <parent>
        <groupId>y</groupId>
        <artifactId>x-serviceapi</artifactId>
        <version>0.0.1-SNAPSHOT</version>
    </parent>

    <dependencies>
        <dependency>
            <groupId>y</groupId>
            <artifactId>x-model</artifactId>
        </dependency>
    </dependencies>

1) Is there a way to minimize the number of times I need to specify the 
version "0.0.1-SNAPSHOT" of my multiproject?
Ideally it should only use it on one spot: in the parent pom.xml
In dependencyManagement I can lower it by using ${pom.version},
but for referencing the parent pom this does not look like an option.

2) Why do I need to add my modules as dependencies in the first place?
It would be nice if the parent pom is smart enough to add all it's 
modules as possible dependencies automatically.


--
Thanks for any and all help,
Geoffrey De Smet


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]