I think we may want to setup some profiles to disable the minimal
assemblies by default, or at least allow the user to configure which
assemblies to build.
For most of my testing I only care about the jetty assembly, so
building the rest of them just slows things down.
--jason
On Jan 17, 2007, at 2:29 PM, [EMAIL PROTECTED] wrote:
Author: jdillon
Date: Wed Jan 17 14:29:18 2007
New Revision: 497213
URL: http://svn.apache.org/viewvc?view=rev&rev=497213
Log:
Build javaee assemblies first, leave minimal muck for afterwards
(so we can stop after one javaee assembly has been built)
Modified:
geronimo/server/trunk/assemblies/pom.xml
Modified: geronimo/server/trunk/assemblies/pom.xml
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/assemblies/
pom.xml?view=diff&rev=497213&r1=497212&r2=497213
======================================================================
========
--- geronimo/server/trunk/assemblies/pom.xml (original)
+++ geronimo/server/trunk/assemblies/pom.xml Wed Jan 17 14:29:18 2007
@@ -70,11 +70,11 @@
<modules>
<module>geronimo-boilerplate-minimal</module>
<module>geronimo-boilerplate-jee5</module>
+ <module>geronimo-jetty6-jee5</module>
+ <module>geronimo-tomcat6-jee5</module>
<module>geronimo-framework</module>
<module>geronimo-jetty6-minimal</module>
- <module>geronimo-jetty6-jee5</module>
<module>geronimo-tomcat6-minimal</module>
- <module>geronimo-tomcat6-jee5</module>
</modules>
</project>
