Re: [gatein-dev] Build Gatein WCI KO
For me having a build which fails by default in the middle of the
process his a really bad thing (like gatein portal). At least we
should add an enforcer rule to no start the build if the tomcat_home
env var isn't set. Another possibility is to use a profile which
activates this module only if the var is set.
Didn't you think to use cargo to avoid all those installations by
default ? It was creAted for that.
Arnaud
On Friday, November 13, 2009, Thomas Heute <theute(a)redhat.com> wrote:
We definitely need to keep Tomcat test. Since WCI is all about Web
Container integration.
It builds fine in our Hudson:
http://hudson.jboss.org/hudson/view/GateIn/job/gatein_wci_trunk_sun5_tomc...
On 11/13/2009 09:58 AM, Arnaud HERITIER wrote:
Hi,
For several days now, the build of WCI is KO :
http://builder.exoplatform.org/hudson/job/gatein-wci-trunk-ci/5/console
This is because the module "WCI
Tomcat 6 test component"
requires to have a local installation of Tomcat in ${env.TOMCAT_6_0_HOME} and actually I
don't have it.
Couldn't we deactivate this
part by default like it is possible in others gatein modules which
require TOMCAT or JBOSS for their integration tests.
Cheers
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net
_______________________________________________
gatein-dev mailing list
gatein-dev@lists.jboss.org <javascript:_e({}, 'cvml',
'gatein-dev(a)lists.jboss.org');>
https://lists.jboss.org/mailman/listinfo/gatein-dev
--
Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net