I'm afraid this is going to open a bag of worms....There are a group of people only interested in Jetty, but another only interested in Tomcat (like myself). What happens when we come to the decision of cxf vs. axis2? Do we create 8 different profile options to build only the assembly you want? How do we ensure that Tomcat only developers don't break the builds for Jetty only developers, unless we always build all of the assemblies???
-Donald Jason Dillon wrote:
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.xmlURL: 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>
smime.p7s
Description: S/MIME Cryptographic Signature
