[
https://issues.jboss.org/browse/JBIDE-10334?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-10334:
---------------------------------------
snjezana - so reading the patch looks like the problem was the
refactoring into a "default configurator" caused this bug and this patch fixes
it.
You are right.
But I guess once there is more than one possible setup the logic for
this would need to be copied or extracted out. but that is for after M5.
I suppose you are talking about Nick's proposal to define a discovery url using
*.properties file instead of a hard coded url in the configurator. Do we need to create a
new jira?
system property option for configuring central discovery has
dissappeared
-------------------------------------------------------------------------
Key: JBIDE-10334
URL:
https://issues.jboss.org/browse/JBIDE-10334
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: central
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.Beta1
Attachments: jbide-10334.patch
before we could set a system property to test against a local discovery xml - that is not
working anymore so one have to change and rebuild code to test.
That's very inefficient, bring it back please.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira