[ 
http://issues.apache.org/jira/browse/GERONIMO-2324?page=comments#action_12432657
 ] 
            
Sachin Patel commented on GERONIMO-2324:
----------------------------------------

Oleg.. 

Could you clarrify what you are doing in the following situation currently???

Lets say you have a single project, WebProject-A in your workspace.  This 
project has a classpath reference to an external jar foo.jar (which in 
production gets copied to the sharedlib.

Now lets say you want to make modifcations to foo.jar and you import foo.jar 
into your workspace as project Foo.  What are you doing with the classpath 
reference on WebProject-A to Foo.jar? Are you currently manually deleting it 
and replacng it with a project reference to project Foo?

I see a problem in this especially if you are keeping your .project and 
.classpath file's under source control.  Is this the case? If so then people 
could accidentally commit these and the next person who checks out the code 
would have a .classpath reference to a non existent project.  This is 
dangerous.  How do you plan to address this?

> 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

        

Reply via email to