August 2013 - jbosstools-issues - Jboss List Archives

[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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-160?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-160 at 8/26/13 4:07 PM: ----------------------------------------------------------- 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/integration-st..." 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/integration-st..." permitCategories="true"/> {code} 2. Launch 2 local nanohttpd servers [1] to host both the directory.xml / discovery plugin, and the Discovery composite site. Put each on a different port. _In future, we ought to simplify this so that the output of the build is a single folder, which can be more easily hosted._ {code} cd ~/tru/jbosstools-integration-stack/jbosstools/discovery/generation/target/plugins /opt/sun-java2-7.0/bin/java NanoHTTPD -d `pwd` -p 8080 {code} {code} cd ~/tru/jbosstools-integration-stack/jbosstools/discovery/generation/target/discovery-site /opt/sun-java2-7.0/bin/java NanoHTTPD -d `pwd` -p 8081 {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/ 6. re-launch Eclipse with {code} ./eclipse -vmargs \ -Djboss.discovery.directory.url=http://localhost:8080/jbosstools-integration-stack-directory.xml \ -Djboss.discovery.site.url=http://localhost:8081/ {code} > Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central > ----------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-160 > URL: https://issues.jboss.org/browse/JBTIS-160 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Paul Leacu > > Rather than hardcoding URLs in plugin.properties for > {code} > jboss.is.update.url = http://download.jboss.org/jbosstools/updates/development/kepler/central/i... > {code} > or > {code} > jboss.is.update.url = https://devstudio.jboss.com/updates/7.0-development/central/integration-s... > {code} > We should use the jboss.discovery.site.url variable so that commandline value of the URL can be set, in order to make testing easier. -- 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

11 years, 1 month

1
0
0 / 0

[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

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-160?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-160: ---------------------------------- https://github.com/jbosstools/jbosstools-integration-stack/pull/104 > Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central > ----------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-160 > URL: https://issues.jboss.org/browse/JBTIS-160 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Paul Leacu > > Rather than hardcoding URLs in plugin.properties for > {code} > jboss.is.update.url = http://download.jboss.org/jbosstools/updates/development/kepler/central/i... > {code} > or > {code} > jboss.is.update.url = https://devstudio.jboss.com/updates/7.0-development/central/integration-s... > {code} > We should use the jboss.discovery.site.url variable so that commandline value of the URL can be set, in order to make testing easier. -- 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

11 years, 1 month

1
0
0 / 0

[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

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-160?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-160: ----------------------------- Assignee: Paul Leacu > Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central > ----------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-160 > URL: https://issues.jboss.org/browse/JBTIS-160 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Paul Leacu > > Rather than hardcoding URLs in plugin.properties for > {code} > jboss.is.update.url = http://download.jboss.org/jbosstools/updates/development/kepler/central/i... > {code} > or > {code} > jboss.is.update.url = https://devstudio.jboss.com/updates/7.0-development/central/integration-s... > {code} > We should use the jboss.discovery.site.url variable so that commandline value of the URL can be set, in order to make testing easier. -- 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

11 years, 1 month

1
0
0 / 0

[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

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-160?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-160: ---------------------------------- merged: https://github.com/jbosstools/jbosstools-integration-stack/pull/103 > Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central > ----------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-160 > URL: https://issues.jboss.org/browse/JBTIS-160 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > > Rather than hardcoding URLs in plugin.properties for > {code} > jboss.is.update.url = http://download.jboss.org/jbosstools/updates/development/kepler/central/i... > {code} > or > {code} > jboss.is.update.url = https://devstudio.jboss.com/updates/7.0-development/central/integration-s... > {code} > We should use the jboss.discovery.site.url variable so that commandline value of the URL can be set, in order to make testing easier. -- 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

11 years, 1 month

1
0
0 / 0

[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

by Nick Boldt (JIRA)

Nick Boldt created JBTIS-160: -------------------------------- Summary: Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central Key: JBTIS-160 URL: https://issues.jboss.org/browse/JBTIS-160 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: distribution Affects Versions: 4.1.0.Beta1 Reporter: Nick Boldt Rather than hardcoding URLs in plugin.properties for {code} jboss.is.update.url = http://download.jboss.org/jbosstools/updates/development/kepler/central/i... {code} or {code} jboss.is.update.url = https://devstudio.jboss.com/updates/7.0-development/central/integration-s... {code} We should use the jboss.discovery.site.url variable so that commandline value of the URL can be set, in order to make testing easier. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-159) JBoss Central discovery installer fails - JBDSIS 7.0.1

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-159: -------------------------------- Summary: JBoss Central discovery installer fails - JBDSIS 7.0.1 Key: JBTIS-159 URL: https://issues.jboss.org/browse/JBTIS-159 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.1-JBDS Reporter: Paul Leacu Assignee: Len DiMaggio Need to test more than just the p2 installer. The Mylyn Discovery JBoss Central installer should give you the same results. i.e. (JBTIS - community) ./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/integration/integration-stack/4.1.2/jbosstools-integration-stack-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/integration/integration-stack/4.1.2/ for JBDSIS (devstudio) - substitute: https://devstudio.jboss.com/updates/7.0-development/integration-stack/ JBoss Central>Software/Update -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install

by Rob Cernich (JIRA)

[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ] Rob Cernich commented on JBTIS-158: ----------------------------------- For JBTIS, we should have a single site, which includes all the IS features and makes reference to the JBT core site and the JBTIS TP (i.e. the JBTIS site is built with two associate sites). This is easy peasy and works today. The structure on jboss.org would be the same as what it has been, where the .../integration-stack URL is a composite site that contains references to each JBTIS version (e.g. ./aggregate/4.1.0, ./aggregate/4.1.1, ./aggregate/4.1.2, etc.). > create composite site zip containing JBDS IS + dependencies for easier offline install > -------------------------------------------------------------------------------------- > > Key: JBTIS-158 > URL: https://issues.jboss.org/browse/JBTIS-158 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Rob Cernich > > Suggested by [~rcernich]: > {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like: > {code}./compositeContent.xml > ./compositeArtifacts.xml > ./7.1.0/7.1.0.Beta1-jbds-is/ > ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code} > {quote} > This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site. > If we did a similar thing for JBT IS, it would need to contain these sites: > {code} > JBT webtools aggregate site (not the full JBT aggregate site) > JBT TP > JBT IS > JBT IS TP > {code} > Or, if we assume that users will already have JBT (or some part of it) installed, then we need only: > {code} > JBT IS > JBT IS TP > {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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install

by Rob Cernich (JIRA)

[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ] Rob Cernich commented on JBTIS-158: ----------------------------------- I think this approach should only apply to JBDS-IS. For JBTIS, I think it is important to include the JBT core in the list of referenced sites so that users have the ability to install just what they need. For example, if a user wants to work with SwitchYard, they can go right to JBTIS and install SwitchYard, without first having to install JBT. I think this is a legitimate use case for community. Personally, I don't see any problem with the way the JBTIS site is setup, where it is a single site with two referenced sites: JBT core and JBTIS TP. This is simple and requires no hoop jumping. > create composite site zip containing JBDS IS + dependencies for easier offline install > -------------------------------------------------------------------------------------- > > Key: JBTIS-158 > URL: https://issues.jboss.org/browse/JBTIS-158 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Rob Cernich > > Suggested by [~rcernich]: > {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like: > {code}./compositeContent.xml > ./compositeArtifacts.xml > ./7.1.0/7.1.0.Beta1-jbds-is/ > ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code} > {quote} > This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site. > If we did a similar thing for JBT IS, it would need to contain these sites: > {code} > JBT webtools aggregate site (not the full JBT aggregate site) > JBT TP > JBT IS > JBT IS TP > {code} > Or, if we assume that users will already have JBT (or some part of it) installed, then we need only: > {code} > JBT IS > JBT IS TP > {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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install

by Nick Boldt (JIRA)

Nick Boldt created JBTIS-158: -------------------------------- Summary: create composite site zip containing JBDS IS + dependencies for easier offline install Key: JBTIS-158 URL: https://issues.jboss.org/browse/JBTIS-158 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: distribution Affects Versions: 4.1.0.Beta1 Reporter: Nick Boldt Assignee: Rob Cernich Suggested by [~rcernich]: {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like: {code}./compositeContent.xml ./compositeArtifacts.xml ./7.1.0/7.1.0.Beta1-jbds-is/ ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code} {quote} This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site. If we did a similar thing for JBT IS, it would need to contain these sites: {code} JBT webtools aggregate site (not the full JBT aggregate site) JBT TP JBT IS JBT IS TP {code} Or, if we assume that users will already have JBT (or some part of it) installed, then we need only: {code} JBT IS JBT IS TP {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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-15374) Create target platform from Luna M1 or M2 dependencies

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15374?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15374: ------------------------------------ Job description [1] updated to document new TP versions. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... > Create target platform from Luna M1 or M2 dependencies > ------------------------------------------------------ > > Key: JBIDE-15374 > URL: https://issues.jboss.org/browse/JBIDE-15374 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > > Create a new target platform for use with JBoss Tools 4.2 (Luna). Should be versioned 4.40.x. > Luna schedule: > http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#Schedule -- 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

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2013