geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sachin Patel (JIRA)" <>
Subject [jira] Commented: (GERONIMO-2324) Allow in-place and exploded jar support for sharedlib
Date Tue, 05 Sep 2006 18:51:24 GMT
    [ ] 
Sachin Patel commented on GERONIMO-2324:

Ok, so running a quick test it seems you can put absolute locations for both directories and
jars inside the manifest classpath entry even though the 1.4.2 jar specification seems to
say otherwise...

On comments above...

(1) Eclipse workspaces are much more flexible now days, and each of the actual project contents
can reside anywhere on the filesystem and the actual contents fo the workspace directory only
contain eclipse configuration metadata.  Also project stuctures can contain multiple outfolders
so this could get compilcated quickly.  I prefer to go down the dummy jar path and recycle
sharedlib as the dummy jar changes. 

> Allow in-place and exploded jar support for sharedlib
> -----------------------------------------------------
>                 Key: GERONIMO-2324
>                 URL:
>             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:
For more information on JIRA, see:


View raw message