Can you post the failure reasons? I just found running on Maven3 with some of the tests caused a few issues (the multithreading of tests seemed to cause some problems)
On Mon, Mar 21, 2011 at 11:32 AM, Rob Chevalier <[email protected]> wrote: > > > > My guess is that the POMs haven't been updated to Maven3. > > > > Use Maven 2.2.1 until M3 support has been verified. > > > > cheers, > > Steve > > > > > > > Warnings shouldn't be preventing it from building so you should be able > to > > ignore them. > > > > That said, if you open a JIRA issue for it, we'll update our poms :-) > > > > Thanks > > Scott > > > > Thank you, Steve and Scott! > > I attempted to update pom.xml on my end for Maven3 but the core server > still > failed to build. Rolling Maven back to 2.2.1 and starting the CAS build > over again was much less painful and the baseline war file built fine. > Thank you for the suggestion! > > Cheers, > > Rob Chevalier > > -- > View this message in context: > http://jasig.275507.n4.nabble.com/CAS-Build-Warning-with-Maven-3-0-3-tp3388373p3394382.html > Sent from the CAS Users mailing list archive at Nabble.com. > > -- > 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
