incubator-isis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mohammad Nour El-Din <>
Subject Re: Commit 1148917: Changes for Maven3
Date Thu, 21 Jul 2011 09:39:19 GMT
One simple approach is to have 2 pom.xml files

1- pom.xml - which is the default one for Maven3 based build
2- pom2.xml - For Maven 2.x.x build

And when we need to build using that later file we use the -f/--file
option to specify that specific file. The drawback of this approach is
that we will need to maintain different files and also IDK about the
effect of this on build of sub-modules.

On Thu, Jul 21, 2011 at 9:55 AM, Kevin Meyer <> wrote:
> Dan,
> Thanks to Nour's getting Isis into the fisheye system[1], I've noticed
> that you updated the framework/pom.xml to allow Maven3 in the rules
> section.
> I seem to recall that there is a problem with the site plugin, though.
> Maven3 requires a maven-site-plugin of 3.0-beta-3 which in turn, requires
> Maven3. Thus, unless there is a way to build in conditional version
> dependencies into the dependencies sections, the same framework/pom.xml
> can't support both Maven 2 and Maven 3, at least as far as the site
> plugin is concerned...
> Any suggestions?
> Regards,
> Kevin
> PS: Thanks Rob (for the nudge) and Nour for switching on the Fisheye view!
> [1]

- Mohammad Nour
  Author of (WebSphere Application Server Community Edition 2.0 User Guide)
- LinkedIn:
- Blog:
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein

"Writing clean code is what you must do in order to call yourself a
professional. There is no reasonable excuse for doing anything less
than your best."
- Clean Code: A Handbook of Agile Software Craftsmanship

"Stay hungry, stay foolish."
- Steve Jobs

View raw message