geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Kashyap" <>
Subject Re: Restructuring top level pom.xml
Date Mon, 20 Mar 2006 17:01:43 GMT
Opened JIRA to track this work.

If we want to set ${geronimoVersion} at the top level pom and  don't
worry about changing it for every release, we have to do a 'mvn -N'
for every pom.xml whose packaging is set to "pom". Currently that
would be like 6 pom.xmls for the 6 top level dirs.

If we want to do a top level build with 1 single 'mvn' command, then
we cannot use ${geronimoVersion} while declaring the project's and
parent's version. We will have to explicitly define the version. That
would mean changing every single pom.xml every time the release

Setting the version in -D doesn't work either.


On 3/18/06, Alan D. Cabrera <> wrote:
>  Jason Dillon wrote:
>  Would you then move all the code inside to the same package, as in
> org.apache.geronimo.modules.kernel or
> org.apache.geronimo.applications.daytrader?
>  Package names do not need to relate directly to Maven groupIds.
> Especially not for intermediate grouping modules, that do not directly
> relate to code anyways.
> I do not recommend that package names be altered at this time. Once
> maven2 conversion is finished and it is time to rethink the general
> structure, it might be a good idea to try and sync up package names.
> I don't think that we ever want to have a
> org.apache.geronimo.modules.kernel... but perhaps a
> org.apache.geronimo.applications.daytrader.
>  Good point.
>  Regards,
>  Alan

View raw message