[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
12:37 p.m.
[
https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-13599 at 3/13/13 1:37 PM:
-------------------------------------------------------------
Does not appear to be working.
Steps to repro:
1. Build JBDS 7 locally from trunk.
{code}
cd ~/devstudio/trunk/product
mvn clean install -P
maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate
{code}
2. Apply this patch:
[^JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt]
3. Build discovery plugins locally from trunk (with patch).
{code}
cd ~/devstudio/trunk/product/discovery
mvn clean install
-DUPDATE_SITE=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
-DEXTRAS_SITE=http://download.jboss.org/jbosstools/updates/kepler/extras/
{code}
4. launch local webserver (in a separate console window - do not close until done
testing):
{code}
cd /tmp
wget -nc https://raw.github.com/elonen/nanohttpd/master/NanoHTTPD.java
/opt/sun-java2-7.0/bin/javac NanoHTTPD.java
java NanoHTTPD -d ~/devstudio/trunk/product/ -p 8080
{code}
5. Install JBDS you just built.
6. Edit its jbdevstudio.ini file, setting these -D flags:
{code}
-Djboss.discovery.directory.url=http://localhost:8080/discovery/core/com.jboss.jbds.central.discovery/target/discovery-site/devstudio-directory.xml
-Djboss.discovery.site.url=http://localhost:8080/discovery/core/com.jboss.jbds.central.discovery/target/discovery-site/
{code}
7. Launch JBDS:
{code}
./jbdevstudio -consolelog -debug
{code}
8. Open the Software/Updates tab in Central. For all the entries with
{code}
siteUrl="${jboss.discovery.site.url:https://devstudio.jboss.com/upda...
{code}
you will see no connectors listed. Only Android and JRebel will be shown.
!JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png!
Error log shows:
{code}
!ENTRY org.eclipse.mylyn.discovery.core 4 0 2013-03-13 13:34:57.449
!MESSAGE
com.jboss.jbds.central.discovery_7.0.0.Alpha2-20130313-0501.jar_3856479853350480263.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 13:34:57.451
!MESSAGE Invalid connectorDescriptor/@siteUrl
{code}
was (Author: nickboldt):
Does not appear to be working.
Steps to repro:
1. Build JBDS 7 locally from trunk.
{code}
cd ~/devstudio/trunk/product
mvn clean install -P
maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate
{code}
2. Apply this patch:
[^JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt]
3. Build discovery plugins locally from trunk (with patch).
{code}
cd ~/devstudio/trunk/product/discovery
mvn clean install
-DUPDATE_SITE=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
-DEXTRAS_SITE=http://download.jboss.org/jbosstools/updates/kepler/extras/
{code}
4. launch local webserver (in a separate console window - do not close until done
testing):
{code}
cd /tmp
wget -nc https://raw.github.com/elonen/nanohttpd/master/NanoHTTPD.java
/opt/sun-java2-7.0/bin/javac NanoHTTPD.java
java NanoHTTPD -d ~/devstudio/trunk/product/ -p 8080
{code}
5. Install JBDS you just built.
6. Edit its jbdevstudio.ini file, setting these -D flags:
{code}
-Djboss.discovery.directory.url=http://localhost:8080/discovery/core/com.jboss.jbds.central.discovery/target/discovery-site/devstudio-directory.xml
-Djboss.discovery.site.url=http://localhost:8080/discovery/core/com.jboss.jbds.central.discovery/target/discovery-site/
{code}
7. Launch JBDS:
{code}
./jbdevstudio -consolelog -debug
{code}
8. Open the Software/Updates tab in Central. For all the entries with
siteUrl="${jboss.discovery.site.url:https://devstudio.jboss.com/upda...
you will see no connectors listed. Only Android and JRebel will be shown.
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
4772
days inactive
4772
days old
jbosstools-issues@lists.jboss.org
0 comments
1 participants
participants (1)
-
Nick Boldt (JIRA)