geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-3155) geronimo-tomcat6-minimal assembly has doubled in size from 17MB to 35MB in the past month
Date Wed, 16 May 2007 00:01:16 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496162
] 

Donald Woods commented on GERONIMO-3155:
----------------------------------------

Looking at leaving G3153 changes in (since ResourceRefBuilder.java needs the yoko-spec-corba
for the ORB class), removing the yoko depend from the minimal config.xml files and just adding
it to the JEE5 assemblies.
So far, this seems to be working.  The minimal Tomcat assembly is down to 17.5MB and I can
still deploy the Servlet-Examples to it without errors.  I'm still testing the JEE5 Tomcat
assembly with the EJB TCK bucket (Samples passed) to verify EJB resource-refs still work.
The only gotcha, may be trying to upgrade a minimal assembly to a full JEE5 assembly, may
require manually adding the yoko depend back into the defaultEnvironment for the connector-deployer
in config.xml, but I could never upgrade a 1.1.1 minimal to a full assembly, so this isn't
lost functionality....


> geronimo-tomcat6-minimal assembly has doubled in size from 17MB to 35MB in the past month
> -----------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-3155
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3155
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.0-M6
>            Reporter: Donald Woods
>         Assigned To: Donald Woods
>            Priority: Critical
>             Fix For: 2.0-M6
>
>
> Between 4/3 and 5/4, the size of the built minimal Tomcat zipfile has increased from
17MB to 34MB.
> The two changes to the minimal assemblies during that period were to include Jasper and
to include Yoko.
> Why are we including Yoko in the minimal assemblies???  Why do the builders need it?
> Do we need to create another unavailable deployer???
> Revision: 525586
> Author: jbohn
> Date: 3:24:18 PM, Wednesday, April 04, 2007
> Message:
> GERONIMO-3057 - include jasper into the minimal assemblies and make the jee5 assemblies
consistent wrt jasper
> ----
> Modified : /geronimo/server/trunk/assemblies/geronimo-jetty6-jee5/src/main/resources/var/config/config.xml
> Modified : /geronimo/server/trunk/assemblies/geronimo-jetty6-minimal/pom.xml
> Modified : /geronimo/server/trunk/assemblies/geronimo-jetty6-minimal/src/main/resources/var/config/config.xml
> Modified : /geronimo/server/trunk/assemblies/geronimo-tomcat6-jee5/src/main/resources/var/config/config.xml
> Modified : /geronimo/server/trunk/assemblies/geronimo-tomcat6-minimal/pom.xml
> Modified : /geronimo/server/trunk/assemblies/geronimo-tomcat6-minimal/src/main/resources/var/config/config.xml
> Revision: 535029
> Author: dblevins
> Date: 7:49:02 PM, Thursday, May 03, 2007
> Message:
> patch from jdmchugh that adds a dep on yoko as now the naming builders need it
> ----
> Modified : /geronimo/server/trunk/assemblies/geronimo-jetty6-minimal/pom.xml
> Modified : /geronimo/server/trunk/assemblies/geronimo-tomcat6-minimal/pom.xml

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message