[
http://jira.jboss.com/jira/browse/JBAS-2617?page=all ]
Dimitris Andreadis updated JBAS-2617:
-------------------------------------
Component/s: EJB3
(was: EJB2)
(was: Build System)
Assignee: Carlo de Wolf (was: Bill Burke)
Assign to Carlo.
ej3.deployer contains too many jars
-----------------------------------
Key: JBAS-2617
URL:
http://jira.jboss.com/jira/browse/JBAS-2617
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: EJB3
Reporter: Scott M Stark
Assigned To: Carlo de Wolf
There are numerous duplicate and seemingly unused jars in the current ejb3.deployer:
[starksm@banshee9100 jboss-4.0]$ ls build/output/jboss-4.0.4beta/server/default
/deploy/ejb3.deployer/
META-INF/ commons-lang-1.0.jar*
antlr-2.7.5H3.jar* commons-logging.jar*
asm-attrs.jar* commons-pool.jar*
asm.jar* dom4j.jar*
cglib-2.1.1.jar* ejb3-persistence.jar*
commons-beanutils.jar* hibernate-annotations.jar*
commons-codec-1.2.jar* hibernate-entitymanager.jar*
commons-collections.jar* hibernate3.jar*
commons-digester-1.6.jar* jaxen-1.1-beta-4.jar*
commons-discovery.jar* jboss-annotations-ejb3.jar*
commons-fileupload.jar* jboss-ejb3.jar*
commons-httpclient.jar* jboss-ejb3x.jar*
Why all these are needed and which ones should be factored out into the server lib
directory need to be defined. There needs to be a distinction between the ejb3.deployer
bundled in the app server vs a standalone bundle for installing into earlier releases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira