...
| No Format |
|---|
mvn release:prepare -DdryRun=true mvn release:clean release:prepare release:perform |
~arwhyte Former user (Deleted): the combination of Maven 2.0.10 (or 2.1.0), Subversion 1.5.6 and maven-release-plugin 2.0-beta-9 on Mac 10.5.7 (Leopard) resulted in a svn commit failure during the release:perform phase when attempting to update the branch pom <version>. I resolved this issue by first performing a rollback and then added my username and password as arguments to the clean/prepare/perform goals. This problem occurred despite my abilit to commit to our SVN SCM system normally using either my username/password or SSH private/public key.
...
links for fixforversion need to be updated to point to 1.0.9.
Example:
| No Format |
|---|
I've released sakai-kernel-1.0.9 and updated both the Sakai maven2 release and snapshot repositories with fresh artifacts (1.0.9, 1.0.10-SNAPSHOT; 1.1-SNAPSHOT was refreshed yesterday). Both Sakai 2.6.x and the upcoming sakai-2.6.0-rc05 will bind to 1.0.9. The issues addressed by 1.0.9 can be reviewed in Jira at
http://jira.sakaiproject.org/jira/browse/KNL/fixforversion/11505
Issues addressed by earlier releases can also be reviewed in Jira at
http://jira.sakaiproject.org/jira/browse/KNL?report=com.atlassian.jira.plugin.system.project:versions-panel
KERNEL (K1) PROJECT INFO
Jira: http://bugs.sakaiproject.org/jira/browse/KNL
Confluence: http://bugs.sakaiproject.org/confluence/display/REL/Kernel+1+(K1)
NOTICE: TRUNK/CONTRIB DEVELOPERS DEVELOPING AGAINST K1
Please refresh your local development environment.
1. MVN: Backup/delete the .m2/repository/org/sakaiproject/kernel of
your repo
2. SVN: perform an svn update on sakai trunk code (this will pick up
Sakai updates that complement the K1 updates)
3. MVN: perform a clean and install on your sakai trunk code to
refresh your .m2 repo with updated kernel 1.1-SNAPSHOT artifacts.
4. Build and deploy to Tomcat.
cd master
mvn clean install
cd ..
mvn clean install sakai:deploy
cheers,
Anthony
|
...