[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611162#comment-13611162
 ] 

Jarek Gawor commented on GERONIMODEVTOOLS-795:
----------------------------------------------

Committed initial changes in revision 1459957. I added support for setting 
PortOffset in GEP and changes made to port information will be now saved into 
the config-substitutions.properties file (if the server is local). However, 
currently, the config-substitutions.properties will be read when a new server 
is created.
With these changes I also fixed a couple of problems in the server 
configuration editor: 1) I've improved undo functionality, 2) Fixed an issue 
where un-saved configuration properties could actually get used by GEP before 
they were actually saved or discarded, 3) Added basic validation to numeric 
fields, and 3) Increased published timeout to 4 hours.

                
> Synchronizing port configuration
> --------------------------------
>
>                 Key: GERONIMODEVTOOLS-795
>                 URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-795
>             Project: Geronimo-Devtools
>          Issue Type: Improvement
>          Components: eclipse-plugin
>    Affects Versions: 3.0-beta-1
>            Reporter: Jarek Gawor
>            Assignee: Jarek Gawor
>
> Currently, GEP keep its own port configuration, separate from the server's 
> configuration. The port information between GEP & server is not synchronized 
> in any way. And sometimes as the port information between the server & GEP 
> becomes out of synch, it creates problems for users when starting or 
> deploying modules to the server from GEP.
> It would be nice to update the GEP to keep the port information in synch with 
> the server. That is, if the server configuration is changed, that change is 
> reflected in GEP. And if the change in made in GEP, the server configuration 
> is updated as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to