[ http://issues.apache.org/jira/browse/GERONIMO-2324?page=comments#action_12432835 ] Sachin Patel commented on GERONIMO-2324: ----------------------------------------
Also, I've come to the realization that this support is only valuable if you have jars/projects that only provide runtime dependencies and not compile time dependencies and that your projects are configured NOT to have explicit references to these runtime dependencies. If you projects are set up to always have references to "shared-lib" projects and jars regardless of their dependency type (runtime/compile) then this support is reduntant and the support for running resources out of the workspace (GERONIMO-1526) will automatically provide this support. Please clarrify on you configuration specifically on wether or not your web apps reference all shared-lib projects and jars. > 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, 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
