[
https://issues.jboss.org/browse/JBDS-2390?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2390:
-------------------------------------------
This is not just about discovery url.
There is multiple things that JBT dynamically fetchs/adjust for.
Non-exhaustive list is:
* list of project examples url's (done via plugins right now)
* download url for server (not sure how that is done now)
* central url
And yes, I think setting this up in a plugin should be done - but extension points
doesn't really work since if there are multiple of these - who wins ?
Thats why we've used the system property for now - since its global.
I was considering if we could simply just add to jbds central plugin an explict system
property override in case the system property is not set already.
This would allow testing/QE to still override it.
How to customize JBT to be like JBDS
------------------------------------
Key: JBDS-2390
URL:
https://issues.jboss.org/browse/JBDS-2390
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: central
Reporter: Mickael Istria
Assignee: Snjezana Peco
Fix For: 6.1.0.Alpha1
In JBDS, we override the discovery.url to set it to the value for JBDS extras site.
However, this is done by hacking system properties. Instead, we could think of using the
"discoveryProviderUrl" extension point in JBT.
JBT would provide an extension to define this URL.
JBDS would provide another extension to define this URL.
Changing URL happens by updating the extension plugin.
So JBT and JBDS would behave the same way when dealing with discovery, and we remove the
system properties settings from JBDS. System proprty would still be available for testing
only.
--
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