Hmmm, a honest answer is I don't know. :-)
This was done in one of those 4am times before Beta3 release.
We could do one of the three.
1) Since SpringDeployer now actually has tests, we can include it in all
distr
2) Disable these tests
3) Enable them only for 'spring' profile of AS
Thinking about it now, I though (3) was the case, but the link proves me
wrong.
Adrian Brock wrote:
Why are we running tests against the spring deployer
in the base testsuite:
http://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/475/tes...
when the spring deployer is commented out of the build?
build-distr.xml
<target name="_module-spring-int-most">
<property name="_module.name" value="spring-int"
override="true"/>
<property name="_module.output" override="true"
value="${project.root}/${_module.name}/output"/>
<!-- Uncomment this if you want jboss-spring.deployer in all
configration -->
<!--
<mkdir dir="${install.server}/all/deploy/jboss-spring.deployer"/>
<unjar src="${_module.output}/lib/jboss-spring.deployer"
dest="${install.server}/all/deploy/jboss-spring.deployer"/>
-->
</target>