[
https://issues.jboss.org/browse/JBIDE-13942?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-13942:
-------------------------------
Comment: was deleted
(was: Worse, even if I run Eclipse like this:
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/jbosstools-directory.xml
-Djboss.discovery.site.url=http://download.jboss.org/jbosstools/updates/requirements/atlassian/3.0.7.v20121218/
... it still finds the Atlassian 3.2 connector instead of the 3.0.7 one. It's as if
it's completely ignoring any value of *jboss.discovery.site.url* I pass in and only
looking into the value in the plugin, eg., to
http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/plugins...:
{code}siteUrl="${jboss.discovery.site.url:http://download.jboss.org/jbosstools/updates/development/kepler/central/core/}"
or
siteUrl="${jboss.discovery.site.url:https://devstudio.jboss.com/upda...
)
enable use of jboss.discovery.site.url & update doc accordingly
---------------------------------------------------------------
Key: JBIDE-13942
URL:
https://issues.jboss.org/browse/JBIDE-13942
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 4.1.0.Alpha2
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-a
Fix For: 4.1.0.Alpha2
* enable use of jboss.discovery.site.url in discovery plugins' plugin.xml files;
verify this works
* remove adjust.plugin.xml step in
https://github.com/jbosstools/jbosstools-discovery/blob/master/build.xml#... and update
user guide in that script
(should also fix paths in the examples after refactoring/migration to github)
* remove unzip/sed/zip steps to tweak plugins; instead only need use new commandline
flag; ensure release guide docs & email templates state this
--
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