You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Joe Bohn (JIRA)" <de...@geronimo.apache.org> on 2006/02/09 04:08:00 UTC
[jira] Updated: (GERONIMO-1613) Eliminate unncessary dependencies
to reduce assemnbly footprint size
[ http://issues.apache.org/jira/browse/GERONIMO-1613?page=all ]
Joe Bohn updated GERONIMO-1613:
-------------------------------
Attachment: RemoveDeps.patch
Patch created in win-XP from geronimo root directory.
I verified that I could start all server configs, access the console, and deploy a web application with these changes. This isnt't the most extensive test ... so I hope that these changes don't cause any problems in other scenarios.
> Eliminate unncessary dependencies to reduce assemnbly footprint size
> --------------------------------------------------------------------
>
> Key: GERONIMO-1613
> URL: http://issues.apache.org/jira/browse/GERONIMO-1613
> Project: Geronimo
> Type: Improvement
> Components: general
> Versions: 1.1
> Environment: all
> Reporter: Joe Bohn
> Fix For: 1.1
> Attachments: RemoveDeps.patch
>
> Clean up assembly project.xml and eliminate some unnecessary dependencies in various modules and configs. This will reduce the footprint size (with special attention to the minimal-tomcat-assembly.
> The patch contains the following:
> - clean up minimal-tomcat-server\project.xml to remove commented out sections
> - clean up web-jms-tomcat-server\project.xml to remove commented out sections
> - remove dependencies from config\j2ee_server on xstream, jaxr-api, and geronimo-derby
> - remove dependencies from config\j2ee_deployer on geronimo-client-builder
> - remove dependencies from module\tomcat on activecluster, wadi-core, and wadi-tomcat55
> There are still more dependencies that should be removed but this is a start.
> These changes reduce the disk footprint of minimal-tomcat-server from 27 meg to about 21 meg.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira