geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lin Sun (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (GERONIMO-4318) All the plugins are marked as installable on the install plugins portlet
Date Wed, 08 Oct 2008 14:49:44 GMT

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

Lin Sun resolved GERONIMO-4318.
-------------------------------

    Resolution: Fixed

See subversion commits.  Many thanks to David Jencks for making changes that work for the
farm scenario.

Currently plugin groups and regular plugins (that are added to the config) are all tracked
correctly.    There are one minor issue:
plugin that doesn't get added to configuration, such as boilerplate and jaxws-tools are marked
as installable even if they are already installed.  I am not sure the best way to solve this
(is there an easy way to detect these type of geronimo plugins?  I know for c-m-p it is easy
as it just detect if it has plan.xml file).




> All the plugins are marked as installable on the install plugins portlet
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-4318
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4318
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console
>    Affects Versions: 2.2
>            Reporter: Lin Sun
>            Assignee: Lin Sun
>             Fix For: 2.2
>
>         Attachments: G4318.patch
>
>
> All the plugins are marked as installable on the install plugins portlet.   We check
if a plugin is installable by using pluginInstaller.validatePlugin.   If an exception is thrown,
then we set the installable to false.   The throw of MissingDependencyException in validatePlugin
method is commented out during rev 696105.
> A proposed fix is to throw ConfigurationAlreadyExistsException when validatePlugin fails
because of the configuration is already installed.   This seems more reasonable and will also
get rid of the confusion message of "Missing Dependency: XXX" when a user attempts to install
a plugin that has already been installed using the "deploy install-plugin" command.

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


Mime
View raw message