[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612893#action_12612893
]
Ted Kirby commented on GERONIMODEVTOOLS-235:
--------------------------------------------
As stated, I do not think this is a good idea. If you are going to read
configuration info from the server, I'd get all of it, not part of it. So, you
should get rid of the manual GEP step of specifying the two ports. We have
always had this manual step, and reading the server config would be a
departure. I presume you'd just take server code. How much would be involved,
and what additional jars would be required for parsing and calculating the
server configuration? We must also consider the remote server case. I don't
think reading a remote server configuration will work out. Do you want to
treat the remote server config case differently? Is the advantage gained from
proposed change worth the effort and change in approach? Does anyone recall
the rationale for the current manual configuration approach in GEP? Are there
any issues being missed in changing from that approach?
> Plugin cannot synchronize with the server when non-zero portOffset value in
> the config-substitutions.properties file
> --------------------------------------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-235
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-235
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 2.0.0
> Reporter: Tim McConnell
> Assignee: Ashish Jain
> Fix For: 2.1.x
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
