Definitely helpful in trying to ship a self-contained release.
On 28/03/2011, at 5:30 PM, Lars Corneliussen wrote:
> Hi,
>
> I really find it an obstacle to build NPanday trunk itself with an old
> NPanday version. It feels like stone age :) But sadly, due to a bug in MVN
> 2.2.1, it is not possible to use plugin-versions that just built within the
> same reactor.
>
> So i suggest to move on to Maven 3.0.x for building NPanday trunk.
>
> Suggestion:
>
> 1) Bootstrapping NPanday with current NPanday. (not possible on MVN 2.2.x)
> 2) Require Maven >= 3 for *building* NPanday >= 1.3.1
>
> We should still make sure, that NPanday does work with Maven 2.2.x, though.
>
> Integration tests should run both in Maven 2.2.1 and Maven 3.0.2 or 3.0.3
>
> *TODO:*
> * Add a Jira-Issue
> * change npanday.stable.version to npanday.bootstrap.version
> * preconfigure npanday.bootstrap.version with ${project.version}
> * update docs
> * remove all .NET-PATHes from the PATH environment
> * remove most of the PATH-related docs
>
> *Helpers on Windows for rapid switching of maven versions:*
>
> *mvn3.bat* (somewhere on the PATH)
> set M2=C:\Program Files\Apache\apache-maven-3.0.2\bin
> set M2_HOME=C:\Program Files\Apache\apache-maven-3.0.2
> set PATH=C:\Program Files\Apache\apache-maven-3.0.2\bin;%PATH%
> mvn --version
>
> *mvn2.bat* (somewhere on the PATH)
> set M2=C:\Program Files\Apache\apache-maven-2.2.1\bin
> set M2_HOME=C:\Program Files\Apache\apache-maven-2.2.1
> set PATH=C:\Program Files\Apache\apache-maven-2.2.1\bin;%PATH%
> mvn --version
>
--
Brett Porter
[email protected]
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
