[
https://issues.apache.org/jira/browse/GERONIMO-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634779#action_12634779
]
David Jencks commented on GERONIMO-4318:
----------------------------------------
I added some tracking for plugins installed into a particular server in rev
699202, but didn't test the effects on the console. The change doesn't appear
to cause the problems seen with the previous attempt.
> 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
>
>
> 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.
