Your project shouldn't have built because those JARs/WARs don't exist. If its building then you've got a corrupt local repository.
If you want to build 3.3.5.1 with your local WAR overlay, as already stated, you need to do the following: 1. check out the CAS 3.3.5.1 tag from SVN (source.jasig.org/cas3) 2. build it using "mvn clean package install -Dmaven.test.skip=true" This will put all the JARs/WARs in your local repository 3. Then build your local overlay with 3.3.5.1 Your other option is to just make the one important JSP page change (the logout page) since you probably have a locally customized file and add the default Services Management Dao configuration into the deployerConfigContext.xml if you're not already planning on more restrictive Services Management Tool services. The original email should have a link to the diff for the JSP page (its casLogoutView.jsp I believe). Its merely removing the block that checks param.url. Whether you upgrade or not via Maven WAR Overlay, you need to apply the Services Management Tool configuration change manually if you're not using the JdbcDao. On Thu, Aug 5, 2010 at 11:52 AM, Steve Cook <[email protected]> wrote: > Ok, let me start over here. > I have successfully updated from 3.3.3 to 3.3.5. During the update process > I also switched over to using the Maven Overlay Method. Now, I am trying to > update from 3.3.5 to 3.3.5.1. I copy my project home, change my POM file to > use cas.version 3.3.5.1 and build the project. I get no build errors, but > the war file is only 7MB where as the 3.3.5 file was 18MB. When I deploy > the war file, it of course does not work properly and does not start. I > know this has to do with the repository not being available for 3.3.5.1, but > what am I missing to get this working! I am attaching my 3.3.5.1 Overlay POM > file, maybe I am missing something from 3.3.5 to 3.3.5.1? Could someone that > has successfully updated please lend me a hand here, I am getting close to > admitting defeat and just deploying 3.3.5 into production. > > Thanks Again! > > Steve > > *[email protected] on Wednesday, August 04, 2010 at 10:44 PM -0500 > wrote:* > The issue isn't the build process per say, its the fact that CAS 3.3.5 and > earlier were hosted on the Jasig repository. Newer versions are hosted > elsewhere (and eventually end up on the central repos). The old Jasig > repository was shut down so the CAS 3.3.5 builds have no where to send the > data to if they are told to deploy. Reconfiguring the build would have > resulted in it being more than just a security fix as well as delayed the > patch. > > > I'll look to see if I can manually upload the jars though. A cursory look > doesn't instill much confidence in it working though. > > > Cheers, > Scott > > > 2010/8/4 Michael Ströder <[email protected]> > > > > Scott Battaglia wrote: > > The original announcement said due to the new repository switch, we > > can't post those artifacts. > > > I'm not familiar with maven and I don't want to just blame the volunteers > doing the work with CAS. But looking at it from an operational point of > view > it's a very unfortunate situation that an important security fix resulting > in > rather minor changes of the code (3.3.5->3.3.5.1) requires a major change > in > the build process. > > After all I'll be able to work around this. But please consider an update > policy within a release series where such an urgent security fix can be > easily > applied by less skilled people by just changing the version numbers in the > pom.xml and then running mvn package. > > Ciao, Michael. > > > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > > > -- > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
