October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18571) Some platform bundles comes from pre-SR1 build in CR2 builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18571?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-18571 at 10/16/14 8:37 AM: -------------------------------------------------------------- Note that in the p2diff, 201409180900-SR1 contains 461 unique IUs, whereas in the SR1a there are only 458. Here are the IUs that disappeared / appeared between the releases: {code:title=Added in SR1a http://download.eclipse.org/releases/luna/201409261001} org.eclipse.jdt.core org.eclipse.objectteams.otdt.core.patch.feature.group {code} {code:title=Removed after SR1 http://download.jboss.org/jbosstools/updates/requirements/luna/2014091809... org.eclipse.rap.jface org.eclipse.rap.jface.databinding org.eclipse.rap.rwt org.eclipse.rcp.configuration_root.cocoa.macosx.x86 org.eclipse.rcp.configuration_root.cocoa.macosx.x86_64 {code} was (Author: nickboldt): Note that in the p2diff, 201409180900-SR1 contains 461 unique IUs, whereas in the SR1a there are only 458. Here are the IUs that disappeared / appeared between the releases: {code:title=http://download.eclipse.org/releases/luna/201409261001} org.eclipse.jdt.core org.eclipse.objectteams.otdt.core.patch.feature.group {code} {code:title=http://download.jboss.org/jbosstools/updates/requirements/luna/201409180900-SR1/} org.eclipse.rap.jface org.eclipse.rap.jface.databinding org.eclipse.rap.rwt org.eclipse.rcp.configuration_root.cocoa.macosx.x86 org.eclipse.rcp.configuration_root.cocoa.macosx.x86_64 {code} > Some platform bundles comes from pre-SR1 build in CR2 builds > ------------------------------------------------------------ > > Key: JBIDE-18571 > URL: https://issues.jboss.org/browse/JBIDE-18571 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.CR2 > Reporter: Martin Malina > Assignee: Mickael Istria > Priority: Minor > Labels: respin-b > Fix For: 4.2.0.CR2 > > Attachments: p2diff_SR1_SR1a > > > JBoss Tools 4.2.0.CR2 / JBDS 8.0.0.CR2 should use Eclipse Luna SR1 (4.4.1), but everywhere we look, we see this Eclipse Platform feature: > org.eclipse.platform_4.4.0.v20140911-0143.jar > In both JBT and JBDS target platforms: > http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... > Also, I can see this version in my local installation of JBDS 8.0.0.CR1 B286. > I know about JBIDE-18539 - that Eclipse didn't upversion the platform, so it's still 4.4.0 for SR1, but at least the time stamp should be v20140925 as mentioned in that JIRA. This seems like we don't have SR1 at all. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18571) Some platform bundles comes from pre-SR1 build in CR2 builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18571?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18571: ------------------------------------ Note that in the p2diff, 201409180900-SR1 contains 461 unique IUs, whereas in the SR1a there are only 458. Here are the IUs that disappeared / appeared between the releases: {code:title=http://download.eclipse.org/releases/luna/201409261001} org.eclipse.jdt.core org.eclipse.objectteams.otdt.core.patch.feature.group {code} {code:title=http://download.jboss.org/jbosstools/updates/requirements/luna/201409180900-SR1/} org.eclipse.rap.jface org.eclipse.rap.jface.databinding org.eclipse.rap.rwt org.eclipse.rcp.configuration_root.cocoa.macosx.x86 org.eclipse.rcp.configuration_root.cocoa.macosx.x86_64 {code} > Some platform bundles comes from pre-SR1 build in CR2 builds > ------------------------------------------------------------ > > Key: JBIDE-18571 > URL: https://issues.jboss.org/browse/JBIDE-18571 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.CR2 > Reporter: Martin Malina > Assignee: Mickael Istria > Priority: Minor > Labels: respin-b > Fix For: 4.2.0.CR2 > > Attachments: p2diff_SR1_SR1a > > > JBoss Tools 4.2.0.CR2 / JBDS 8.0.0.CR2 should use Eclipse Luna SR1 (4.4.1), but everywhere we look, we see this Eclipse Platform feature: > org.eclipse.platform_4.4.0.v20140911-0143.jar > In both JBT and JBDS target platforms: > http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... > Also, I can see this version in my local installation of JBDS 8.0.0.CR1 B286. > I know about JBIDE-18539 - that Eclipse didn't upversion the platform, so it's still 4.4.0 for SR1, but at least the time stamp should be v20140925 as mentioned in that JIRA. This seems like we don't have SR1 at all. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18247) Eclipse is blocked for several minutes on startup when HTTP/80 is firewalled

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18247?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-18247: ------------------------------------ I've tried to build jbosstools-base 4.2.x branch and install all from the site into cr2a. The fix works. > Eclipse is blocked for several minutes on startup when HTTP/80 is firewalled > ---------------------------------------------------------------------------- > > Key: JBIDE-18247 > URL: https://issues.jboss.org/browse/JBIDE-18247 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Assignee: Fred Bricon > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.CR2 > > Attachments: console-log.txt, eclipse-firewalled-jstack.txt, stack-cr1a.txt > > > Imagine a situation where you are behind firewall which blocks HTTP/80. > You unpack fresh eclipse and install jbosstools. After installation you are prompted to restart eclipse. But eclipse is blocked at startup for several minutes - there is blocking central thread which cannot access web because of firewall. > If you don't forget to setup proxy in eclipse you won't experience this. But otherwise you will be stucked on eclipse startup. And that is bad user experience. > I would suggest to fix it so, that eclipse can at least start - just central content is not loaded when http is blocked. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18138) Javascript errors when importing Aerogear Quickstarts

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18138?page=com.atlassian.jira.plugi... ] Victor Rubezhny edited comment on JBIDE-18138 at 10/16/14 8:10 AM: ------------------------------------------------------------------- Once WTP 3.6.2/3.7.0 is released, there will be a new preference available for disabling the strict validation for keywords usage. The preference enables strict validation by default, so error markers are to be shown on 'improper' keywords usage. This PR turns the strict keyword validation off, so there is no need to make it manually. However this 'automatic' turn will stop to disable strict validation once a user has modified the value of JSDT's 'strict keyword validation' preference (The key is: if a user knows how to turn on the strict validation, he/she knows how to turn it off the same way, so we don't need to help him anymore). was (Author: vrubezhny): Once WTP 3.6.2/3.7.0 is released, there will be a new preference available for disabling the strict validation for keywords usage. The preference enables strict validation by default, so error markers are to be shown on 'improper' keywords usage. This PR turns the strict keyword validation off, so there is no need to make it manually. However this 'automatic' turn will stop to disable strict validation once a user has modified the value of JSDT's 'strict keyword validation' preference (The key is: if a user can turn on the strict validation, he/she can turn it off the same way, so we don't need to help him anymore). > Javascript errors when importing Aerogear Quickstarts > ----------------------------------------------------- > > Key: JBIDE-18138 > URL: https://issues.jboss.org/browse/JBIDE-18138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.CR1 > Reporter: Burr Sutter > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > Attachments: error screenshot on CR1.png > > > Testing of: > https://github.com/aerogear/aerogear-push-quickstarts/tree/master/client/... > https://github.com/aerogear/aerogear-push-quickstarts/tree/master/client/... > Errors: > http://screencast.com/t/hnI0WZFpxz > http://screencast.com/t/fGiVBQdm -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3181) Include EAP 6.3.1 in JBDS 8.0.0 installer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3181?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3181: ------------------------------------------- when we shipped EAP 5 we did it with EAP 5 + seamgen patches. > Include EAP 6.3.1 in JBDS 8.0.0 installer > ----------------------------------------- > > Key: JBDS-3181 > URL: https://issues.jboss.org/browse/JBDS-3181 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.CR2 > Reporter: Nick Boldt > Assignee: Burr Sutter > Priority: Blocker > Fix For: 8.0.0.GA > > > EAP 6.3.1 is available [1]. > Should we include it in the JBDS 8.0.0.GA installer as part of this week's respin-b / rename for GA dance, or are we prevented from doing so by some sort of subscription rules? > [1] http://download.devel.redhat.com/released/JBEAP-6/6.3.1/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18650) Forge wizard window isn't focused after command selection (CTRL-4)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18650: ---------------------------------------- Assignee: Snjezana Peco > Forge wizard window isn't focused after command selection (CTRL-4) > ------------------------------------------------------------------ > > Key: JBIDE-18650 > URL: https://issues.jboss.org/browse/JBIDE-18650 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Environment: jbds 8.0.0.CR1 > [selrahal@fedora20 jbdevstudio]$ uname -a > Linux fedora20 3.15.10-201.fc20.x86_64 #1 SMP Wed Aug 27 21:10:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > [selrahal@fedora20 jbdevstudio]$ java -version > java version "1.7.0_65" > OpenJDK Runtime Environment (fedora-2.5.1.3.fc20-x86_64 u65-b17) > OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) > Reporter: Salem Elrahal > Assignee: Snjezana Peco > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > I have created a new project and used forge to add a JPA entity. I select the class, use ctrl+4 to bring up the forge 2 UI, and select 'JPA: New Field'. The new window pops up but is not in focus. I have to then click on the window to enter the field name etc... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18650) Forge wizard window isn't focused after command selection (CTRL-4)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18650: --------------------------------------------- [~snjeza] can you help locate the source of the issue here ? my guess is some SWT/GTK2/3 incompatbility or some special case in the way cmd+4 works that triggers focus bug. > Forge wizard window isn't focused after command selection (CTRL-4) > ------------------------------------------------------------------ > > Key: JBIDE-18650 > URL: https://issues.jboss.org/browse/JBIDE-18650 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Environment: jbds 8.0.0.CR1 > [selrahal@fedora20 jbdevstudio]$ uname -a > Linux fedora20 3.15.10-201.fc20.x86_64 #1 SMP Wed Aug 27 21:10:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > [selrahal@fedora20 jbdevstudio]$ java -version > java version "1.7.0_65" > OpenJDK Runtime Environment (fedora-2.5.1.3.fc20-x86_64 u65-b17) > OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) > Reporter: Salem Elrahal > Assignee: Snjezana Peco > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > I have created a new project and used forge to add a JPA entity. I select the class, use ctrl+4 to bring up the forge 2 UI, and select 'JPA: New Field'. The new window pops up but is not in focus. I have to then click on the window to enter the field name etc... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18650) Forge wizard window isn't focused after command selection (CTRL-4)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18650: ---------------------------------------- Fix Version/s: 4.2.1.Final 4.3.0.Alpha1 > Forge wizard window isn't focused after command selection (CTRL-4) > ------------------------------------------------------------------ > > Key: JBIDE-18650 > URL: https://issues.jboss.org/browse/JBIDE-18650 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Environment: jbds 8.0.0.CR1 > [selrahal@fedora20 jbdevstudio]$ uname -a > Linux fedora20 3.15.10-201.fc20.x86_64 #1 SMP Wed Aug 27 21:10:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > [selrahal@fedora20 jbdevstudio]$ java -version > java version "1.7.0_65" > OpenJDK Runtime Environment (fedora-2.5.1.3.fc20-x86_64 u65-b17) > OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) > Reporter: Salem Elrahal > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > I have created a new project and used forge to add a JPA entity. I select the class, use ctrl+4 to bring up the forge 2 UI, and select 'JPA: New Field'. The new window pops up but is not in focus. I have to then click on the window to enter the field name etc... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18650) Forge wizard window isn't focused after command selection (CTRL-4)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18650: --------------------------------------------- :) great then this is a Mutter/swt issue until proven otherwise. moving off as a blocker for GA. > Forge wizard window isn't focused after command selection (CTRL-4) > ------------------------------------------------------------------ > > Key: JBIDE-18650 > URL: https://issues.jboss.org/browse/JBIDE-18650 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Environment: jbds 8.0.0.CR1 > [selrahal@fedora20 jbdevstudio]$ uname -a > Linux fedora20 3.15.10-201.fc20.x86_64 #1 SMP Wed Aug 27 21:10:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > [selrahal@fedora20 jbdevstudio]$ java -version > java version "1.7.0_65" > OpenJDK Runtime Environment (fedora-2.5.1.3.fc20-x86_64 u65-b17) > OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) > Reporter: Salem Elrahal > > I have created a new project and used forge to add a JPA entity. I select the class, use ctrl+4 to bring up the forge 2 UI, and select 'JPA: New Field'. The new window pops up but is not in focus. I have to then click on the window to enter the field name etc... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18647) For JBIDE 4.2.0.Final: Prepare for Final/GA release [Portlet]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18647?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-18647. --------------------------------- Resolution: Done > For JBIDE 4.2.0.Final: Prepare for Final/GA release [Portlet] > ------------------------------------------------------------- > > Key: JBIDE-18647 > URL: https://issues.jboss.org/browse/JBIDE-18647 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: portal-gatein > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.2.0.Final > > > For JBIDE 4.2.0.Final [Portlet]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Final-SNAPSHOT</version> > </parent> > {code} > 2. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.Final-SNAPSHOT > {code} > 4. 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 Portlet task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 October 2014