Simple - Check out Sakai - check out /svn/portlet - checkout /contrib/portlets (yes - one is singular and one is plural - sorry).
Start with fresh Tomcat.
Compile everything - "maven sakai" or "maven bld dpl" depending on your fun. This compiles with the old jars - but is necessary to get everything downloaded to your maven repo.
Go into tomcat/shared and do "find . -name '*pluto*'" - blast everything - these should be the previous verison of Pluto - there should be four of them.
Edit master/project.properties and increment the version of Pluto
Go into ~/.maven/repository/org.apache.pluto/jars and wack all the files
Based on the URL in the message on the pluto-dev list, use CURL to pull down the most recent jars. You need four of them.
curl -O http://people.apache.org/builds/portals-pluto/m2-staging-repository/org/apache/pluto/pluto-container/1.1.3/pluto-container-1.1.3.jar
curl -O http://people.apache.org/builds/portals-pluto/m2-staging-repository/org/apache/pluto/pluto-descriptor-api/1.1.3/pluto-descriptor-api-1.1.3.jar
curl -O http://people.apache.org/builds/portals-pluto/m2-staging-repository/org/apache/pluto/pluto-descriptor-impl/1.1.3/pluto-descriptor-impl-1.1.3.jar
curl -O http://people.apache.org/builds/portals-pluto/m2-staging-repository/org/apache/pluto/pluto-taglib/1.1.3/pluto-taglib-1.1.3.jar
Go into ~/dev/sakai/portal
maven -o bld dpl
This makes sure you don't pull the old jars back down.
Just for fun and to keep your mind at ease - go to tomcat/shared
find . -name '*pluto*'
There should be four files with the *new* version.
Start Tomcat - tail the log like any good hacker (or if you are cool use the debugger).
Make a site - add the "Test Portlet - Sakai Test Portlet (JSR-168)" to your site - it is the one near the bottom.
Click around - test everything - watch the log. It is normally quite chatty - so you are watching for failures.
Posted by csev at March 31, 2007 07:25 PM