[jbosstools-issues] [JBoss JIRA] (JBTIS-160) Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central

[ https://issues.jboss.org/browse/JBTIS-160?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-160 at 8/26/13 5:04 PM: ----------------------------------------------------------- PR: https://github.com/jbosstools/jbosstools-integration-stack/pull/103 How to use: 1. Build: {code} cd ~/tru/jbosstools-integration-stack/jbosstools mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=4.1.2.Final -DVERSION=4.1.2 \ -DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 -DCOMPOSITE_SITE=file://`pwd`/site/target/repository \ -DUPSTREAM_DIRECTORY_XML=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml \ -DCOMPOSITE_URLS=http://download.jboss.org/jbosstools/updates/development/kepler/,http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/,http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.1.2.Final/REPO/ {code} 2. Fix generated directory.xml to point to locally-built jar, eg., use this {code} <entry url="org.jboss.tools.central.discovery.integration-stack_4.1.2.CI-2013-08-21_20-10-23-B111-v20130101-0001-B111.jar" permitCategories="true"/> {code} instead of {code} <entry url="http://download.jboss.org/jbosstools/discovery/integration/inte... permitCategories="true"/> {code} 2. Launch a local nanohttpd server [1] to host the directory.xml / discovery plugin, and the Discovery composite site. {code} cd ~/tru/jbosstools-integration-stack/jbosstools/discovery/generation/target/ /opt/sun-java2-7.0/bin/java NanoHTTPD -d `pwd` -p 8080 {code} [1] https://github.com/NanoHttpd/nanohttpd/blob/master/core/src/main/java/fi/... 4. install Eclipse Kepler JEE bundle; launch at fresh workspace 5. install JBoss Central into Eclipse from http://localhost:8081/discovery-site/ 6. re-launch Eclipse with {code} ./eclipse -vmargs \ -Djboss.discovery.directory.url=http://localhost:8080/plugins/jbosstools-integration-stack-directory.xml \ -Djboss.discovery.site.url=http://localhost:8081/discovery-site/ {code} was (Author: nickboldt): PR: https://github.com/jbosstools/jbosstools-integration-stack/pull/103 How to use: 1. Build: cd ~/tru/jbosstools-integration-stack/jbosstools mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=4.1.2.Final -DVERSION=4.1.2 -DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 -DCOMPOSITE_SITE=file://`pwd`/site/target/repository -DUPSTREAM_DIRECTORY_XML=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml -DCOMPOSITE_URLS=http://download.jboss.org/jbosstools/updates/development/kepler/,http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/,http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.1.2.Final/REPO/ 2. Fix generated directory.xml to point to locally-built jar, eg., use this {code} <entry url="org.jboss.tools.central.discovery.integration-stack_4.1.2.CI-2013-08-21_20-10-23-B111-v20130101-0001-B111.jar" permitCategories="true"/> {code} instead of {code} <entry url="http://download.jboss.org/jbosstools/discovery/integration/inte... permitCategories="true"/> {code} 2. Launch a local nanohttpd server [1] to host the directory.xml / discovery plugin, and the Discovery composite site. {code} cd ~/tru/jbosstools-integration-stack/jbosstools/discovery/generation/target/ /opt/sun-java2-7.0/bin/java NanoHTTPD -d `pwd` -p 8080 {code} [1] https://github.com/NanoHttpd/nanohttpd/blob/master/core/src/main/java/fi/... 4. install Eclipse Kepler JEE bundle; launch at fresh workspace 5. install JBoss Central into Eclipse from http://localhost:8081/discovery-site/ 6. re-launch Eclipse with {code} ./eclipse -vmargs \ -Djboss.discovery.directory.url=http://localhost:8080/plugins/jbosstools-integration-stack-directory.xml \ -Djboss.discovery.site.url=http://localhost:8081/discovery-site/ {code} -- 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