Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <herve.boutemy@free.fr>
To: dev@maven.apache.org
Subject: easing Maven parent poms management
Date: Sun, 01 Nov 2015 10:03:34 +0100
Message-ID: <2524303.3Sa8sxfxFZ@herve-desktop>
User-Agent: KMail/4.13.3 (Linux/3.13.0-66-generic; KDE/4.13.3; x86_64; ; )
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

Currently, we have 5 Maven parent POMs [1] (not counting Doxia), each w=
ith its=20
own release cycle.
Releasing each separately is a pain. And knowing which pom is at which =
version=20
is a pain also.

What would you think of:

1. setting the same version to every Maven parent POM: next would be ve=
rsion=20
29, since the maximum currently is plugins parent at 28

2. releasing the 5 POMs in only one release

This would mean putting all the poms in pom svn [2] (currently plugins =
parent=20
is in plugins, shared in shared, skins in skin...).
I still don't know if the best bet is to make Maven parent the release =
root:
maven
   |-- plugins
   |-- shared
   |-- skins
   |-- archetypes

or if we should create a new parent that is only used as reactor

any opinion?

Regards,

Herv=E9

[1] http://maven.apache.org/pom/index.html

[2] http://svn.apache.org/repos/asf/maven/pom/trunk/maven/

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