Steps to ship?
Brent Putman
putmanb at georgetown.edu
Wed Jun 25 15:16:18 EDT 2014
On 6/25/14, 1:55 PM, Cantor, Scott wrote:
>> It will take me a little while to start. Having some minor machine
>> problems at the moment after upgrading my machine to Mavericks
>> yesterday.
> Probably a good idea to cross-check against the release process page too to make sure it's accurate and current, I don't know what state that's in. I think we updated it when we did the 2.4.0 release, but I guess this is the first "real" runthrough of the steps for the whole V3 stack.
The v3 parent, java-support and spring-extensions are done. Started
working on opensaml.
I think I've hit upon the first hiccup for the v3 multi-module
projects. I don't think we currently have any scripts, etc to automate
updating the version of the project -parent in each of the modules. For
example each module has:
<parent>
<groupId>org.opensaml</groupId>
<artifactId>opensaml-parent</artifactId>
<version>3.0-SNAPSHOT</version>
<relativePath>../opensaml-parent</relativePath>
</parent>
Needs to be 3.0.0-alpha1, for example.
So I guess I'll do it manually for now.
Since there are a whole lot of POM's, it's also necessary to be careful
and make sure to check/update each one to remove references to things
like SNAPSHOT versions of dependencies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20140625/5617d9a1/attachment.html
More information about the dev
mailing list