[
https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13599:
------------------------------------
1. With nanohttpd server (above) still running, build Central from master
{code}
cd /home/nboldt/tru/jbosstools-central/
mvn clean install -DskipTests
{code}
2. Add these URLs to Eclipse, and install the Central Community feature
{code}
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
/home/nboldt/tru/jbosstools-central/site/target/repository
{code}
{code}
3. Shut down eclipse completely
4. Edit eclipse.ini file adding these under the -vmargs line
{code}
-Djboss.discovery.directory.url=http://localhost:8080/discovery/core/org.jboss.tools.central.discovery/target/discovery-site/jbosstools-directory.xml
-Djboss.discovery.site.url=http://localhost:8080/discovery/core/org.jboss.tools.central.discovery/target/discovery-site/
{code}
5. Start eclipse using -consolelog -debug
Same problem:
{code}
!ENTRY org.eclipse.mylyn.discovery.core 4 0 2013-03-13 14:47:30.362
!MESSAGE
org.jboss.tools.central.discovery_1.2.0.Alpha2-20130313-0625.jar_4413449892339815491.jar:
Invalid connectorDescriptor/@siteUrl
!STACK 1
org.eclipse.mylyn.internal.discovery.core.model.ValidationException: Invalid
connectorDescriptor/@siteUrl
at
org.eclipse.mylyn.internal.discovery.core.model.ConnectorDescriptor.validate(ConnectorDescriptor.java:228)
at
org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscoveryExtensionReader.readConnectorDescriptor(ConnectorDiscoveryExtensionReader.java:112)
at
org.eclipse.mylyn.internal.discovery.core.model.BundleDiscoveryStrategy.processExtensions(BundleDiscoveryStrategy.java:72)
at
org.eclipse.mylyn.internal.discovery.core.model.RemoteBundleDiscoveryStrategy.performDiscovery(RemoteBundleDiscoveryStrategy.java:198)
at
org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:115)
at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1510)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
!SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2013-03-13 14:47:30.362
!MESSAGE Invalid connectorDescriptor/@siteUrl
{code}
6.
externalize Central site URL into a commandline property so that
testing or mirroring is easier
-----------------------------------------------------------------------------------------------
Key: JBIDE-13599
URL:
https://issues.jboss.org/browse/JBIDE-13599
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Snjezana Peco
Fix For: 4.1.0.Alpha2
Attachments:
JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png,
JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt
As discussed in
https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&p...
testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard
when we're on an early Alpha and don't want bits to be public before they've
passed QE.
A better approach than having the update site URL used in Central's discovery
plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse
or JBDS. This would allow it to be overwritten/overridden should a user want to test
installation from a different URL than the default value.
This might even make it possible to have the same discovery plugin used for JBT and JBDS
(assuming the list of connectors were the same, and certification was to appear for both
instances) simply by having the preference changed to a different default URL when
installing JBT or JBDS BYOE.
--
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