gotcha, thanks

On 10/23/07, Scott Battaglia <[EMAIL PROTECTED]> wrote:
>
> The two errors result from a few Google Accounts test cases that are
> dependent on specific Java versions (Sun decided to not include the required
> classes in certain JVMs on certain OSes).
>
> More info on Java versions can be found here:
> http://www.ja-sig.org/wiki/display/CASUM/Java+Versions
>
> The short version is that you can ignore those bad tests.  The above link
> has details on skipping tests.
>
> -Scott
>
> On 10/23/07, jashaffner <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > scott_battaglia wrote:
> > >
> > > We've put up a new release candidate of CAS 3.1.1 with a few minor
> > > changes.
> > > If anyone can test it to confirm that it works for them that would be
> > > great.  We are aiming for a final release by the end of this week so
> > we
> > > can
> > > start focusing on CAS 3.1.2.
> > >
> >
> > After checking out (svn) a repo, cd to 3.1.1 rc2 tag, and ran mvn
> > package,
> > should I disregard the two errors (below)?
> >
> > ****
> > Results :
> >
> > Tests in error:
> >
> > testResponse(
> > org.jasig.cas.authentication.principal.GoogleAccountsServiceTests)
> >
> > testWithGoogleAccountsService(
> > org.jasig.cas.web.flow.DynamicRedirectViewSelectorTests)
> >
> > Tests run: 393, Failures: 0, Errors: 2, Skipped: 0
> > --
> > View this message in context:
> > http://www.nabble.com/CAS-Server-3.1.1-Release-Candidate-2-tf4636093.html#a13368540
> > Sent from the CAS Users mailing list archive at Nabble.com.
> >
> > _______________________________________________
> > Yale CAS mailing list
> > [email protected]
> > http://tp.its.yale.edu/mailman/listinfo/cas
> >
>
>
>
> --
> -Scott Battaglia
>
> LinkedIn: http://www.linkedin.com/in/scottbattaglia
> _______________________________________________
> 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

Reply via email to