Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.fr;
  h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=DSEuOI4XcYSOm50n5PavYjWwDAQZa5+Be+oP6ybODmPVeXi++CQFmfzVt/o6JslPKkR/gS4xT8Y/tdD1wBX0eSDg3530RFkYFqccb8AN99Kr++5E0tyZd0VWecSfVx9CfwyoWJ9qgLYBQwLxpnA3qnFZeXMtK6bybSpJ2+ph3tw=;
Message-ID: <1311322109.55066.YahooMailNeo@web28503.mail.ukl.yahoo.com>
Date: Fri, 22 Jul 2011 09:08:29 +0100 (BST)
From: Julien HENRY <henryju@yahoo.fr>
Reply-To: Julien HENRY <henryju@yahoo.fr>
Subject: Maven API: how to get "reactor" order
To: Maven Users List <users@maven.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,=0A=0ABackground: I'm trying to develop a release helper tool for my com=
pany. We can't use the maven-release-plugin for several reasons. We have a =
notion that is like a "release train" were several projects must be release=
d at the same time. These projects can be Maven multi-module projects. Thes=
e projects can have interdependencies (SNAPSHOT). But of course no SNAPSHOT=
 dependency is allowed on a project that is not in the release train.=0A=0A=
Basically, I'm trying to have a tool to replace the current manual process:=
=0A=A0=A0=A0 1) think about release order according to inter dependencies (=
cycles are forbidden)=0A=0A=A0=A0=A0 2) mvn release:prepare release:perform=
 on first project=0A=A0=A0=A0 3) update all references to this project (rep=
lace SNAPSHOT version by released version) in all pom of the release train=
=0A=A0=A0=A0 4) mvn release:prepare release:perform on second project=0A=A0=
=A0=A0 5) update all references to this project (replace SNAPSHOT version b=
y released version) in all pom of the release train=0A=A0=A0=A0 ... (repeat=
 for all projects of the train)=0A=0A=0AWe already have a "tweak" to allow =
a full build of the release train with one Maven command. We have a tool th=
at create a Maven aggregator pom where each submodule is a svn:externals li=
nking to the trunk of each project.=0A=0Apom.xml (aggregator)=0A=0Aproject1=
 -> svn:externals to another_location/project1/trunk=0A=0Aproject2-> svn:ex=
ternals to another_location/project2/trunk=0A...=0A=0AprojectN-> svn:extern=
als to another_location/projectN/trunk=0A=0ANow I try to do step 1 automati=
cally. I want to find release order based on inter dependencies of my relea=
se train. I found the ProjectSorter class in Maven API, but it seems I have=
 to create a MavenProject for each project, and each sub module (as it seem=
s this is not recursive).=0AIs there a better way ?=0A=0AIn fact the best w=
ould be to create a graph of interdependencies. Because I would also try to=
 detect and prevent this kind of cycle:=0Aproject1/submodule1 depend on pro=
ject2/submodule1=0Aproject2/submodule1 depend on project1/submodule2=0A=0AT=
hanks for any pointer.=0A=0AJulien=0A

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org