<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, 5:10 PM, Brent Putman
wrote:<br>
</div>
<blockquote cite="mid:53AB3ADD.1040503@georgetown.edu" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
<div class="moz-cite-prefix">On 6/25/14, 3:16 PM, Brent Putman
wrote:<br>
</div>
<blockquote cite="mid:53AB2002.9040008@georgetown.edu" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
The v3 parent, java-support and spring-extensions are done.
Started working on opensaml.<br>
</blockquote>
<br>
OpenSAML is done now too and in Nexus. It took awhile b/c I did a
full test build first with all the POM changes, before I did the
real deployed one. <br>
</blockquote>
<br>
Btw, I had not ever done a multi-module project deploy before. I
guess in hindsight this is expected, but with a multi-module project
it of course deploys each module to the repo as it builds each one,
including signing, etc (as opposed to doing them all at the end or
something). I didn't have any problems, but since OpenSAML takes 40
minutes to build on my machines, I was mildly worried what would
happen if the network, repo server, etc went down in the middle of
the process. I'm hoping/expecting it could be started back up where
it left off using the Maven "continue from module X" switch (which
escapes me at the moment).<br>
<br>
I was also pleasantly surprised that it prompts for the GPG signing
key passphrase on the first module and then remembers it for all the
others. I thought you might have to sit there and re-enter it for
each one.<br>
<br>
</body>
</html>