[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-349.
--------------------------------------------
Resolution: Fixed
Hi Ashish, now I know why the 2nd scenario was working for you and BJ, but
failing for me. The reason it was not working for me was that the
org.apache.geronimo.st.core plugin was not getting activated. Having a server
defined in the workspace is not enough to activate this plugin. However, when I
created a new project in my workspace with the defined server as the target
runtime the plugin will get activated on GEP startup. So presumably, you and
BJ must have had something in your workspace causing the plugin to activate on
startup. As a matter of fact this is a good solution -- if there is nothing in
the workspace using the defined server as a target there is no reason to
synchronize with that server. Also, this is not a case where we want to violate
the lazy-start we use for all the GEP eclipse plugins. So, nice work and thanks
for the patch. Hopefully, you can work on more GEP JIRAs.
> GEP synchronization with a server running outside of Eclipse no longer works
> ----------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-349
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-349
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 2.1.0
> Reporter: Tim McConnell
> Assignee: Ashish Jain
> Fix For: 2.1.2
>
> Attachments: GERONIMODEVTOOLS-349.patch,
> GERONIMODEVTOOLS-349_updated.patch
>
>
> The GEP should synchronize with a Geronimo server running either inside of
> Eclipse or outside of Eclipse. It no longer works though when the server is
> started outside of Eclipse....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
