Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <21563900.85281283218975580.JavaMail.jira@thor>
Date: Mon, 30 Aug 2010 21:42:55 -0400 (EDT)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Closed: (GERONIMO-4912) Should plugins be packed jar files
 or exploded?
In-Reply-To: <1586737249.1255715431357.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/GERONIMO-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed GERONIMO-4912.
----------------------------------

    Resolution: Invalid

I haven't heard of problems recently so think this is working ok.

> Should plugins be packed jar files or exploded?
> -----------------------------------------------
>
>                 Key: GERONIMO-4912
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4912
>             Project: Geronimo
>          Issue Type: Sub-task
>      Security Level: public(Regular issues) 
>          Components: osgi
>    Affects Versions: 3.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.0
>
>
> Currently the osgi framework only works with plugins packed as jar files, not exploded jar files like the regular geronimo server.  Since osgi can deal with classpaths inside a  jar file, I rather think that we should proceed with this as standard practice for the rest of the server.  However this will mean moving the archiving functionality out of the car-maven-plugin and into the deployer.
> The alternative is to make sure that unpacked plugins actually work in osgi.  I didn't experiment with this at all.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.