January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21513) Delete project menu entry is not enabled to delete a project

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21513?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-21513. ----------------------------------- Resolution: Done > Delete project menu entry is not enabled to delete a project > ------------------------------------------------------------ > > Key: JBIDE-21513 > URL: https://issues.jboss.org/browse/JBIDE-21513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Fred Bricon > Labels: openshift_deployment_view > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21414) Application wizard: ConcurrentModificationException when creating a new appliaction

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21414?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21414. --------------------------------- Verified in nigthly build of JBT with OpenShift tools plugin of version 3.1.0.Beta2-v20160121-0335-B154. > Application wizard: ConcurrentModificationException when creating a new appliaction > ------------------------------------------------------------------------------------ > > Key: JBIDE-21414 > URL: https://issues.jboss.org/browse/JBIDE-21414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta2 > > Attachments: concurrent-modification-exception.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21480) Log message if unable to determine client for connection when starting watch

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21480?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21480: --------------------------------------- Is there a way to verify it in tooling? If no, please close issue, otherwise please provide steps to verify. > Log message if unable to determine client for connection when starting watch > ---------------------------------------------------------------------------- > > Key: JBIDE-21480 > URL: https://issues.jboss.org/browse/JBIDE-21480 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_deployment_view > Fix For: 4.3.1.Beta2 > > > Log a message instead of throwing to fix tests -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21504) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Forge]

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21504?page=com.atlassian.jira.plugi... ] George Gastaldi reassigned JBIDE-21504: --------------------------------------- Assignee: George Gastaldi > For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Forge] > --------------------------------------------------- > > Key: JBIDE-21504 > URL: https://issues.jboss.org/browse/JBIDE-21504 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta2 > > > For JBIDE 4.3.1.Beta2 [Forge]: Please perform the following tasks: > 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101 > *NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), you do *not* need to do so again. > Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT. > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta2-SNAPSHOT</version> > </parent> > {code} > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT > {code} > 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch; > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > git checkout -b jbosstools-4.3.1.Beta2x > git push origin jbosstools-4.3.1.Beta2x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*. > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > {code} > 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and > * *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 Forge 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3583) Cannot start JBDS 9 with jdk 1.9 EA

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3583?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3583: -------------------------------- Description: Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). It just shows an error saying where to look for log. The log is linked here: https://issues.jboss.org/secure/attachment/12396824/1453206771791.log Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486213 was: Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). It just shows an error saying where to look for log. The log is linked here: https://issues.jboss.org/secure/attachment/12396824/1453206771791.log > Cannot start JBDS 9 with jdk 1.9 EA > ----------------------------------- > > Key: JBDS-3583 > URL: https://issues.jboss.org/browse/JBDS-3583 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows an error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486213 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3583) Cannot start JBDS 9 with jdk 1.9 EA

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3583?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3583: ------------------------------------- This is the related change in the JRE: http://openjdk.java.net/jeps/223 > Cannot start JBDS 9 with jdk 1.9 EA > ----------------------------------- > > Key: JBDS-3583 > URL: https://issues.jboss.org/browse/JBDS-3583 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows an error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486213 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21290) CDK 2 is detected as version 1.0

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21290: --------------------------------------- And I can confirm that as of JBDS 9.1.0.Beta2 B237, runtime detection reports CDK is version 2.0, so that should do for now. > CDK 2 is detected as version 1.0 > -------------------------------- > > Key: JBIDE-21290 > URL: https://issues.jboss.org/browse/JBIDE-21290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, runtime-detection, upstream > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: cdk-runtime-detection.png, Screenshot 2016-01-07 09.16.12.png > > > When you detect CDK using runtime detection, it will show you the name cdk-v2 which clearly shows it's version 2 (this is actually just based on the folder it seems). But the Version column says Version 1.0. > !cdk-runtime-detection.png! > Could we change it to version 2? > I know that this probably doesn't have any meaning right now - I noticed there is no runtime anymore, so the version is nowhere to be seen once you create the cdk server adapter. But it would still be nicer to show the correct version if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3575) Add Fedora 22 and 23 to the support matrix

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3575?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3575: ------------------------------------- [~akazakov], did what happen? Yes, we are now testing with Fedora 22 and 23, so that's all from my side. Now it's up to [~mhusnain] to update the support matrix. [~mhusnain], I think we can do it even for Beta2. It's just that the code freeze is now, so Alexey wanted to clear up all the JIRAs I suppose. So I will assign this to you and I suggest once this is done, you can resolve the JIRA for both 9.1.0.Beta2 and 10.0.0.Alpha1 as Fix versions. > Add Fedora 22 and 23 to the support matrix > ------------------------------------------ > > Key: JBDS-3575 > URL: https://issues.jboss.org/browse/JBDS-3575 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3575) Add Fedora 22 and 23 to the support matrix

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3575?page=com.atlassian.jira.plugin.... ] Martin Malina reassigned JBDS-3575: ----------------------------------- Assignee: Misha Ali (was: Martin Malina) > Add Fedora 22 and 23 to the support matrix > ------------------------------------------ > > Key: JBDS-3575 > URL: https://issues.jboss.org/browse/JBDS-3575 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Misha Ali > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21511) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [LiveReload]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21511?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-21511. --------------------------------- Resolution: Done > For JBIDE 4.3.1.Beta2: Code Freeze + Branch [LiveReload] > -------------------------------------------------------- > > Key: JBIDE-21511 > URL: https://issues.jboss.org/browse/JBIDE-21511 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta2 > > > For JBIDE 4.3.1.Beta2 [LiveReload]: Please perform the following tasks: > 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101 > *NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), you do *not* need to do so again. > Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT. > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta2-SNAPSHOT</version> > </parent> > {code} > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT > {code} > 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch; > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > git checkout -b jbosstools-4.3.1.Beta2x > git push origin jbosstools-4.3.1.Beta2x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*. > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > {code} > 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and > * *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 LiveReload 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, 5 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 January 2016