[ http://issues.apache.org/jira/browse/GERONIMO-2324?page=comments#action_12428429 ] Paul McMahan commented on GERONIMO-2324: ----------------------------------------
I agree this is an important feature, I would use this in Eclipse all the time. The patch didn't apply cleanly for me on branches/1.1: bash-3.1$ patch -p0 < ../patches/GERONIMO-2324.patch patching file configs/sharedlib/src/plan/plan.xml patching file modules/system/src/java/org/apache/geronimo/system/sharedlib/SharedLib.java Hunk #1 FAILED at 16. 1 out of 3 hunks FAILED -- saving rejects to file modules/system/src/java/org/apache/geronimo/system/sharedlib/SharedLib.java.rej bash-3.1$ Also, I'm wondering if adding the external jars via SharedLib is ideal since as I understand it SharedLib makes the classes available server wide and this might cause complications when two applications in the development environment want to use different versions of an external jar. But maybe I am misunderstanding SharedLib . Could the Eclipse plugin add the external dependencies into the application's MANIFEST.MF instead? Might be cleaner since it's application specific. One more question :-) What happens when the application is exported from Eclipse? Are the external references exported somehow or is that left to be resolved later at deployment time? > Allow in-place and exploded jar support for sharedlib > ----------------------------------------------------- > > Key: GERONIMO-2324 > URL: http://issues.apache.org/jira/browse/GERONIMO-2324 > Project: Geronimo > Issue Type: RTC > Security Level: public(Regular issues) > Components: deployment > Affects Versions: 1.1 > Reporter: Sachin Patel > Assigned To: Sachin Patel > Fix For: 1.x > > Attachments: GERONIMO-2324.patch > > > The shared library support should allow in-place support to allow and load > jars (exploded as well) that are located externally on the filesystem. This > is needed to improve developer experience and allow better integration within > tooling and the runtime. > Perhaps we can have a properties file insie the shared lib that have external > entries in them. -- 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
