October 2014 - jbosstools-issues - Jboss List Archives

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ] Lincoln Baxter III updated JBIDE-18650: --------------------------------------- Summary: Forge wizard window isn't focused after command selection (CTRL-4) (was: JPA:New Field window doesn't start in focus) > 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 > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18650) JPA:New Field window doesn't start in focus

by Salem Elrahal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ] Salem Elrahal commented on JBIDE-18650: --------------------------------------- Update: This does not only happen to the JPA: New Field command, but for every command. When I press ctrl+4 the window that comes up is in focus, but after selecting any command the new window is never in focus. I always need to click on it. > JPA:New Field window doesn't start in focus > ------------------------------------------- > > Key: JBIDE-18650 > URL: https://issues.jboss.org/browse/JBIDE-18650 > Project: Tools (JBoss Tools) > Issue Type: Bug > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3183) Usage website does not contain ws tester reporting

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3183?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3183: -------------------------------------- The PR has been merged. > Usage website does not contain ws tester reporting > -------------------------------------------------- > > Key: JBDS-3183 > URL: https://issues.jboss.org/browse/JBDS-3183 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: usage, website > Affects Versions: 8.0.0.CR2 > Reporter: Radim Hopp > Assignee: Radim Hopp > Priority: Minor > > Usage website is missing info about Web Service Tester usage reporting. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

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

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18571?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18571: ---------------------------------------- Mirroring in progress at http://download.jboss.org/jbosstools/updates/requirements/luna/2014092610... > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18628) NPE when creating Connection Profile using forge wizard

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18628?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18628: --------------------------------------------- ah - so this is not an absolute blocker. Forge should be fixed to not rely on the path being always filled at this stage IMO. We can put it as a workaround for GA. btw. I dont see any errors otherwise in the screecast - does things just otherwise work or ? > NPE when creating Connection Profile using forge wizard > ------------------------------------------------------- > > Key: JBIDE-18628 > URL: https://issues.jboss.org/browse/JBIDE-18628 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR2 > Reporter: Pavol Srna > Priority: Blocker > Labels: regression > Fix For: 4.2.0.CR2 > > > {code} > java.lang.NullPointerException > at java.util.Hashtable.put(Hashtable.java:459) > at java.util.Properties.setProperty(Properties.java:166) > at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.createProperties(ConnectionProfileManagerImpl.java:172) > at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveExistingProfile(ConnectionProfileManagerImpl.java:82) > at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveConnectionProfile(ConnectionProfileManagerImpl.java:73) > at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveConnectionProfiles(ConnectionProfileManagerImpl.java:142) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) > at org.jboss.forge.addon.database.tools.connections.ConnectionProfileManager_$$_javassist_38d8b832-4a59-46f2-bc9d-eb9ff785daba.saveConnectionProfiles(ConnectionProfileManager_$$_javassist_38d8b832-4a59-46f2-bc9d-eb9ff785daba.java) > at org.jboss.forge.addon.database.tools.connections.ui.CreateConnectionProfileCommandImpl.execute(CreateConnectionProfileCommandImpl.java:62) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103) > at org.jboss.forge.addon.database.tools.connections.ui.CreateConnectionProfileCommandImpl_$$_javassist_e7993baf-c96e-4b2e-9196-875229a146df.execute(CreateConnectionProfileCommandImpl_$$_javassist_e7993baf-c96e-4b2e-9196-875229a146df.java) > at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) > at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_7a19049c-bb8a-4bcc-9fab-671730e3e0e2.execute(CommandController_$$_javassist_7a19049c-bb8a-4bcc-9fab-671730e3e0e2.java) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard$1.run(ForgeWizard.java:113) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

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

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18644?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-18644: ------------------------------------- Assignee: Xavier Coulon > For JBIDE 4.2.0.Final: Prepare for Final/GA release [Webservices] > ----------------------------------------------------------------- > > Key: JBIDE-18644 > URL: https://issues.jboss.org/browse/JBIDE-18644 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.2.0.Final > > > For JBIDE 4.2.0.Final [Webservices]: 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 Webservices 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, 8 months

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3181?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3181: ------------------------------------- [~nickboldt], just to clarify: They're non-free, and non-existent :) You can only download the patch if you're a paying customer, but not the full zip of a .x EAP release. Also, we (QE) do test the patch releases today. Typically the EAP QE team is the first to test those (before they release them) and afterwards it's us. But to be 100% honest, I did this mostly for EAP 6.2.1 and 6.2.2, not so much in case of 6.3.1 yet. > 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, 8 months

1
0
0 / 0

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

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18649?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-18649: ------------------------------------- Assignee: Xavier Coulon > For JBIDE 4.2.0.Final: Prepare for Final/GA release [LiveReload] > ---------------------------------------------------------------- > > Key: JBIDE-18649 > URL: https://issues.jboss.org/browse/JBIDE-18649 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.2.0.Final > > > For JBIDE 4.2.0.Final [LiveReload]: 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 LiveReload 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18650) JPA:New Field window doesn't start in focus

by Salem Elrahal (JIRA)

Salem Elrahal created JBIDE-18650: ------------------------------------- Summary: JPA:New Field window doesn't start in focus Key: JBIDE-18650 URL: https://issues.jboss.org/browse/JBIDE-18650 Project: Tools (JBoss Tools) Issue Type: Feature Request 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 Priority: Minor 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18650) JPA:New Field window doesn't start in focus

by Salem Elrahal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ] Salem Elrahal updated JBIDE-18650: ---------------------------------- Priority: Major (was: Minor) > JPA:New Field window doesn't start in focus > ------------------------------------------- > > Key: JBIDE-18650 > URL: https://issues.jboss.org/browse/JBIDE-18650 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > 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, 8 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