Versions Compared

Old Version 3

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

No Format
mvn release:prepare -DdryRun=true
mvn release:clean release:prepare release:perform

(warning) 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.

No Format

mvn release:rollback
mvn -Dusername=arwhyte@umich.edu -Dpassword=mypassword release:clean release:prepare release:perform

When prompted for new versions:

...

The release plugin will then branch the current trunk to branches/kernel-1.1.x.
Edit the poms to 1.2-SNAPSHOT and commit.

Finis(warning) If the release:perform should hang for some reason you can check out the tag do the following:

  1. restore maven2/org/sakaiproject/kernel from backup *.tgz
  2. check out 1.0.9 tag and generate release from tag:
No Format

cd 1.0.9
mvn release:perform -DconnectionUrl=scm:svn:https://source.sakaiproject.org/svn/kernel/tags/kernel-1.0.9

Check 1.0.9 tag

The release plugin will generate a 1.0.9 tag. Check it out and make sure it works, binding it against a local working copy of 2.6.x.

...

No Format
I've released sakai-kernel-1.0.69 and updated both the Sakai maven2 reporelease and snapshot repositories with fresh artifacts.   (1.0.9, 1.0.6 has been released in support of.10-SNAPSHOT; 1.1-SNAPSHOT was refreshed yesterday).  Both Sakai 2.6.x and the upcoming sakai-2.6.0 release-rc05 will bind to 1.0.9.  
The issues addressed by 1.0.69 can be reviewed in Jira at

http://bugsjira.sakaiproject.org/jira/browse/KNL/fixforversion/1147611505

Issues addressed by earlier releases can also be reviewed in Jira at

http://bugsjira.sakaiproject.org/jira/browse/KNL?report=com.atlassian.jira.plugin.system.project:versions-panel


MAVEN2
REPO

The maven2 repo includes the following new or refreshed artifacts:

https://source.sakaiproject.org/maven2/org/sakaiproject/kernel/

1.0.6
1.0.7-SNAPSHOT
1.1-SNAPSHOT


SVN

The 1.0.6 release has been tagged and the 2.6.x branch /master/pom.xml file 
has been updated to bind to 1.0.7-SNAPSHOT.  
When the next 2.6.0 tag is cut it will bind to K1 1.0.6.


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 -Dmaven.test.skip=true sakai:deploy

cheers,

Anthony

...