On Oct 22, 2009, at 4:01 PM, Christophe Laprun wrote:
Maven versions:set should perform validity check on the new version.
It's quite stupid to accept setting the version to a value you know is
not valid... So now I'm left trying to figure out what constitutes a
valid maven version… <sigh>
For reference:
http://mojo.codehaus.org/versions-maven-plugin/version-rules.html
Seems like it's actually a problem with exobuild, ultimately:
Result of /bin/sh -c cd /Users/claprun/Dev/gatein/portal/branches/wsrp-
integration/packaging/pkg && java -Dexo.package.home=/Users/claprun/
Dev/gatein/portal/branches/wsrp-integration/packaging/pkg/target/
exopackage -Dexo.current.dir=/Users/claprun/Dev/gatein/portal/branches/
wsrp-integration/packaging/pkg -Dexo.base.dir=null -Dexo.conf.dir=/
Users/claprun/Dev/gatein/portal/branches/wsrp-integration/packaging/
pkg/target/exopackage-conf -Dexo.working.dir=/Users/claprun/Dev/gatein/
portal/branches/wsrp-integration/packaging/pkg/target -Dexo.dep.dir=/
Users/claprun/Dev/exo-dependencies -Dexo.m2.repos=file:/Users/
claprun/.m2/repository,http://maven2.exoplatform.org/rest/maven2,http://r...
-Dclean.server=jboss-5.1.0.GA -Dexo.m2.home=/Users/claprun/Dev/
apache-maven-2.2.1 -Xshare:auto -Xms128m -Xmx512m -classpath /Users/
claprun/Dev/gatein/portal/branches/wsrp-integration/packaging/pkg/
target/exopackage/lib/js.jar org.mozilla.javascript.tools.shell.Main /
Users/claprun/Dev/gatein/portal/branches/wsrp-integration/packaging/
pkg/target/exopackage/javascript/eXo/eXo.js exobuild --product=portal
--deploy=jbossear execution is: '3'.
Cordialement / Best,
Chris
==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow JBoss Portal:
http://jbossportal.blogspot.com /
http://twitter.com/jbossportal
Follow me:
http://metacosm.codepuccino.com /
http://twitter.com/metacosm