Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
From: "Loehr, Ruel" <rloehr@pointserve.com>
To: "ivy-user@ant.apache.org" <ivy-user@ant.apache.org>
Date: Thu, 10 Apr 2008 09:07:40 -0500
Subject: RE: multimodule conversion from maven to ant + ivy
Thread-Topic: multimodule conversion from maven to ant + ivy
Thread-Index: AQHImw5uHs4z0T3SOkuWPDMmh4mHT42k8Q6w
Message-ID: 
 <93B3B6122B906D44BC7E8B8CEFB0DBBB1844B992A3@SGP-EXCHANGE.pointserve.com>
In-Reply-To: 
 <93B3B6122B906D44BC7E8B8CEFB0DBBB18448FA485@SGP-EXCHANGE.pointserve.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

To get a little more detailed:

In my top level module I have a version.properties which defines a MAJOR, M=
INOR, and REVISION property.

When I call the main build, I have three specific targets:,  dev, nightly, =
release.

The dev target constructs a version of 2.0.0-dev.   It publishes to a local=
 repository.

Nightly constructs a version of 2.0.0-SNAPSHOT.  It publishes to a public r=
epository.

Release constructs a vesion of 2.0.0.   Also publishes to a public reposito=
ry.

1)  Still not sure how handle versioning in sub modules.   I assume that a =
submodule can be executed standalone and I would like to not hardcode value=
s in for project dependencies.


Thoughts?


-----Original Message-----
From: Loehr, Ruel [mailto:rloehr@pointserve.com]
Sent: Thursday, April 10, 2008 8:26 AM
To: ivy-user@ant.apache.org
Subject: multimodule conversion from maven to ant + ivy

We have a legacy project which is maven based.  Everyone hates maven, and w=
e use ivy for other projects, thus, a migration is necessary.


I'd like to keep the existing file structure as is, and simply replace the =
build scripts.        That part is done.     I need some help with how to h=
andle the versioning though.


Assume we have a multi module structure:


Root

       /a

       /b

       /c


What I "think" should happen is that in the root directory I define a versi=
on.properties file with the version.   That version should propogate into e=
ach submodule.


The ivy.xml in submodule b will list a dependency like this:


            <dependency org=3D"a" name=3D"a" rev=3D"${VERSION}" conf=3D"com=
pile->runtime"/>


This works great as long you check out the root folder and always execute e=
ach build from the top level aggregator.   However, as we develop in eclips=
e, people must check out each projects as standalone.    Their isn't a vers=
ion defined when running in that context.


Has anyone else faced this?   How do you handle it?   In maven, it works du=
e to the sub builds going to the repository and getting the parent pom.....


R