June 2016 - jbosstools-issues - Jboss List Archives

[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: ----------------------------------------- Where can I download it? Couldn't reproduce it after trying once again > 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-22463) Update CDK code after API change in Docker tooling

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22463?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22463. --------------------------------- nothing to verify from QE perspective. > Update CDK code after API change in Docker tooling > -------------------------------------------------- > > Key: JBIDE-22463 > URL: https://issues.jboss.org/browse/JBIDE-22463 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Final > > > The APi to create a connection changed in the latest version of Docker tooling. This impacts the {{CDKDockerUtility}} class in the {{org.jboss.tools.openshift.cdk.server}} bundle. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18224) Table Selection has poor performance if "Verify Database Connection" is checked in previous step

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18224?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-18224. ------------------------------------- Fix Version/s: 4.4.0.Final (was: 4.2.x) (was: 4.3.x) Assignee: George Gastaldi (was: Koen Aers) Resolution: Done I believe this should be fixed now with FORGE-2651 and FORGE-2644. > Table Selection has poor performance if "Verify Database Connection" is checked in previous step > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-18224 > URL: https://issues.jboss.org/browse/JBIDE-18224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.0.Final > > > If the "Verify Database Connection" *is checked* then there is very *poor performance* in the next step during tables selection on JPA: Generate Entities From Tables wizard. > I don't understand what is going on behind the scenes - but there is for sure some communication with DB happening. Not sure if this is necessary as the list of tables is read correctly and imho the list should be just checked if there is at least one table selected. > It works *without performance problems* if "Verify Database Connection" was *not checked* in previous step. -- 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:20 AM: ------------------------------------------------------------------- [~rob.stryker] cant replicate the brk-point not being hit in general. The brk-point mentioned above isnt hit when browsing the page, it is hit if you point your browser to <host>/rest/members. I can have others hit, so beside the NPE this issue is a non-issue since you filed the NPE to another jira. What is the other issue, so that we can link it here? 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 since you filed the NPE to another jira. What is the other issue, so that we can link it here? > 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-22477) For JBIDE 4.4.0.Final: Prepare for Final/GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22477?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22477: ------------------------------------ For future reference, a branch rename can be done like this: {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 > ------------------------------------------- > > Key: JBIDE-22477 > URL: https://issues.jboss.org/browse/JBIDE-22477 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.0.Final > > > For JBIDE 4.4.0.Final: 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...] > See also: JBDS-3920 -- 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 Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22546?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-22546: ------------------------------------ I've used devstudio 10.0.0.GA build, that is based on Eclipse Neon RC2. > 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-22482) For JBIDE 4.4.0.Final: Prepare for Final/GA [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22482?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22482: ------------------------------------ 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 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22482 > URL: https://issues.jboss.org/browse/JBIDE-22482 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.0.Final > > > For JBIDE 4.4.0.Final [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: 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 build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch 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:17 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. What is the other issue, so that we can link it here? 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 since you filed the NPE to another jira. > 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-22482) For JBIDE 4.4.0.Final: Prepare for Final/GA [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22482?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22482. ------------------------------ Resolution: Done > For JBIDE 4.4.0.Final: Prepare for Final/GA [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22482 > URL: https://issues.jboss.org/browse/JBIDE-22482 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.0.Final > > > For JBIDE 4.4.0.Final [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: 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 build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch 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-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 closed JBIDE-22479. ------------------------------ Resolution: Done > 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

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