Page Comparison

<!-- This should be part of the test framework -->
    <dependency>
      <groupId>org.sakaiproject.kernel</groupId>
      <artifactId>sakai-kernel-private</artifactId>
      <version>1.0.4-SNAPSHOT</version>
      <scope>test</scope>
    </dependency>

h3.  Testing exceptions

None.  ${sakai.kernel.version} property added to gradebook/app/standalone-app/pom.xml and sections/sections-impl/integration-support/pom.xml

<!--
Binding directly to the kernel impl is not a good idea,
It is liable to change.
When a test harness becomes available this code should be ported.

Hard coding the version so that we dont forget.
-->
    <dependency>
      <groupId>org.sakaiproject.kernel.impl</groupId>
      <artifactId>sakai-util-impl</artifactId>
      <version>1.0RC2-SNAPSHOT</version>
    </dependency>

 now binds to sakai-kernel-impl properly

h3. Performing the release

h4. Copy Maven2 /kernel locally

Start now as this can take some time.  Folder copy will later serve as target for deploying artifacts generated during the deploy phase.

{noformat}
copy http://source.sakaiproject.org/maven2/org/sakaiproject/kernel 
to 
/tmp/maven2/org/sakaiproject/kernel

{noformat}

h4. Backup Sakai Maven2 Repo /kernel

Create a backup copy of /kernel.

{noformat}
cd /var/www/html/maven2/org/sakaiproject
sudo cp -R kernel kernel-[current version]

{noformat}

h4. Checkout the kernel project 

Checkout a clean version of the project using SVN not git.

{noformat}
svn co https://source.sakaiproject.org/svn/kernel/branches/kernel-1.0.x/ kernel-1.0.x

{noformat}  

(!) Avoid opening it in Eclipse; otherwise you will pollute the projects with Eclipse metadata files that will have to be deleted before performing the release.  Checkout with svn (not git)

h4. Clean out local repo 

Verify that a clean build works ok with no external dependencies.  Issuing {{mvn -o clean install}} ensures that {{.m2}} repo is populated, a requirement for the assembly plugin.  If the build fails because external dependencies are missing in {{.m2}} run {{mvn clean install}}, then delete {{/kernel}} and run {{mvn -o clean install}} again.

{noformat}
rm -rf ~/.m2/repository/org/sakaiproject/kernel
mvn -o clean install
{noformat}

*Note:* check for Eclipse metadata files (.classpath, .project) and remove.  Uncommitted versions of these files will cause {{mvn release:prepare}} to fail.

}}.

h3. Trunk vs Branch releases

When releasing from trunk, issue the branch goal to create a new branch:

{noformat}
mvn release:clean  (clean up release)  
mvn release:branch -DbranchName=kernel-1.1.x

}}

{noformat}
#!/bin/sh
# Delete artifact folders prior to deploying Maven snapshot artifacts.
# This is necessary as Maven does not update it's metadata files correctly when an old artifact exists in the repo.
# bash deletesakaiartifact.bash [TARGET FOLDER NAME] (e.g., 1.1-SNAPSHOT) [LOCATION] (e.g. /tmp/maven2/org/sakaiproject/kernel)
# author=Anthony Whyte, arwhyte@umich.edu

TARGET=$1
LOCATION=$2

cd $LOCATION
echo "Removing ${TARGET} folders and content recursively from ${LOCATION}"
rm -rf `find . -type d -name ${TARGET}`