You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Shawn Jiang (JIRA)" <ji...@apache.org> on 2009/11/24 08:30:39 UTC

[jira] Commented: (GERONIMO-4912) Should plugins be packed jar files or exploded?

    [ https://issues.apache.org/jira/browse/GERONIMO-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781809#action_12781809 ] 

Shawn Jiang commented on GERONIMO-4912:
---------------------------------------

Currently, some API that assumes car are exploded are not working well because car are packed in Geronimo 3.0.   Some of them are:

RepositoryConfigurationStore.listConfigurations()
ExecutableConfigurationUtil.writeConfiguration(ConfigurationData, File)
RepositoryConfigurationStore.createNewConfigurationDir(Artifact)


Which are keeping me from migrating some of deployer shell commands.

> Should plugins be packed jar files or exploded?
> -----------------------------------------------
>
>                 Key: GERONIMO-4912
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4912
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: osgi
>    Affects Versions: 3.0
>            Reporter: 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.