Yeah but I would have had to have done the initial download at some point using the same settings ;-) I can't remember if I did the download when I was using 2.0.7 or 2.0.9. It wouldn't be surprising if the behavior changed between versions.
JIRA is here: http://www.ja-sig.org/issues If you don't have an account you'll just need to create one. Thanks! -Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Fri, Aug 15, 2008 at 8:29 AM, <[EMAIL PROTECTED]> wrote: > > 2.0.8 > > I'm assuming it worked for you because you already had the stuff in your > local repository & so download was not needed. One of those bugs that only > the noobs can catch. :-) > > Thanks, > Ann > > ------ > G. Ann Campbell > Systems Engineer > Shaw Industries > > > > > *"Scott Battaglia" <[EMAIL PROTECTED]>* > Sent by: [EMAIL PROTECTED] > > 08/14/2008 09:11 PM > Please respond to > Yale CAS mailing list <[email protected]> > > To > "Yale CAS mailing list" <[email protected]> cc > Subject > Re: CAS Server 3.3 Final Release > > > > > Would you mind opening a JIRA issue for that so we can fix that for 3.3.1? > Strange that it works on my machine though...what version of Maven2 are you > using? > > -Scott > > -Scott Battaglia > PGP Public Key Id: 0x383733AA > LinkedIn: > *http://www.linkedin.com/in/scottbattaglia*<http://www.linkedin.com/in/scottbattaglia> > > > On Thu, Aug 14, 2008 at 4:21 PM, <[EMAIL PROTECTED]<[EMAIL PROTECTED]>> > wrote: > > Nevermind. > > I was able to stumble past this. > > Looks like the cas-server-integration-memcached/pom.xml needed a trailing > slash in the repository URL. > > i.e. this: > <url>*http://bleu.west.spy.net/~dustin/repo*<http://bleu.west.spy.net/%7Edustin/repo> > */*</url> > (not > <url>*http://bleu.west.spy.net/~dustin/repo*<http://bleu.west.spy.net/%7Edustin/repo> > </url>) > > Ditto the repository URL in cas-server-integration-restlet/pom.xml > > > Thanks, > Ann > > ------ > G. Ann Campbell > Systems Engineer > Shaw Industries > > > > *Ann Campbell/SHAW* > > 08/14/2008 03:44 PM > > To > Yale CAS mailing list <[EMAIL PROTECTED] <[email protected]>> cc > Subject > Re: CAS Server 3.3 Final > Release*Link*<Notes:///8525734D005FE7BC/DABA975B9FB113EB852564B5001283EA/E351E339FDC0F971852574A500556278> > > > > > > I'm still in the exploratory phase with CAS and am interested in using it > for Google Apps authentication, so I set aside the version I had been > working with, downloaded 3.3, made a few configuration changes and ran: > mvn -Dmaven.test.skip=true package > > I'm getting a build error (stupid console won't let me copy, so I'll sum > up): > Missing: > 1) spy:memcached:jar:2.1 > ... > 2) spy:spy:jar:2.4 > ... > 2 required artifacts are missing. > for artifact: > org.jasig.cas:cas-server-integration-memcached:jar:3.3 > > I was able to find * > http://developer.ja-sig.org/maven2/org/jasig/cas/cas-server-integration-memcached/3.3/cas-server-integration-memcached-3.3.jar > *<http://developer.ja-sig.org/maven2/org/jasig/cas/cas-server-integration-memcached/3.3/cas-server-integration-memcached-3.3.jar>in > one of the "specified remote repositories" ... > > So I'm wondering - was this the result of a temporary network glitch on my > end? Or does this mean there's a mistyped path in the Maven file? > > (This is my first dealing with Maven, so be gentle, please) > > > Thanks, > Ann > > ------ > G. Ann Campbell > Systems Engineer > Shaw Industries > > > > *"Scott Battaglia" <[EMAIL PROTECTED]<[EMAIL PROTECTED]> > *>* > Sent by: [EMAIL PROTECTED] <[EMAIL PROTECTED]> > > 08/14/2008 11:14 AM > > > Please respond to > Yale CAS mailing list <[EMAIL PROTECTED] <[email protected]>> > > To > "CAS Users Mailing List" <[EMAIL PROTECTED] <[email protected]>>, > "CAS Developers Mailing List" <[EMAIL PROTECTED]<[EMAIL PROTECTED]>>, > [EMAIL PROTECTED] <[EMAIL PROTECTED]> cc > Subject > CAS Server 3.3 Final Release > > > > > > > Dear CAS Community, > > We're pleased to announce the final release of CAS Server 3.3. CAS Server > 3.3 includes numerous bug fixes, enhancements, and new features including: > > Bug Fixes > * LDAP - support "/" in DNs > * Move all files that require Spring LDAP to the LDAP module > * Data too long for column in Services Management tool > * Properly escaping all example JSP pages > * Language fixes for German > * Properly populate meta data on re-authentication > > Enhancements > * Descriptions of all Spring configuration files > * Google Accounts Support upgrade to support latest Google Apps > * Requires Maven 2.0.9 to build > * Library upgrades including PersonDirectory 1.1.2, JBossCache 2, Spring > Security 2.0 and Inspektr 0.7.0 > * Transforming Principal names with SPNEGO > * Added Logging to JpaTicketRegistry > * Service Management Tool can ignore custom principals > > New Features > * RESTful API > * Memcached-backed Ticket Registry > * Terracotta Support > * Trusted LDAP module for trusted network clients > * Slovenian language support > * Support for Services Management via LDAP > > Thanks to everyone who reported bugs and helped test! > > You can download the entire release from our web site: * > http://www.ja-sig.org/products/cas/downloads/*<http://www.ja-sig.org/products/cas/downloads/> > > Some information on upgrading from CAS 3.2 to 3.3 can be found here: * > **http://www.ja-sig.org/wiki/display/CASUM/Upgrading*<http://www.ja-sig.org/wiki/display/CASUM/Upgrading> > > Thanks > -Scott > > -Scott Battaglia > PGP Public Key Id: 0x383733AA > LinkedIn: > *http://www.linkedin.com/in/scottbattaglia*<http://www.linkedin.com/in/scottbattaglia> > _______________________________________________ > Yale CAS mailing list* > [EMAIL PROTECTED] <[email protected]>* > **http://tp.its.yale.edu/mailman/listinfo/cas*<http://tp.its.yale.edu/mailman/listinfo/cas> > > > ********************************************************** > Privileged and/or confidential information may be contained in this > message. If you are not the addressee indicated in this message (or are not > responsible for delivery of this message to that person) , you may not copy > or deliver this message to anyone. In such case, you should destroy this > message and notify the sender by reply e-mail. > If you or your employer do not consent to Internet e-mail for messages of > this kind, please advise the sender. > Shaw Industries does not provide or endorse any opinions, conclusions or > other information in this message that do not relate to the official > business of the company or its subsidiaries. > ********************************************************** > > > _______________________________________________ > Yale CAS mailing list* > [EMAIL PROTECTED] <[email protected]>* > **http://tp.its.yale.edu/mailman/listinfo/cas*<http://tp.its.yale.edu/mailman/listinfo/cas> > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > > ********************************************************** > Privileged and/or confidential information may be contained in this message. > If you are not the addressee indicated in this message (or are not > responsible for delivery of this message to that person) , you may not copy > or deliver this message to anyone. In such case, you should destroy this > message and notify the sender by reply e-mail. > If you or your employer do not consent to Internet e-mail for messages of > this kind, please advise the sender. > Shaw Industries does not provide or endorse any opinions, conclusions or > other information in this message that do not relate to the official business > of the company or its subsidiaries. > ********************************************************** > > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
