October 2014 - jbosstools-issues - Jboss List Archives

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

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-18650: ------------------------------------ Hey [~maxandersen], you are right as always ;-) fedora20 uses Mutter and Ubuntu 14.04 Compiz. I've installed Mutter on my ubuntu and then I've replaced default window manager with Mutter. I can reproduce the issue on ubuntu running with Mutter window manager. > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-512) OpenShift How To: Manage Existing Applications

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-512?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-512: -------------------------------------------- Hi [~mmurray] and [~aakanksha], Please review the Work with Existing OpenShift Applications article located at: https://docs.google.com/a/redhat.com/document/d/1GQmZvunNDPnpHytNKLEt2C2T... Thanks, Supriya > OpenShift How To: Manage Existing Applications > ---------------------------------------------- > > Key: TOOLSDOC-512 > URL: https://issues.jboss.org/browse/TOOLSDOC-512 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: User Guide - OpenShift Tools > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Final > > > Article 3: > Deploy an Existing Workspace Application > Introductory paragraphs > In the New OpenShift Application wizard, click Use my existing OpenShift application and then click Browse to look for the application > Detailed steps > Import a Running Application to a Workspace > Introductory paragraphs > Click File > Import. Expand OpenShift and click Existing OpenShift Application and then click Next > Detailed steps -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-510) OpenShift How To: Establish an OpenShift Connection

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-510?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-510: -------------------------------------------- Hi [~mmurray] and [~aakanksha_writer], Please reviwe the Establish an OpenShift Connection article that is located at: https://docs.google.com/a/redhat.com/document/d/1a2tXP8JKWbhoesw7rKzkBROF... Thanks, Supriya > OpenShift How To: Establish an OpenShift Connection > --------------------------------------------------- > > Key: TOOLSDOC-510 > URL: https://issues.jboss.org/browse/TOOLSDOC-510 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: User Guide - OpenShift Tools > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Final > > > Article 1: Establish Connection with OpenShift > Introductory paragraphs > Create user online account (will this be a prerequisite to this task?) > Take user through steps to create the account > If OpenShift Explorer view is not visible: click Windows > Show View > Others. Expand JBoss Tools and select OpenShift > Once OpenShift Online account is ready: > Click the Connections icon,... > Take user through steps to connect > Set the SSH keys: From the OpenShift Explorer view, right-click the connection and click Manage SSH Keys. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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: --------------------------------------------- gnome is not the window manager afaik - thats just the toolkit. metacity ? unity? cinnamon ? > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18540) JPP examples in JBoss Central requires JPP 6.2 artifacts

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18540?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18540. ------------------------------ Portal examples are now OK in JBT 4.2.0.CR2a. > JPP examples in JBoss Central requires JPP 6.2 artifacts > -------------------------------------------------------- > > Key: JBIDE-18540 > URL: https://issues.jboss.org/browse/JBIDE-18540 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.2.0.CR2 > Environment: JBT 4.2.0.CR2 > Reporter: Radim Hopp > Assignee: Peter Palaga > Priority: Critical > Fix For: 4.2.0.CR2 > > > Portal Application examples referenced from JBoss Central requires JPP 6.2. artifacts, which are not yet available publicly (on http://maven.repository.redhat.com/techpreview/all/) thus contains lot of errors after importing. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

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

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-18650: ------------------------------------ I believe that fedora20 comes with gnome 3.10. and ubuntu 14.04 too. > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18540) JPP examples in JBoss Central requires JPP 6.2 artifacts

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18540?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-18540: ------------------------------- Fix Version/s: 4.2.0.CR2 > JPP examples in JBoss Central requires JPP 6.2 artifacts > -------------------------------------------------------- > > Key: JBIDE-18540 > URL: https://issues.jboss.org/browse/JBIDE-18540 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.2.0.CR2 > Environment: JBT 4.2.0.CR2 > Reporter: Radim Hopp > Assignee: Peter Palaga > Priority: Critical > Fix For: 4.2.0.CR2 > > > Portal Application examples referenced from JBoss Central requires JPP 6.2. artifacts, which are not yet available publicly (on http://maven.repository.redhat.com/techpreview/all/) thus contains lot of errors after importing. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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: --------------------------------------------- any difference in window manager for those two ? can you try use the same ? > 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, 7 months

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18628?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18628: --------------------------------------- {quote} This fails with clean workspace if jbds with bundled eap is used. {quote} And when you have bundled EAP, it runs runtime detection on it, so it creates the profile. So the prerequisite of this bug still seems to be that you need an existing data source profile in order to reproduce this. > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-337) Installation: Add test case covers features version check

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-337?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík edited comment on JBTIS-337 at 10/16/14 4:30 AM: -------------------------------------------------------------- -Add report generation - HTML format, user friendly- * added report generation * added hash comparison between same features was (Author: tsedmik): TODO Add report generation - HTML format, user friendly > Installation: Add test case covers features version check > --------------------------------------------------------- > > Key: JBTIS-337 > URL: https://issues.jboss.org/browse/JBTIS-337 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Original Estimate: 2 days > Time Spent: 4 days > Remaining Estimate: 0 minutes > > Check versions of features on an Eclipse update site against an older update site -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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