Well, rtfm, I say to myself... item 6 in README.txt reads as follows: If building CAS from the source, running the test cases currently requires an active Internet connection. Please see: http://maven.apache.org/general.html#skip-test on how to disable the tests.
I'll have a look at the tests, and I might be able to help out with making them independent of a Internet connection and blocking firewalls, but I can't really promise anything at this point in time. Btw, congratulations to you and the team behind CAS! I've already recommended it as a great starting point for a real world project setup of Maven 2. Regards Bernd 2008/7/28 Scott Battaglia <[EMAIL PROTECTED]> > Bernd, > > Thanks for the feedback. I'm installing Maven 2.0.9 now to try it out. > > I'll take a look at some of the tests. For some, there's not much we can > do unless we want to run our own HTTP server with SSL (I suppose we could > run Jetty in embedded mode). > > If anyone has time and would like to rewrite the tests so they don't rely > on the real Internet, that would be great! In the meantime, we recommend > people who can't access the Internet due to things like a corporate firewall > disable the tests. > > Also, if you build your local application via the Maven WAR overlay method > (detailed in our Wiki), it pulls in the WAR file and the appropriate jars > but won't re-execute the CAS tests. > > Off to install Maven 2.0.9... ;-) > > -Scott > > -Scott Battaglia > PGP Public Key Id: 0x383733AA > LinkedIn: http://www.linkedin.com/in/scottbattaglia > > > On Fri, Jul 25, 2008 at 10:37 AM, Bernd Götz <[EMAIL PROTECTED]>wrote: > >> Hello CAS people >> >> First of all, I have been able to setup and run CAS 3.3-RC2 quite easily. >> I'm using the trusted mode setup to hook into an already existing SSO >> environment at the company I work at. >> >> Here are some observations from my initial build experiences: >> >> 1) Building CAS 3.3-RC2 fails with "strange" class loading issues >> (Spring?) using Maven 2.0.9. Using Maven 2.0.8 makes the class loader >> issues go away. I didn't look into this issue any further. Maven 2.0.9 seems >> to have introduced some changes that code like Spring does not like. >> >> 2) Building CAS 3.3-RC2 using Maven 2.0.8 and Sun JDK 1.6.0_07 on Windows >> fails: >> >> Tests run: 358, Failures: 6, Errors: 5, Skipped: 0 >> >> I guess this is because I'm running behind corporate firewalls, at least >> some of the tests can't connect to ldap servers in the Internet... These >> unit test classes fail: >> >> - SafeDispatcherServletTests: works from within Eclipse, but not on >> the command line. >> - CredentialsToLDAPAttributePrincipalResolverTests: connection to >> ldap://ldap1.rutgers.edu fails >> - GoogleAccountsServiceTests: >> java.security.spec.InvalidKeySpecException: Inappropriate key >> specification: >> IOException: algid parse error, not a sequence >> - AuthenticationManagerImplTests: connectivity issues >> - HttpBasedServiceCredentialsAuthenticationHandlerTests: connectivity >> issues >> - CentralAuthenticationServiceImplTests - ? >> - GoogleAccountsArgumentExtractorTests - ? >> - HttpClientTests: connectivity >> - RemoteCentralAuthenticationServiceTests >> - Cas20ProxyHandlerTests - connectivity >> - SafeContextLoaderListenerTests >> >> I propose to separate those tests out into a group of "integration test >> cases" or refactor the implementations and their corresponding tests to use >> local mockup tests, e.g. by using an embedded opends ldap server for the >> tests. But that's just loud thinking for the moment. >> >> Regards >> Bernd >> >> >> >> _______________________________________________ >> 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
