March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3374) Remove org.eclipse.cvs feature from JBDS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3374?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3374: ------------------------------------- Easy to remove it from JBDS update site/installer: https://github.com/jbdevstudio/jbdevstudio-product/pull/285 It will leave cvs feature available from TP. > Remove org.eclipse.cvs feature from JBDS > ---------------------------------------- > > Key: JBDS-3374 > URL: https://issues.jboss.org/browse/JBDS-3374 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > > com.jboss.devstudio.core.feature/feature.xml declares > {quote} > <import feature="org.eclipse.cvs"/> > {quote} > I can't see any reason why we'd do that in 2015. > Burr Sutter, Len DiMaggio, Max Rydahl Andersen : is there any client requirement about CVS support? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3361) Cannot install JBDS 8.0.2.GA in offline mode

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3361?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3361: ------------------------------------- Even though I like the idea of using zipped TP inclusion, there is still simpler solution https://github.com/jbdevstudio/jbdevstudio-product/pull/284 which: 1. Includes all required deps into jbdevstudio p2repo so it would work offline 2. Make jbds installer build faster because it just include jbdevstudio product IU into installer p2 repo > Cannot install JBDS 8.0.2.GA in offline mode > -------------------------------------------- > > Key: JBDS-3361 > URL: https://issues.jboss.org/browse/JBDS-3361 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 8.0.2.GA > Reporter: Tomáš Sedmík > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.Alpha2 > > > Cannot install JBDS 8.0.2.GA in offline mode - see the problem > {code:borderStyle=solid} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Developer Studio (Core Features) 8.0.2.GA-v20150114-2029-B382 (com.jboss.devstudio.core.feature.feature.group 8.0.2.GA-v20150114-2029-B382) > Missing requirement: JBoss Developer Studio (Core Features) 8.0.2.GA-v20150114-2029-B382 (com.jboss.devstudio.core.feature.feature.group 8.0.2.GA-v20150114-2029-B382) requires 'org.eclipse.core.runtime.compatibility.auth 0.0.0' but it could not be found > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19491) For JBIDE 4.2.3.Final: Prepare for JBT 4.2.3.Final / JBDS 8.1.0.GA [Base]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19491?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-19491. ---------------------------------- Assignee: Alexey Kazakov Resolution: Done > For JBIDE 4.2.3.Final: Prepare for JBT 4.2.3.Final / JBDS 8.1.0.GA [Base] > ------------------------------------------------------------------------- > > Key: JBIDE-19491 > URL: https://issues.jboss.org/browse/JBIDE-19491 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core, usage > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.2.3.Final > > > For JBIDE 4.2.3.Final [Base]: Please perform the following tasks: > *If you contributed anything to the 4.2.3.Beta1 or 4.2.3.CR1 builds, you will need to perform the following task.* > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.3.Final-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version: > {code} > mvn clean verify -Dtpc.version=4.42.0.Final-SNAPSHOT # or, once released > mvn clean verify -Dtpc.version=4.42.0.Final > {code} > 2. 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 Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19493) For JBIDE 4.2.3.Final: Prepare for JBT 4.2.3.Final / JBDS 8.1.0.GA [JavaEE]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19493?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-19493. ---------------------------------- Assignee: Alexey Kazakov Resolution: Done > For JBIDE 4.2.3.Final: Prepare for JBT 4.2.3.Final / JBDS 8.1.0.GA [JavaEE] > --------------------------------------------------------------------------- > > Key: JBIDE-19493 > URL: https://issues.jboss.org/browse/JBIDE-19493 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions, jsf, seam2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.2.3.Final > > > For JBIDE 4.2.3.Final [JavaEE]: Please perform the following tasks: > *If you contributed anything to the 4.2.3.Beta1 or 4.2.3.CR1 builds, you will need to perform the following task.* > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.3.Final-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version: > {code} > mvn clean verify -Dtpc.version=4.42.0.Final-SNAPSHOT # or, once released > mvn clean verify -Dtpc.version=4.42.0.Final > {code} > 2. 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 JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19489) For JBIDE 4.2.3.Final: Prepare for JBT 4.2.3.Final / JBDS 8.1.0.GA [JST]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19489?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-19489. ---------------------------------- Assignee: Alexey Kazakov Resolution: Done > For JBIDE 4.2.3.Final: Prepare for JBT 4.2.3.Final / JBDS 8.1.0.GA [JST] > ------------------------------------------------------------------------ > > Key: JBIDE-19489 > URL: https://issues.jboss.org/browse/JBIDE-19489 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.2.3.Final > > > For JBIDE 4.2.3.Final [JST]: Please perform the following tasks: > *If you contributed anything to the 4.2.3.Beta1 or 4.2.3.CR1 builds, you will need to perform the following task.* > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.3.Final-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version: > {code} > mvn clean verify -Dtpc.version=4.42.0.Final-SNAPSHOT # or, once released > mvn clean verify -Dtpc.version=4.42.0.Final > {code} > 2. 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 JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19362) Garbled text in forge list when SWT_GTK3 is true

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19362?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-19362: --------------------------------------- See https://bugs.eclipse.org/bugs/show_bug.cgi?id=446075#c27 > Garbled text in forge list when SWT_GTK3 is true > ------------------------------------------------ > > Key: JBIDE-19362 > URL: https://issues.jboss.org/browse/JBIDE-19362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.0.Beta1 > > Attachments: garbled-text.png > > > This is probably an older eclipse issue with GTK3 [1]. But if we can find some workaround for forge it would be nice. > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=446075 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3383) Include Feature Patch for WTP 3.6.3 into JBDS 8.1

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBDS-3383?page=com.atlassian.jira.plugin.... ] Victor Rubezhny edited comment on JBDS-3383 at 3/20/15 4:49 PM: ---------------------------------------------------------------- [~maxandersen] The following snippet: {code} var top = screen.height / 2; {code} is the simplest way to get into that infinite loop.For sure, there are other ways in a javascript to get the same result, but even when I saw this issue appearance it was pretty difficult to localize the problem until I've got this simple code that reproduces the issue. And yes, the fix is as easy as add the binding name into the set of names that are already processed. Otherwise, the binding has being constantly added to the bindings to process, so the for cycle at line 630 never ends... at least until the free memory come to the end. Regarding the producing of WTP v. 3.6.4... I see no chances to make it possible: there is only one Feature Patch made (this one) after 3.6.3 (SR2) is released. It could be possible in case some other Feature Patches were acquired, but there are not. I don't think it's OK for WTP to release another build just because of one issue. May be I'm too pessimistic, but I don't believe they will agree to produce 3.6.4. was (Author: vrubezhny): [~maxandersen] The following snippet: {code} var top = screen.height / 2; {code} is the simplest way to get into that infinite loop.For sure, there are other ways in a javascript to get the same result, but even when I saw this issue appearance it was pretty difficult to localize the problem. And yes, the fix is as easy as add the binding name into the set of names that are already processed. Otherwise, the binding has being constantly added to the bindings to process, so the for cycle at line 630 never ends... at least until the free memory come to the end. Regarding the producing of WTP v. 3.6.4... I see no chances to make it possible: there is only one Feature Patch made (this one) after 3.6.3 (SR2) is released. It could be possible in case some other Feature Patches were acquired, but there are not. I don't think it's OK for WTP to release another build just because of one issue. May be I'm too pessimistic, but I don't believe they will agree to produce 3.6.4. > Include Feature Patch for WTP 3.6.3 into JBDS 8.1 > ------------------------------------------------- > > Key: JBDS-3383 > URL: https://issues.jboss.org/browse/JBDS-3383 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: target-platform > Affects Versions: 8.1.0.CR1 > Reporter: Victor Rubezhny > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.GA > > Attachments: WTP Patches 3.6.3-P.png > > > When the fix for [Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515] was made, the WTP 3.6 stream was already closed (it's ended with 3.6 SR2), so the fix was made only for WTP 3.7 stream. > JSDT Feature Patch was made due to let the users to bring the fix back to their 3.6 SR2 environments. See: [Bug 461160 - Backport the fix for 'Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=461160] > Can we apply this fix into JBDS 8.1? > Technically, the Feature Patch installs org.eclipse.wst.jsdt.feature.patch feature that brings fixed org.eclipse.wst.jsdt.core_1.3.301.v201503171857.jar instead of org.eclipse.wst.jsdt.core_1.3.300.v201410221502.jar harmed by the bug. > Feature Patch is released at The Eclipse Web Tools Platform (WTP) software repository: http://download.eclipse.org/webtools/repository/luna -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3383) Include Feature Patch for WTP 3.6.3 into JBDS 8.1

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBDS-3383?page=com.atlassian.jira.plugin.... ] Victor Rubezhny edited comment on JBDS-3383 at 3/20/15 4:48 PM: ---------------------------------------------------------------- [~maxandersen] The following snippet: {code} var top = screen.height / 2; {code} is the simplest way to get into that infinite loop.For sure, there are other ways in a javascript to get the same result, but even when I saw this issue appearance it was pretty difficult to localize the problem. And yes, the fix is as easy as add the binding name into the set of names that are already processed. Otherwise, the binding has being constantly added to the bindings to process, so the for cycle at line 630 never ends... at least until the free memory come to the end. Regarding the producing of WTP v. 3.6.4... I see no chances to make it possible: there is only one Feature Patch made (this one) after 3.6.3 (SR2) is released. It could be possible in case some other Feature Patches were acquired, but there are not. I don't think it's OK for WTP to release another build just because of one issue. May be I'm too pessimistic, but I don't believe they will agree to produce 3.6.4. was (Author: vrubezhny): [~maxandersen] The following snippet: {code} var top = screen.height / 2; {code} is the simplest way to get into that infinite loop.For sure, there are other ways in a javascript to get the same result, but even I saw this issue appearance it was pretty difficult to localize the problem. And yes, the fix is as easy as add the binding name into the set of names that are already processed. Otherwise, the binding has being constantly added to the bindings to process, so the for cycle at line 630 never ends... at least until the free memory come to the end. Regarding the producing of WTP v. 3.6.4... I see no chances to make it possible: there is only one Feature Patch made (this one) after 3.6.3 (SR2) is released. It could be possible in case some other Feature Patches were acquired, but there are not. I don't think it's OK for WTP to release another build just because of one issue. May be I'm too pessimistic, but I don't believe they will agree to produce 3.6.4. > Include Feature Patch for WTP 3.6.3 into JBDS 8.1 > ------------------------------------------------- > > Key: JBDS-3383 > URL: https://issues.jboss.org/browse/JBDS-3383 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: target-platform > Affects Versions: 8.1.0.CR1 > Reporter: Victor Rubezhny > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.GA > > Attachments: WTP Patches 3.6.3-P.png > > > When the fix for [Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515] was made, the WTP 3.6 stream was already closed (it's ended with 3.6 SR2), so the fix was made only for WTP 3.7 stream. > JSDT Feature Patch was made due to let the users to bring the fix back to their 3.6 SR2 environments. See: [Bug 461160 - Backport the fix for 'Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=461160] > Can we apply this fix into JBDS 8.1? > Technically, the Feature Patch installs org.eclipse.wst.jsdt.feature.patch feature that brings fixed org.eclipse.wst.jsdt.core_1.3.301.v201503171857.jar instead of org.eclipse.wst.jsdt.core_1.3.300.v201410221502.jar harmed by the bug. > Feature Patch is released at The Eclipse Web Tools Platform (WTP) software repository: http://download.eclipse.org/webtools/repository/luna -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3383) Include Feature Patch for WTP 3.6.3 into JBDS 8.1

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBDS-3383?page=com.atlassian.jira.plugin.... ] Victor Rubezhny commented on JBDS-3383: --------------------------------------- [~maxandersen] The following snippet: {code} var top = screen.height / 2; {code} is the simplest way to get into that infinite loop.For sure, there are other ways in a javascript to get the same result, but even I saw this issue appearance it was pretty difficult to localize the problem. And yes, the fix is as easy as add the binding name into the set of names that are already processed. Otherwise, the binding has being constantly added to the bindings to process, so the for cycle at line 630 never ends... at least until the free memory come to the end. Regarding the producing of WTP v. 3.6.4... I see no chances to make it possible: there is only one Feature Patch made (this one) after 3.6.3 (SR2) is released. It could be possible in case some other Feature Patches were acquired, but there are not. I don't think it's OK for WTP to release another build just because of one issue. May be I'm too pessimistic, but I don't believe they will agree to produce 3.6.4. > Include Feature Patch for WTP 3.6.3 into JBDS 8.1 > ------------------------------------------------- > > Key: JBDS-3383 > URL: https://issues.jboss.org/browse/JBDS-3383 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: target-platform > Affects Versions: 8.1.0.CR1 > Reporter: Victor Rubezhny > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.GA > > Attachments: WTP Patches 3.6.3-P.png > > > When the fix for [Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515] was made, the WTP 3.6 stream was already closed (it's ended with 3.6 SR2), so the fix was made only for WTP 3.7 stream. > JSDT Feature Patch was made due to let the users to bring the fix back to their 3.6 SR2 environments. See: [Bug 461160 - Backport the fix for 'Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=461160] > Can we apply this fix into JBDS 8.1? > Technically, the Feature Patch installs org.eclipse.wst.jsdt.feature.patch feature that brings fixed org.eclipse.wst.jsdt.core_1.3.301.v201503171857.jar instead of org.eclipse.wst.jsdt.core_1.3.300.v201410221502.jar harmed by the bug. > Feature Patch is released at The Eclipse Web Tools Platform (WTP) software repository: http://download.eclipse.org/webtools/repository/luna -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3383) Include Feature Patch for WTP 3.6.3 into JBDS 8.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3383?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3383: ---------------------------------- Do you mean pushing WTP to do a full 3.6.4 release, instead of this patch-release? There was already a 3.6.3 on Feb 16 2015: http://download.eclipse.org/webtools/downloads/drops/R3.6.3/R-3.6.3-20150... > Include Feature Patch for WTP 3.6.3 into JBDS 8.1 > ------------------------------------------------- > > Key: JBDS-3383 > URL: https://issues.jboss.org/browse/JBDS-3383 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: target-platform > Affects Versions: 8.1.0.CR1 > Reporter: Victor Rubezhny > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.GA > > Attachments: WTP Patches 3.6.3-P.png > > > When the fix for [Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515] was made, the WTP 3.6 stream was already closed (it's ended with 3.6 SR2), so the fix was made only for WTP 3.7 stream. > JSDT Feature Patch was made due to let the users to bring the fix back to their 3.6 SR2 environments. See: [Bug 461160 - Backport the fix for 'Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=461160] > Can we apply this fix into JBDS 8.1? > Technically, the Feature Patch installs org.eclipse.wst.jsdt.feature.patch feature that brings fixed org.eclipse.wst.jsdt.core_1.3.301.v201503171857.jar instead of org.eclipse.wst.jsdt.core_1.3.300.v201410221502.jar harmed by the bug. > Feature Patch is released at The Eclipse Web Tools Platform (WTP) software repository: http://download.eclipse.org/webtools/repository/luna -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

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 March 2015