July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17826) Unable to run Aerogear Cordova project with CordovaSim

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17826?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-17826: ------------------------------------- No it worked with JBT 4.2.0.Beta3a. It was never working with JBDS 8.0.0.Beta3 unless nightly discovery sites were used. > Unable to run Aerogear Cordova project with CordovaSim > ------------------------------------------------------ > > Key: JBIDE-17826 > URL: https://issues.jboss.org/browse/JBIDE-17826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Affects Versions: 4.2.0.Beta3 > Environment: Fedora 18 KDE 64bit > JBDS 8.0.0.Beta3-v20140706-0939-B172 (jboss-devstudio-8.0.0.Beta3-v20140706-0939-B172-installer-eap.jar) > Oracle JDK 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.2.0.CR1 > > Attachments: central.png > > > 1. Import Hybrid Mobile Project from JBoss Central > 2. Run it with CordovaSim > ERROR: > {noformat} > no protocol: /home/vpakan/jbds800Beta3/studio/configuration > Stack trace: > java.net.MalformedURLException: no protocol: /home/vpakan/jbds800Beta3/studio/configuration > at java.net.URL.<init>(URL.java:586) > at java.net.URL.<init>(URL.java:483) > at java.net.URL.<init>(URL.java:432) > at org.jboss.tools.vpe.cordovasim.CordovaSimArgs.getPortFromURL(CordovaSimArgs.java:100) > at org.jboss.tools.vpe.cordovasim.CordovaSimArgs.parseArgs(CordovaSimArgs.java:51) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:88) > org.jboss.tools.vpe.cordovasim.model.preferences.CordavaSimSpecificPreferencesStorage.load()Ljava/lang/Object; > Stack trace: > java.lang.NoSuchMethodError: org.jboss.tools.vpe.cordovasim.model.preferences.CordavaSimSpecificPreferencesStorage.load()Ljava/lang/Object; > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.loadPreferences(CordovaSimRunner.java:165) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.createCordovaSim(CordovaSimRunner.java:179) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:110) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:89) > org.jboss.tools.vpe.cordavasim.command.stop.server: Server on port 0 was stopped > {noformat} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17826) Unable to run Aerogear Cordova project with CordovaSim

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17826?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-17826: ------------------------------------- [~vpakan], so it worked with Beta3a and stop working with Beta3b. What's in the stack trace? > Unable to run Aerogear Cordova project with CordovaSim > ------------------------------------------------------ > > Key: JBIDE-17826 > URL: https://issues.jboss.org/browse/JBIDE-17826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Affects Versions: 4.2.0.Beta3 > Environment: Fedora 18 KDE 64bit > JBDS 8.0.0.Beta3-v20140706-0939-B172 (jboss-devstudio-8.0.0.Beta3-v20140706-0939-B172-installer-eap.jar) > Oracle JDK 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.2.0.CR1 > > Attachments: central.png > > > 1. Import Hybrid Mobile Project from JBoss Central > 2. Run it with CordovaSim > ERROR: > {noformat} > no protocol: /home/vpakan/jbds800Beta3/studio/configuration > Stack trace: > java.net.MalformedURLException: no protocol: /home/vpakan/jbds800Beta3/studio/configuration > at java.net.URL.<init>(URL.java:586) > at java.net.URL.<init>(URL.java:483) > at java.net.URL.<init>(URL.java:432) > at org.jboss.tools.vpe.cordovasim.CordovaSimArgs.getPortFromURL(CordovaSimArgs.java:100) > at org.jboss.tools.vpe.cordovasim.CordovaSimArgs.parseArgs(CordovaSimArgs.java:51) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:88) > org.jboss.tools.vpe.cordovasim.model.preferences.CordavaSimSpecificPreferencesStorage.load()Ljava/lang/Object; > Stack trace: > java.lang.NoSuchMethodError: org.jboss.tools.vpe.cordovasim.model.preferences.CordavaSimSpecificPreferencesStorage.load()Ljava/lang/Object; > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.loadPreferences(CordovaSimRunner.java:165) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.createCordovaSim(CordovaSimRunner.java:179) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:110) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:89) > org.jboss.tools.vpe.cordavasim.command.stop.server: Server on port 0 was stopped > {noformat} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17173) Local EAP6/AS7 server fails to start properly when hostname is not localhost

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17173?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17173. --------------------------------- > Local EAP6/AS7 server fails to start properly when hostname is not localhost > ---------------------------------------------------------------------------- > > Key: JBIDE-17173 > URL: https://issues.jboss.org/browse/JBIDE-17173 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1 > OS X 10.9 Mavericks > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-b > Fix For: 4.2.0.Beta3 > > > When you change the host name property on a local EAP/AS server and then start the server, it has difficulty recognizing the server has started. > This is probably because you expect the server to listen to management commands at $hostname, but unless you select "Expose management port", the server will actually still bind the management port to localhost, not $hostname. > So the management startup poller will fail to recognize the server start. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17843) Connecting to a local JBoss AS process in JMX Navigator fails - java version

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17843?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17843. --------------------------------- Verified in JBDS 8.0.0.Beta3b B193 > Connecting to a local JBoss AS process in JMX Navigator fails - java version > ---------------------------------------------------------------------------- > > Key: JBIDE-17843 > URL: https://issues.jboss.org/browse/JBIDE-17843 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3 B172 running with java 8 > JBoss AS 7.1 running with java 6 > workspace default is java 8 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.Beta3 > > > I started a local JBoss AS 7.1 server and then tried to connect to the java process in JMX Navigator in Local Processes. > When I tried to connect, I got this in the server log: > {code} > Exception in thread "Attach Listener" 10:13:20,404 ERROR [stderr] (Attach Listener) java.lang.UnsupportedClassVersionError: org/jboss/tools/jmx/jvmmonitor/internal/agent/Agent : Unsupported major.minor version 51.0 > 10:13:20,405 ERROR [stderr] (Attach Listener) at java.lang.ClassLoader.defineClass1(Native Method) > 10:13:20,405 ERROR [stderr] (Attach Listener) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637) > 10:13:20,405 ERROR [stderr] (Attach Listener) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) > 10:13:20,406 ERROR [stderr] (Attach Listener) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) > 10:13:20,406 ERROR [stderr] (Attach Listener) at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) > 10:13:20,406 ERROR [stderr] (Attach Listener) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) > 10:13:20,406 ERROR [stderr] (Attach Listener) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) > 10:13:20,407 ERROR [stderr] (Attach Listener) at java.security.AccessController.doPrivileged(Native Method) > 10:13:20,407 ERROR [stderr] (Attach Listener) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > 10:13:20,407 ERROR [stderr] (Attach Listener) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > 10:13:20,407 ERROR [stderr] (Attach Listener) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > 10:13:20,408 ERROR [stderr] (Attach Listener) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) > 10:13:20,408 ERROR [stderr] (Attach Listener) at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:280) > 10:13:20,408 ERROR [stderr] (Attach Listener) at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:348) > Agent failed to start! > {code} > Java version 51.0 indicates Java SE 7. This is probably because the AS is running with java 6, but the attached agent jar is built with java 7. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17939) Move JMX Navigator location to bottom left

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17939?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17939: ---------------------------------- Description: I was quite confused by the UI of JMX Navigator and Properties view - when I was connected to more than 1 local processes, I was wondering which one I was viewing in the Properties view. It turns out that all throughout Eclipse, the Properties view usually shows details for an item that is currently selected in another view. But this can be confusing, because by default, both JMX Navigator and Properties views use the same window/location. So you never see both of them at once. Rob suggested that the JMX Navigator could have a default location of botton left - below Project Explorer. I like the idea. But right now we don't display anything in that area. So Rob needs to investigate if this will work. We need it to work for both scenarios: 1. Server -> Shown in JMX Navigator 2. Open the JMX Navigator using Window -> Show view was: I was quite confused by the UI of JMX Navigator and Properties view - when I was connected to more than 1 local processes, I was wondering which one I was viewing in the Properties view. It turns out that all throughout Eclipse, the Properties view usually shows details for an item that is currently selected in another view. But this can be confusing, because by default, both JMX Navigator and Properties views use the same window/location. So you never see both of them at once. Rob suggested that the JMX Navigator could have a default location of botton left - below Project Explorer. I like the idea. But right now we don't display anything in that area. So Rob needs to investigate if this will work. > Move JMX Navigator location to bottom left > ------------------------------------------ > > Key: JBIDE-17939 > URL: https://issues.jboss.org/browse/JBIDE-17939 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jmx, server > Affects Versions: 4.2.0.Beta3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > I was quite confused by the UI of JMX Navigator and Properties view - when I was connected to more than 1 local processes, I was wondering which one I was viewing in the Properties view. > It turns out that all throughout Eclipse, the Properties view usually shows details for an item that is currently selected in another view. But this can be confusing, because by default, both JMX Navigator and Properties views use the same window/location. So you never see both of them at once. > Rob suggested that the JMX Navigator could have a default location of botton left - below Project Explorer. I like the idea. But right now we don't display anything in that area. So Rob needs to investigate if this will work. > We need it to work for both scenarios: > 1. Server -> Shown in JMX Navigator > 2. Open the JMX Navigator using Window -> Show view -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17894) Generate Entities From Tables is blocked

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17894?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-17894: --------------------------------------- Not for me, I have 720p as the highest, weird. https://www.dropbox.com/s/osup9hsk304ieaw/Screenshot%202014-07-21%2011.14... > Generate Entities From Tables is blocked > ---------------------------------------- > > Key: JBIDE-17894 > URL: https://issues.jboss.org/browse/JBIDE-17894 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Pavol Srna > Priority: Blocker > Fix For: 4.2.0.CR1 > > Attachments: jstack.txt > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17939) Move JMX Navigator location to bottom left

