June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3920) For JBDS 10.0.0.GA: Prepare for Final/GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3920?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3920. ---------------------------- Resolution: Done > For JBDS 10.0.0.GA: Prepare for Final/GA > ---------------------------------------- > > Key: JBDS-3920 > URL: https://issues.jboss.org/browse/JBDS-3920 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 10.0.0.GA > > > For JBDS 10.0.0.GA: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA > [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch > 2. 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:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!) > * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch > 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. 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...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22507) Debugging: cannot debug kitchensink, no breakpoint is being hit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22507?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22507 at 6/6/16 10:16 AM: ------------------------------------------------------------------- [~rob.stryker] cant replicate the brk-point not being hit in general. The brk-point mentioned above isnt hit when browsing the page, but I can have others hit, so beside the NPE this issue is a non-issue since you filed the NPE to another jira. was (Author: adietish): [~rob.stryker] cant replicate the brk-point not being hit in general. The brk-point mentioned above isnt hit when browsing the page, but I can have others hit, so beside the NPE this issue is a non-issue. > Debugging: cannot debug kitchensink, no breakpoint is being hit > --------------------------------------------------------------- > > Key: JBIDE-22507 > URL: https://issues.jboss.org/browse/JBIDE-22507 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: debug, openshift_v3 > Fix For: 4.4.1.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22241) OpenShift Explorer: Cascade resource deletion

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22241?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22241: --------------------------------------- [~jcantrill] I agree with you, it will ease our testing too, because it will be in upstream, less potential places for errors... And it would be waste of time and resources to have almost duplicate logic imho. What I was trying to say with my comments was only a note that simple deletion is not as simple as it could appear. > OpenShift Explorer: Cascade resource deletion > --------------------------------------------- > > Key: JBIDE-22241 > URL: https://issues.jboss.org/browse/JBIDE-22241 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: explorer, openshift_v3, ux > Fix For: 4.4.1.Alpha1 > > > It would be nice to have a possibility to allow cascading deletion, deletion of related resource/resource managed by the resource which is about to be deleted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22507) Debugging: cannot debug kitchensink, no breakpoint is being hit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22507?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22507: ------------------------------------------ [~rob.stryker] cant replicate the brk-point not being hit in general. The brk-point mentioned above isnt hit when browsing the page, but I can have others hit. > Debugging: cannot debug kitchensink, no breakpoint is being hit > --------------------------------------------------------------- > > Key: JBIDE-22507 > URL: https://issues.jboss.org/browse/JBIDE-22507 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: debug, openshift_v3 > Fix For: 4.4.1.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22546) Project is not refreshed automatically after Scaffold Generate

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22546?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-22546: ----------------------------------------- I tried to reproduce your issue but failed to do so. Are you using Eclipse Mars.2 ? Can you give me more details about the parameters (or maybe screencast if that's easier)? > Project is not refreshed automatically after Scaffold Generate > -------------------------------------------------------------- > > Key: JBIDE-22546 > URL: https://issues.jboss.org/browse/JBIDE-22546 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Alpha2 > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Critical > Labels: respin-a > Fix For: 4.4.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22507) Debugging: cannot debug kitchensink, no breakpoint is being hit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22507?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22507 at 6/6/16 10:15 AM: ------------------------------------------------------------------- [~rob.stryker] cant replicate the brk-point not being hit in general. The brk-point mentioned above isnt hit when browsing the page, but I can have others hit, so beside the NPE this issue is a non-issue. was (Author: adietish): [~rob.stryker] cant replicate the brk-point not being hit in general. The brk-point mentioned above isnt hit when browsing the page, but I can have others hit. > Debugging: cannot debug kitchensink, no breakpoint is being hit > --------------------------------------------------------------- > > Key: JBIDE-22507 > URL: https://issues.jboss.org/browse/JBIDE-22507 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: debug, openshift_v3 > Fix For: 4.4.1.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22479) For JBIDE 4.4.0.Final: Prepare for Final/GA [Central Discovery]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22479?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22479: ------------------------------------ Renamed with: {code} old=jbosstools-4.4.x new=jbosstools-4.4.0.x git checkout $old git pull origin $old git branch -m $old $new || git branch $new git push origin $new git push origin :$old {code} > For JBIDE 4.4.0.Final: Prepare for Final/GA [Central Discovery] > --------------------------------------------------------------- > > Key: JBIDE-22479 > URL: https://issues.jboss.org/browse/JBIDE-22479 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.0.Final > > > For JBIDE 4.4.0.Final [Central Discovery]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA > [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch > 2. 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:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!) > * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch > 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. 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 Central Discovery 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3920) For JBDS 10.0.0.GA: Prepare for Final/GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3920?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3920: ---------------------------------- Renamed with: {code} old=jbosstools-4.4.x new=jbosstools-4.4.0.x git checkout $old git pull origin $old git branch -m $old $new || git branch $new git push origin $new git push origin :$old {code} > For JBDS 10.0.0.GA: Prepare for Final/GA > ---------------------------------------- > > Key: JBDS-3920 > URL: https://issues.jboss.org/browse/JBDS-3920 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 10.0.0.GA > > > For JBDS 10.0.0.GA: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA > [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch > 2. 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:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!) > * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch > 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. 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...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22446) Release process can include snapshots artifacts

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22446: ---------------------------------------- This issues is not about fixing the rest client dependency. It has been already done in separate issue - JBIDE-22444 This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. Lack of such a test is not a blocker for this release. Removing it from respin-a. > Release process can include snapshots artifacts > ----------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Fix For: 4.4.x > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22446) Release process can include snapshots artifacts

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22446: ----------------------------------- Description: 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. was:4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Release process can include snapshots artifacts > ----------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Fix For: 4.4.x > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016