I haven't requested the CI move to Maven yet (was awaiting responses
from teammates), but will do so now, so we don't keep getting emails
about ant clean dist failing. That said, the fact we're doing to mvn
clean install on CI shouldn't mean you have rush to merge it all
together as I believe it's OK (?) for mvn clean install to just generate
an unsigned WAR for a few days. If not, we'll find out, and we'll just
get failure emails on the Ant build for some days (no big deal) until
build@ lets us switch to Maven.
Glen
On 05/23/2013 04:55 AM, Juan Pablo Santos RodrÃguez wrote:
Hi,
mvn_branch currently has defined maven-gpg-plugin, which signs generated
artifacts only via mvn gpg:.... However, we should have a "deploy" profile
which generates binaries, sources, javadocs and sign all them so we can mvn
deploy -Dgpg.passphrase and have all done
As we're doing mvn clean install on CI (or at least requested it) I'll try
to sync mvn_branch with current trunk (tomorrow?)tonight, so we can perform
the clean move to multimodule
br,
juan pablo
On Thu, May 23, 2013 at 6:18 AM, Glen Mazza <glen.ma...@gmail.com> wrote:
Hi all, I managed to shrink our build.xml about 35% today. For everything
up to a WAR, now use the Maven script, for you have no choice anymore. :)
I have a few loose ends I could clean up further in the build.xml (moving
Cobertura from MVN3 to trunk comes to mind), but we're basically ready for
JP to propagate his Selenium and multi-module design on trunk (which is
good because I could use some time off.)
Question for JP: We have a lot of JAR-signing stuff remaining in our
build.xml, is what you have on MVN3_Branch good enough to get rid of it?
(I guess I can leave it in the Ant file and just wait for you to move the
MVN3 stuff to trunk.)
Regards,
Glen