by Martin Malina (JIRA)

Martin Malina created JBIDE-17939: ------------------------------------- Summary: Move JMX Navigator location to bottom left Key: JBIDE-17939 URL: https://issues.jboss.org/browse/JBIDE-17939 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jmx, server Affects Versions: 4.2.0.Beta3 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.2.0.CR1 I was quite confused by the UI of JMX Navigator and Properties view - when I was connected to more than 1 local processes, I was wondering which one I was viewing in the Properties view. It turns out that all throughout Eclipse, the Properties view usually shows details for an item that is currently selected in another view. But this can be confusing, because by default, both JMX Navigator and Properties views use the same window/location. So you never see both of them at once. Rob suggested that the JMX Navigator could have a default location of botton left - below Project Explorer. I like the idea. But right now we don't display anything in that area. So Rob needs to investigate if this will work. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17894) Generate Entities From Tables is blocked

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17894?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17894: --------------------------------------------- the highest resolution available is 360: http://screencast.com/t/P2m0RHCfjaly i'll try run through these steps though - thanks for providing them. > Generate Entities From Tables is blocked > ---------------------------------------- > > Key: JBIDE-17894 > URL: https://issues.jboss.org/browse/JBIDE-17894 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Pavol Srna > Priority: Blocker > Fix For: 4.2.0.CR1 > > Attachments: jstack.txt > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17840) Eclipse Thym release should be able to replace JBDS hybrid mobile tools

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17840?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-17840. ------------------------------- Verified with JBDS Beta3-v20140718-2145-B193 Once Thym installed it's not possible to run Hybrid Mobile project with CordovaSim. I guess it's part of another issue? > Eclipse Thym release should be able to replace JBDS hybrid mobile tools > ----------------------------------------------------------------------- > > Key: JBIDE-17840 > URL: https://issues.jboss.org/browse/JBIDE-17840 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta2 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.2.0.Beta3 > > > Releases from Eclipse Thym should be able to update JBDS 4.2.0 Beta3 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11996) Persistence unit not found for default JPA project with DB connection string when Eclipse is run with JDK7

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11996?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-11996. -------------------------------- Verified with JBDS 8.0.0.Beta3b, GNU/Linux 64 > Persistence unit not found for default JPA project with DB connection string when Eclipse is run with JDK7 > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-11996 > URL: https://issues.jboss.org/browse/JBIDE-11996 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 3.3.0.CR1 > Environment: JBT 3.3.CR1-trunk, L64, HSQL 1.8 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.2.0.Beta3 > > > org.hibernate.console.HibernateConsoleRuntimeException: Persistence unit not found: 'null'. > at org.hibernate.console.ConfigurationFactory.buildJPAConfiguration(ConfigurationFactory.java:235) > at org.hibernate.console.ConfigurationFactory.buildConfiguration(ConfigurationFactory.java:174) > at org.hibernate.console.ConfigurationFactory.createConfiguration(ConfigurationFactory.java:96) > at org.hibernate.console.ConsoleConfiguration$3.execute(ConsoleConfiguration.java:240) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107) > at org.hibernate.console.ConsoleConfiguration.buildWith(ConsoleConfiguration.java:237) > at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:188) > at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:42) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

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