<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 6/25/14, 1:55 PM, Cantor, Scott
wrote:<br>
</div>
<blockquote
cite="mid:BA63CEAE152A7742B854C678D9491383CA316039@CIO-KRC-D1MBX01.osuad.osu.edu"
type="cite">
<blockquote type="cite">
<pre wrap="">It will take me a little while to start. Having some minor machine
problems at the moment after upgrading my machine to Mavericks
yesterday.
</pre>
</blockquote>
<pre wrap="">
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.
</pre>
</blockquote>
<br>
The v3 parent, java-support and spring-extensions are done. Started
working on opensaml.<br>
<br>
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:<br>
<br>
<tt> <parent></tt><tt><br>
</tt><tt> <groupId>org.opensaml</groupId></tt><tt><br>
</tt><tt>
<artifactId>opensaml-parent</artifactId></tt><tt><br>
</tt><tt> <version>3.0-SNAPSHOT</version></tt><tt><br>
</tt><tt>
<relativePath>../opensaml-parent</relativePath></tt><tt><br>
</tt><tt> </parent></tt><br>
<br>
<br>
Needs to be 3.0.0-alpha1, for example.<br>
<br>
So I guess I'll do it manually for now. <br>
<br>
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.<br>
<br>
<br>
</body>
</html>