September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20775) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Aerogear]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20775: ---------------------------------- Summary: For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Aerogear] Key: JBIDE-20775 URL: https://issues.jboss.org/browse/JBIDE-20775 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: aerogear-hybrid, cordovasim Reporter: Nick Boldt Priority: Blocker For JBIDE 4.4.0.Alpha1 [Aerogear]: Please perform the following tasks: 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) Otherwise: 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT {code} 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.0.Alpha1-SNAPSHOT</version> </parent> {code} 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; {code} mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT {code} 4. Close (do not resolve) this JIRA when done. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20774) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20774: ---------------------------------- Summary: For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 Key: JBIDE-20774 URL: https://issues.jboss.org/browse/JBIDE-20774 Project: Tools (JBoss Tools) Issue Type: Task Components: build Reporter: Nick Boldt Priority: Blocker Fix For: 4.4.0.Alpha1 For JBIDE 4.4.0.Alpha1: Please perform the following tasks: 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) Otherwise: 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT {code} 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.0.Alpha1-SNAPSHOT</version> </parent> {code} 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; {code} mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT {code} 4. Close (do not resolve) this JIRA when done. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] See also: JBDS-3529 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-506) Update JBDS-IS version to 8.0.3 in info box on Markeplace

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-506?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-506: ---------------------------------- [~apodhrad] - please try this again. thkx > Update JBDS-IS version to 8.0.3 in info box on Markeplace > --------------------------------------------------------- > > Key: JBTIS-506 > URL: https://issues.jboss.org/browse/JBTIS-506 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > There is an old version (8.0.2) of JBDS-IS in info box on Marketplace, see > https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-in... > This old version also occurs in Eclipse IDE when trying to install JBDS-IS from markeplace. > Note that correct features are installed (those in JBDS-IS 8.0.3.GA). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-498) improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-498?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-498: ---------------------------------- Re: #5, I see you now have two identical copies of the directory.xml file: https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discov... https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discov... Why do you create two of them? > improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning > ----------------------------------------------------------------------------------------- > > Key: JBTIS-498 > URL: https://issues.jboss.org/browse/JBTIS-498 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > > Would it be possible to change your publishing process so that you're not dumping dozens of old jars into the same folder? Surely you aren't staging ALL these? (We only stage to QE once or twice per milestone... CR1, CR1a.) > Have a look here: > http://download.jboss.org/jbosstools/mars/staging/updates/integration-sta... > https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discov... > And contrast that with the way the JBT & JBDS discovery jars are done: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... > https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce... > (using rsync.sh, you get automated build folder cleanup every time you publish a new build, or you can force cleanup it with this job [1]). > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-cleanup/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20401) OpenShift tooling UI should include a link to user docs

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20401?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20401: ----------------------------------- Resolution: (was: Done) Assignee: Fred Bricon (was: Nick Boldt) Link to http://tools.jboss.org/documentation/howto/openshift3_getting_started.html has been restored. > OpenShift tooling UI should include a link to user docs > ------------------------------------------------------- > > Key: JBIDE-20401 > URL: https://issues.jboss.org/browse/JBIDE-20401 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Len DiMaggio > Assignee: Fred Bricon > Priority: Blocker > Labels: help_wanted > Fix For: 4.3.0.CR1 > > > Given the very different architecture of OpenShift v3 as compared to v2, we should provide users with a link to docs detailing the differences. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20401) OpenShift tooling UI should include a link to user docs

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20401?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20401. --------------------------------- Resolution: Done > OpenShift tooling UI should include a link to user docs > ------------------------------------------------------- > > Key: JBIDE-20401 > URL: https://issues.jboss.org/browse/JBIDE-20401 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Len DiMaggio > Assignee: Fred Bricon > Priority: Blocker > Labels: help_wanted > Fix For: 4.3.0.CR1 > > > Given the very different architecture of OpenShift v3 as compared to v2, we should provide users with a link to docs detailing the differences. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20773) JBoss Tools source zip contains nested zips?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20773?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-20773: ---------------------------------- Assignee: Nick Boldt > JBoss Tools source zip contains nested zips? > -------------------------------------------- > > Key: JBIDE-20773 > URL: https://issues.jboss.org/browse/JBIDE-20773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > > I noticed that the latest JBT 4.3.0.CR1a build's source zip and update site are both 388M [1]: > {code} > [ ] jbosstools-4.3.0.CR1-src.zip 17-Sep-2015 22:51 388M > [ ] repository.zip 17-Sep-2015 22:49 388M > {code} > [1] http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-4.3.0... > Yet when I build locally, I get these sizes: > {code} > -rw-rw-r-- 1 nboldt nboldt 247M Sep 23 14:05 repository.zip > -rw-rw-r-- 1 nboldt nboldt 222M Sep 23 14:09 jbosstools-4.3.0.CR2-src.zip > {code} > Also noticed that the CR1a src zip contains this: > {code} > jbosstools-4.3.0.CR1-src > jbosstools-livereload_ccd14f8a3ac6f99379c932b1ecbd069679c53c20_sources.zip > jbosstools-aerogear_8cc37fac2c06c12165becc71377d4367627146db_sources.zip > jbosstools-vpe_a6c1b12f38e9e56c4f2aa3af5ca057c90b1ca60a_sources.zip > jbosstools-javaee_788cd9fabcfb402ffe30c060d338cb334fb8f754_sources.zip > jbosstools-webservices_0b33c0e8aee5da84a0c8a55906b95084a4ea0b8a_sources.zip > {code} > The in the *src folder: > {code} > buildinfo > jbosstools-aerogear-4760415028f4cd667cffc1caaa0647b26a791bd2 > jbosstools-arquillian-412c297a0a6092cd5b877e9972c6a96dcf57c3fb > jbosstools-base-49f978da2bbccf381b26dbd64dc08ccd1138a0ab > jbosstools-birt-d2e797324294e60048d39d24536f2f16b1b78e30 > jbosstools-browsersim-b284a67fa3ccac3dfa2383873aeb24a3a4486c8e > jbosstools-build-sites-0580a57bed9d3b0ae957b2f5f6f26cc71a3159c2 > jbosstools-central-b3f750efa36eea63bc7dd2f77d3aca798583c48e > jbosstools-forge-20aafeb5f36fcf70f3658e9ad45c6b8b405b8af2 > jbosstools-freemarker-171cac721242580d65699e52544f38c44eac7019 > jbosstools-hibernate-fe17a3451ec4c278da05f4563ab6ebadb5437717 > jbosstools-javaee-c46ca764fae83c2525d4b8ad885b12b8b3f0c14d > jbosstools-jst-333c9a71aca9b449b5bae05a12e770f988ef7178 > jbosstools-livereload-bf4fa2662aa7e625198ce178701c9a0b9fd9bd72 > jbosstools-openshift-951590f4f5cf8d004b36e30d460d985be50ed42e > jbosstools-portlet-4eec888e7045ab1413934670cbdcdf7a11447b52 > jbosstools-server-b3c0959c85a130fca26165e46737e90565aad983 > jbosstools-vpe-ce6b5237c98a138a3ef55ec7baf0c3e37ed81490 > jbosstools-webservices-6aa98d422ce06a4aa53d35076cd405bc5f78ef31 > jbosstools-xulrunner-2edce933f7d64efbb4d7a5b16be8dadae8de766e > {code} > When I build locally, I get just one subfolder in the zip: > {code} > jbosstools-4.3.0.CR1-src > {code} > and in the *src folder: > {code} > buildinfo > jbosstools-aerogear-4760415028f4cd667cffc1caaa0647b26a791bd2 > jbosstools-arquillian-412c297a0a6092cd5b877e9972c6a96dcf57c3fb > jbosstools-base-49f978da2bbccf381b26dbd64dc08ccd1138a0ab > jbosstools-birt-d2e797324294e60048d39d24536f2f16b1b78e30 > jbosstools-browsersim-2dce9b6a53cb99e400ff6d4023d1545f5393db26 > jbosstools-build-sites-6b2a3fe3373341e0ed8c3f31e2f62d75217c2873 > jbosstools-central-b3f750efa36eea63bc7dd2f77d3aca798583c48e > jbosstools-forge-20aafeb5f36fcf70f3658e9ad45c6b8b405b8af2 > jbosstools-freemarker-171cac721242580d65699e52544f38c44eac7019 > jbosstools-hibernate-fe17a3451ec4c278da05f4563ab6ebadb5437717 > jbosstools-javaee-c46ca764fae83c2525d4b8ad885b12b8b3f0c14d > jbosstools-jst-333c9a71aca9b449b5bae05a12e770f988ef7178 > jbosstools-livereload-bf4fa2662aa7e625198ce178701c9a0b9fd9bd72 > jbosstools-openshift-951590f4f5cf8d004b36e30d460d985be50ed42e > jbosstools-portlet-4eec888e7045ab1413934670cbdcdf7a11447b52 > jbosstools-server-b3c0959c85a130fca26165e46737e90565aad983 > jbosstools-vpe-ce6b5237c98a138a3ef55ec7baf0c3e37ed81490 > jbosstools-webservices-6aa98d422ce06a4aa53d35076cd405bc5f78ef31 > jbosstools-xulrunner-2edce933f7d64efbb4d7a5b16be8dadae8de766e > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20773) JBoss Tools source zip contains nested zips?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20773: ---------------------------------- Summary: JBoss Tools source zip contains nested zips? Key: JBIDE-20773 URL: https://issues.jboss.org/browse/JBIDE-20773 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.3.0.CR1 Reporter: Nick Boldt Priority: Blocker I noticed that the latest JBT 4.3.0.CR1a build's source zip and update site are both 388M [1]: {code} [ ] jbosstools-4.3.0.CR1-src.zip 17-Sep-2015 22:51 388M [ ] repository.zip 17-Sep-2015 22:49 388M {code} [1] http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-4.3.0... Yet when I build locally, I get these sizes: {code} -rw-rw-r-- 1 nboldt nboldt 247M Sep 23 14:05 repository.zip -rw-rw-r-- 1 nboldt nboldt 222M Sep 23 14:09 jbosstools-4.3.0.CR2-src.zip {code} Also noticed that the CR1a src zip contains this: {code} jbosstools-4.3.0.CR1-src jbosstools-livereload_ccd14f8a3ac6f99379c932b1ecbd069679c53c20_sources.zip jbosstools-aerogear_8cc37fac2c06c12165becc71377d4367627146db_sources.zip jbosstools-vpe_a6c1b12f38e9e56c4f2aa3af5ca057c90b1ca60a_sources.zip jbosstools-javaee_788cd9fabcfb402ffe30c060d338cb334fb8f754_sources.zip jbosstools-webservices_0b33c0e8aee5da84a0c8a55906b95084a4ea0b8a_sources.zip {code} The in the *src folder: {code} buildinfo jbosstools-aerogear-4760415028f4cd667cffc1caaa0647b26a791bd2 jbosstools-arquillian-412c297a0a6092cd5b877e9972c6a96dcf57c3fb jbosstools-base-49f978da2bbccf381b26dbd64dc08ccd1138a0ab jbosstools-birt-d2e797324294e60048d39d24536f2f16b1b78e30 jbosstools-browsersim-b284a67fa3ccac3dfa2383873aeb24a3a4486c8e jbosstools-build-sites-0580a57bed9d3b0ae957b2f5f6f26cc71a3159c2 jbosstools-central-b3f750efa36eea63bc7dd2f77d3aca798583c48e jbosstools-forge-20aafeb5f36fcf70f3658e9ad45c6b8b405b8af2 jbosstools-freemarker-171cac721242580d65699e52544f38c44eac7019 jbosstools-hibernate-fe17a3451ec4c278da05f4563ab6ebadb5437717 jbosstools-javaee-c46ca764fae83c2525d4b8ad885b12b8b3f0c14d jbosstools-jst-333c9a71aca9b449b5bae05a12e770f988ef7178 jbosstools-livereload-bf4fa2662aa7e625198ce178701c9a0b9fd9bd72 jbosstools-openshift-951590f4f5cf8d004b36e30d460d985be50ed42e jbosstools-portlet-4eec888e7045ab1413934670cbdcdf7a11447b52 jbosstools-server-b3c0959c85a130fca26165e46737e90565aad983 jbosstools-vpe-ce6b5237c98a138a3ef55ec7baf0c3e37ed81490 jbosstools-webservices-6aa98d422ce06a4aa53d35076cd405bc5f78ef31 jbosstools-xulrunner-2edce933f7d64efbb4d7a5b16be8dadae8de766e {code} When I build locally, I get just one subfolder in the zip: {code} jbosstools-4.3.0.CR1-src {code} and in the *src folder: {code} buildinfo jbosstools-aerogear-4760415028f4cd667cffc1caaa0647b26a791bd2 jbosstools-arquillian-412c297a0a6092cd5b877e9972c6a96dcf57c3fb jbosstools-base-49f978da2bbccf381b26dbd64dc08ccd1138a0ab jbosstools-birt-d2e797324294e60048d39d24536f2f16b1b78e30 jbosstools-browsersim-2dce9b6a53cb99e400ff6d4023d1545f5393db26 jbosstools-build-sites-6b2a3fe3373341e0ed8c3f31e2f62d75217c2873 jbosstools-central-b3f750efa36eea63bc7dd2f77d3aca798583c48e jbosstools-forge-20aafeb5f36fcf70f3658e9ad45c6b8b405b8af2 jbosstools-freemarker-171cac721242580d65699e52544f38c44eac7019 jbosstools-hibernate-fe17a3451ec4c278da05f4563ab6ebadb5437717 jbosstools-javaee-c46ca764fae83c2525d4b8ad885b12b8b3f0c14d jbosstools-jst-333c9a71aca9b449b5bae05a12e770f988ef7178 jbosstools-livereload-bf4fa2662aa7e625198ce178701c9a0b9fd9bd72 jbosstools-openshift-951590f4f5cf8d004b36e30d460d985be50ed42e jbosstools-portlet-4eec888e7045ab1413934670cbdcdf7a11447b52 jbosstools-server-b3c0959c85a130fca26165e46737e90565aad983 jbosstools-vpe-ce6b5237c98a138a3ef55ec7baf0c3e37ed81490 jbosstools-webservices-6aa98d422ce06a4aa53d35076cd405bc5f78ef31 jbosstools-xulrunner-2edce933f7d64efbb4d7a5b16be8dadae8de766e {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-506) Update JBDS-IS version to 8.0.3 in info box on Markeplace

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-506?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-506: -------------------------------- Assignee: Paul Leacu > Update JBDS-IS version to 8.0.3 in info box on Markeplace > --------------------------------------------------------- > > Key: JBTIS-506 > URL: https://issues.jboss.org/browse/JBTIS-506 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > There is an old version (8.0.2) of JBDS-IS in info box on Marketplace, see > https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-in... > This old version also occurs in Eclipse IDE when trying to install JBDS-IS from markeplace. > Note that correct features are installed (those in JBDS-IS 8.0.3.GA). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20762) ensure SHA256 sum is created for browsersim standalone zip

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20762?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20762: -------------------------------------- Assignee: Nick Boldt (was: Konstantin Marmalyukov) > ensure SHA256 sum is created for browsersim standalone zip > ---------------------------------------------------------- > > Key: JBIDE-20762 > URL: https://issues.jboss.org/browse/JBIDE-20762 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, build > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.Final, 4.4.0.Alpha1 > > > There is no sha256 sum in http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-4.3.0... > So no sha was copied to http://download.jboss.org/jbosstools/static/mars/development/updates/core... > I've manually created the files, but we need to know why it's not being created automatically as part of the build, eg., in http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bro... or http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bro... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2015