Hi Jesse,
Thanks for the response.
I see what's going on. JPP's 2.07 is revision -9, dated march of 2009,
which probably contains all kinds of fixes backported from later
versions of maven - classic enterprise-style version control.
I'll edited the version in the pom to be 2.0.7.
It now builds with one fatal error, which I don't understand:
-------------------------------------------------------------------------------
Test set:
org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandlerTests
-------------------------------------------------------------------------------
Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.146
sec <<< FAILURE!
testAcceptsProperCertificateCredentials(org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandlerTests)
Time elapsed: 0.25sec <<< FAILURE!
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertTrue(Assert.java:27)
at
org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandlerTests.testAcceptsProperCertificateCredentials(HttpBasedServiceCredentialsAuthenticationHandlerTests.java:39)
Is this something simple?
Brian
On 3/8/2010 7:31 PM, Jesse Farinacci wrote:
Brian,
On Mon, Mar 8, 2010 at 9:20 PM, Brian Hill<[email protected]> wrote:
Can maven 2.07 not be used?
[INFO] [enforcer:enforce {execution: enforce-versions}]
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireMavenVersion failed
with message:
Detected Maven Version: 2.0.7 is not in the allowed range 2.0.9.
I'd like to use 2.07 because that's the rpm version from JPP.
Brian
2.0.7 was released in June of 2007, that's nearly 3 years behind the
curve. I find it hard to believe JPP hasn't released a more current
level of Maven, especially given the HUGE number of bug fixes between
2.0.7->2.0.11. People should have exceptional reasons for running less
than 2.2.1, frankly speaking.
If you insist, however, you could quite easily edit the pom and
comment out the enforcer rule for requiring maven 2.0.9+ .... You
deserve whatever punishments are bestowed upon you though.
-Jesse
--
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
