[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526477
]
Tim McConnell commented on GERONIMODEVTOOLS-202:
------------------------------------------------
Hi Shiva, I share your concern as well, but I'm not sure you have too much of a
choice at this point. One thing though that you should consider is to just give
it the top-level directory of the path and let the plugin search and find the
jarfile. That's how I tried to mitigate the similar situations in
GeronimoServerRuntimeTargetHandler. One advantage of this approach is that your
code shouldn't have to be changed again when a new version of the Server is
introduced, assuming of course that the main geroimo-server path remains the
same, which is probably a good assumption. Plus, of course you don't have to
hardcode the name of the jarfile. Thanks.
> "A geronimo installation was detected, however the version could not be
> verified" warning while adding Geronimo 2.0.1
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-202
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-202
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 2.0
> Reporter: Shiva Kumar H R
> Assignee: Tim McConnell
> Priority: Minor
> Fix For: 2.0
>
> Attachments: GERONIMODEVTOOLS-202-temp.patch
>
>
> Initial debugging shows that this is due to:
> org.apache.geronimo.st.core.GeronimoRuntimeDelegate.detectVersion() method
> returning null, which in turn is due to missing "geronimo-system-*.jar" file
> in <GERONIMO-HOME>\lib directory of Geronimo 2.0.1 installation.
> geronimo-system-2.0.1.jar can however be found
> "<GERONIMO-HOME>\repository\org\apache\geronimo\modules\geronimo-system\2.0.1"
> directory of AG 2.0.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
