I'm at my wits end - I just can't get the release process to work using the normal release plugin process as documented (https://cwiki.apache.org/confluence/display/SHIRO/Performing+a+Release). This has always worked in all other previous releases. I don't know what makes the 1.2.1 poms different.
mvn release:prepare works mvn release:perform fails when it gets to the support/web module. I'm too frustrated and tired to debug further (I've tried everything from different Maven versions to upgrading plugin versions to latest stable, etc - all to no effect). Can someone (Kalle?) take a look and figure out why this may be the case? For now, I'm just doing a manual checkout of the 1.2.1 tag (created successfully during mvn release:prepare) and calling mvn deploy -Pdocs,apache-release. At least this will give us voteable artifacts. If I'm lucky site-deploy will work without problems too. They just don't work together in the context of the release plugin. Regards, -- Les Hazlewood | @lhazlewood CTO, Stormpath | http://stormpath.com | @goStormpath | 888.391.5282 Stormpath wins GigaOM Structure Launchpad Award! http://bit.ly/MvZkMk On Tue, Jul 24, 2012 at 8:45 PM, Les Hazlewood <[email protected]> wrote: > After blowing 5 hours on trying to release today, I've finally found that: > > 1) The RAT plugin is _terrible_ about indicating why something failed. > 2) Our build passed on mvn apache-rat:rat but _not_ on apache-rat:check > > I couldn't figure out for the life of me why things all built > beautifully, apache-rat:rat worked, but the build continually failed > during release only, especially after we put apache-rat:rat in our > release <preparationGoals/> section. The build output, even when > using the -X (debug) and -e options didn't say _anything_ as to why > the build failed. > > On a gut feeling, I decided to try apache-rat:check instead of > apache-rat:rat, and that finally found the culprit: the > DomainPermissionTest.java class did not have an ASL header. > > As a security measure to prevent this again, I'm going to change > preparation goals and our CI server config to use apache-rat:check > instead so we can catch this in the future. > > Just a friendly reminder: please configure your IDE to use a copyright > plugin to update file headers when working within Apache projects :) > > Ok, now that I know what's going on, I should be able to start a vote > fairly soon. Yay! :) > > Cheers, > > -- > Les Hazlewood | @lhazlewood > CTO, Stormpath | http://stormpath.com | @goStormpath | 888.391.5282 > Stormpath wins GigaOM Structure Launchpad Award! http://bit.ly/MvZkMk
