February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23908) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [arquillian]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23908?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-23908: ---------------------------------- Assignee: Snjezana Peco > For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [arquillian] > -------------------------------------------------------------------- > > Key: JBIDE-23908 > URL: https://issues.jboss.org/browse/JBIDE-23908 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: arquillian > Reporter: Jeff MAURY > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.4.4.AM1 > > > For JBIDE 4.4.4.AM1 [arquillian]: Please perform the following tasks: > > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1 > > [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...] > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.4.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch: > > {code} > git checkout master; > git pull origin master; > git checkout -b jbosstools-4.4.x; > git push origin jbosstools-4.4.x > {code} > > Now, your root pom will use parent pom version: > > * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too. > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final > > {code} > mvn clean verify -Dtpc.version=4.60.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final > > {code} > mvn clean verify -Dtpc.version=4.60.2.Final > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23909) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [foundation]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23909?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-23909: ---------------------------------- Assignee: Rob Stryker > For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [foundation] > -------------------------------------------------------------------- > > Key: JBIDE-23909 > URL: https://issues.jboss.org/browse/JBIDE-23909 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.4.4.AM1 > > > For JBIDE 4.4.4.AM1 [foundation]: Please perform the following tasks: > > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1 > > [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...] > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.4.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch: > > {code} > git checkout master; > git pull origin master; > git checkout -b jbosstools-4.4.x; > git push origin jbosstools-4.4.x > {code} > > Now, your root pom will use parent pom version: > > * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too. > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final > > {code} > mvn clean verify -Dtpc.version=4.60.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final > > {code} > mvn clean verify -Dtpc.version=4.60.2.Final > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23910) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [browsersim]

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-23910: ---------------------------------- Summary: For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [browsersim] Key: JBIDE-23910 URL: https://issues.jboss.org/browse/JBIDE-23910 Project: Tools (JBoss Tools) Issue Type: Task Components: browsersim Reporter: Jeff MAURY Priority: Blocker Fix For: 4.4.4.AM1 For JBIDE 4.4.4.AM1 [browsersim]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1 [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.4.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch: {code} git checkout master; git pull origin master; git checkout -b jbosstools-4.4.x; git push origin jbosstools-4.4.x {code} Now, your root pom will use parent pom version: * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for browsersim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23907) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [aerogear-hybrid]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23907?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-23907: ---------------------------------- Assignee: Gorkem Ercan > For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [aerogear-hybrid] > ------------------------------------------------------------------------- > > Key: JBIDE-23907 > URL: https://issues.jboss.org/browse/JBIDE-23907 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid > Reporter: Jeff MAURY > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.4.4.AM1 > > > For JBIDE 4.4.4.AM1 [aerogear-hybrid]: Please perform the following tasks: > > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1 > > [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...] > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.4.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch: > > {code} > git checkout master; > git pull origin master; > git checkout -b jbosstools-4.4.x; > git push origin jbosstools-4.4.x > {code} > > Now, your root pom will use parent pom version: > > * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too. > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final > > {code} > mvn clean verify -Dtpc.version=4.60.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final > > {code} > mvn clean verify -Dtpc.version=4.60.2.Final > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23907) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [aerogear-hybrid]

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-23907: ---------------------------------- Summary: For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [aerogear-hybrid] Key: JBIDE-23907 URL: https://issues.jboss.org/browse/JBIDE-23907 Project: Tools (JBoss Tools) Issue Type: Task Components: aerogear-hybrid Reporter: Jeff MAURY Priority: Blocker Fix For: 4.4.4.AM1 For JBIDE 4.4.4.AM1 [aerogear-hybrid]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1 [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.4.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch: {code} git checkout master; git pull origin master; git checkout -b jbosstools-4.4.x; git push origin jbosstools-4.4.x {code} Now, your root pom will use parent pom version: * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23895) JBoss Tools Central install job (smoke test) failing due to UI blocker

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23895?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23895: ------------------------------------ When I ran your job again, it failed. It didn't find the remediation screen? https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Devstudi... Or it did, but then it failed? https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Devstudi... > JBoss Tools Central install job (smoke test) failing due to UI blocker > ---------------------------------------------------------------------- > > Key: JBIDE-23895 > URL: https://issues.jboss.org/browse/JBIDE-23895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: install-tests > Affects Versions: 4.4.3.Final > Reporter: Nick Boldt > Assignee: Lukáš Valach > > This job is failing: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code} > 08:40:05.807 DEBUG [main][ScreenshotCapturer] Capturing Screenshot: ./target/screenshots/default/com.jboss.jbds.byoe.test.UpdateSiteTest.testInstallFromUpdateSite.png > java.lang.AssertionError: Licence is accepted by default{code} > -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Devstudi... > I'd like to use it to help verify that staged bits for QE are correctly populated, but I can't if the test won't run. :( > Can it be fixed to bypass the UI blockage? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23812) Server adapter editor: server adapter wired to offline server is not editable any more

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23812?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23812: ------------------------------------------ the suggested fix only works partially. I thus postponed this issue to 4.4.4.AM1 > Server adapter editor: server adapter wired to offline server is not editable any more > -------------------------------------------------------------------------------------- > > Key: JBIDE-23812 > URL: https://issues.jboss.org/browse/JBIDE-23812 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter_editor > Fix For: 4.4.4.AM1 > > Attachments: 2-connections.png, connection-switched-editor-not-dirty.png, using-connection-to-cdkv2.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23812) Server adapter editor: server adapter wired to offline server is not editable any more

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23812?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23812: ------------------------------------- Fix Version/s: 4.4.4.AM1 (was: 4.4.3.Final) > Server adapter editor: server adapter wired to offline server is not editable any more > -------------------------------------------------------------------------------------- > > Key: JBIDE-23812 > URL: https://issues.jboss.org/browse/JBIDE-23812 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter_editor > Fix For: 4.4.4.AM1 > > Attachments: 2-connections.png, connection-switched-editor-not-dirty.png, using-connection-to-cdkv2.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods when no service is available

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23490: ------------------------------------------ [~aurelien.pupier] [~jeffmaury] if we create such an adapter it'll only be able to publish. The other functionalities like "Show In > Browser" wont work afaics. There's no service that a route could point to and thus no visibility via an Url. Correct or do I miss something? > Server adapter: provide ability to link pods when no service is available > ------------------------------------------------------------------------- > > Key: JBIDE-23490 > URL: https://issues.jboss.org/browse/JBIDE-23490 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard > Fix For: 4.4.3.Final > > > When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application. > The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1040) Update the logic for checking all available quickstarts in RH Central

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1040?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1040. ------------------------------------ Verified with Devstudio 10.2.0.GA > Update the logic for checking all available quickstarts in RH Central > --------------------------------------------------------------------- > > Key: JBTIS-1040 > URL: https://issues.jboss.org/browse/JBTIS-1040 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.1.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: additional_features.png, rh3.png, rhc1.png, rhc2.png > > > There is again a problem with the Fuse quickstart. Currently, the quickstart is available only if we enable Early Access in RH Central. At the first sight it looks like the behavior is hard coded. > Please update the logic for checking all available quickstarts so that it will detect Fuse quickstart without just checking if the Early Access is enabled or not. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017