[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-99?page=all ]
Sachin Patel closed GERONIMODEVTOOLS-99.
----------------------------------------
Resolution: Fixed
fixed in head. Option is now available in sever editor "enable in place shared
lib" in which for a given project being deployed, any jars on the build path or
referenced projects that are not configured to be packaged as web-inf libraries
or utility jars inside the application are deployed "in-place" to the shared
library.
> need to publish web project dependencies outside of WAR
> -------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-99
> URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-99
> Project: Geronimo-Devtools
> Issue Type: Improvement
> Components: eclipse-plugin
> Affects Versions: 1.1.0
> Environment: IBM Java 1.5, Eclipse 3.2.0, WTP 1.5, w2k/w3k, 32/64 bit
> Reporter: Oleg Gusakov
> Assigned To: Sachin Patel
> Priority: Blocker
> Fix For: 1.x
>
>
> In our use case for geronimo plugin we need to be able to deploy WAR project
> dependencies outside of WAR. The best place seems to SharedLib deployer.
> Dependencies to deploy include:
> - Eclipse WAR project references to other Eclipse projects
> - external JAR files, attached to the project and/ot it's dependencies
> - external dependencies supplied by Maven plugin from project's POM file.
> This is almost identical to the previous one.
> All dependencies need to be deployed "in place" for efficiency reasons.
> Binary dependencies do not change often and can reside in one classloader.
> Eclipse projects, on the other hand, change a lot and could be subjected to
> hot redeployment, so they probably should reside in their own set of
> classloaders.
> Please consider for implementation.
--
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
