Trying to reproduce this, I get the a license check failure:
[ERROR] Failed to find Licenses for the following dependencies:
[ERROR] log4j:log4j:jar:1.2.17:compile
[ERROR] velocity:velocity:jar:1.5:compile
[ERROR] Try adding them to a 'licenseMapping' file.
[ERROR] A stub license-mapping.xml file containing the unresolved
dependencies has been written to:
/home/ohsied/src/cas/target/license-mappings.xml
Is that expected?
From: Ohsie, David [mailto:[email protected]]
Sent: Friday, July 05, 2013 1:11 PM
To: [email protected]
Subject: RE: [cas-dev] Status of 4.0.0-RC1 Release
In my experience, running a release build is a whole different ballgame with
recursive mvn invocations and such..
From: Stephen More [mailto:[email protected]]
Sent: Friday, July 05, 2013 12:49 PM
To: [email protected]
Subject: Re: [cas-dev] Status of 4.0.0-RC1 Release
For what it is worth, I did a:
git clone https://github.com/Jasig/cas.git
git checkout tags/v4.0.0-RC1
mvn install
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
------------------------------------------------------------------------
[INFO] Jasig Central Authentication Service .................. SUCCESS
[3.933s]
[INFO] Jasig CAS Core ........................................ SUCCESS
[1:02.173s]
[INFO] Jasig CAS Generic Support ............................. SUCCESS
[2.377s]
[INFO] Jasig CAS Web Application support ..................... SUCCESS
[16.874s]
[INFO] Jasig CAS Web Application ............................. SUCCESS
[8.843s]
[INFO] Jasig CAS JDBC Support ................................ SUCCESS
[1.305s]
[INFO] Jasig CAS Legacy Support .............................. SUCCESS
[1.823s]
[INFO] Jasig CAS LDAP Support ................................ SUCCESS
[3.201s]
[INFO] Jasig CAS OpenId Server Support ....................... SUCCESS
[6.320s]
[INFO] Jasig CAS RADIUS Support .............................. SUCCESS
[1.541s]
[INFO] Jasig CAS SPNEGO/NTLM Support ......................... SUCCESS
[4.066s]
[INFO] Jasig CAS Trusted User Support ........................ SUCCESS
[2.546s]
[INFO] Jasig CAS X.509 Client Certificate Support ............ SUCCESS
[4.757s]
[INFO] Jasig CAS OAuth Server Support ........................ SUCCESS
[3.495s]
[INFO] Jasig CAS Client Protocols Support using pac4j ........ SUCCESS
[2.631s]
[INFO] Jasig CAS SAML Server and Validation Support .......... SUCCESS
[5.266s]
[INFO] Jasig CAS JBoss Cache Integration ..................... SUCCESS
[21.806s]
[INFO] Jasig CAS Memcached Integration ....................... SUCCESS
[3.289s]
[INFO] Jasig CAS Ehcache Integration ......................... SUCCESS
[3.955s]
[INFO] Jasig CAS Restlet Integration ......................... SUCCESS
[1.413s]
[INFO] Jasig CAS - Uber WAR .................................. SUCCESS
[7.444s]
[INFO] Jasig CAS Documentation ............................... SUCCESS
[0.127s]
[INFO] Jasig CAS ClearPass Extension ......................... SUCCESS
[3.738s]
[INFO] Jasig CAS Management Web Application .................. SUCCESS
[9.019s]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 3 minutes 2 seconds
[INFO] Finished at: Fri Jul 05 12:44:56 EDT 2013
[INFO] Final Memory: 324M/612M
[INFO]
------------------------------------------------------------------------
$ mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_43
Java home: /home/smore/jdk1.6.0_43/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "3.2.0-48-generic" arch: "amd64" Family: "unix"
-Steve
On Fri, Jul 5, 2013 at 12:23 PM, Marvin S. Addison
<[email protected]> wrote:
1) Are you using the right version of maven? Sometimes an upgrade solves
strange problems. Does cas use maven 2.x or 3.x?
Don't think there's an official standard; it's simply whatever the core devs
use, which is 3.x. I'm using 3.0.4, so no issue there.
2) Are you passing in the "-s" flag to get a specfic settings.xml file?
Nope. I've done the release process several times now using the following
instructions without incident:
https://wiki.jasig.org/display/CAS/Release+Process
This time it's proving to be a major pain point for multiple folks.
M
--
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-dev
--
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-dev
smime.p7s
Description: S/MIME cryptographic signature
