Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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-Issuechange npanday.stable.version to npanday.bootstrap.version- preconfigure npanday.bootstrap.version with ${project.version}
- update docs (http://incubator.apache.org/npanday/docs/1.3-incubating/developers/building.html)
- document how to do the first build (when npanday-settings.xml not yet exists)
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
Attachments
Issue Links
- is depended upon by
-
NPANDAY-383 update groupID to org.apache.npanday
- Resolved