February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-18581) jboss-kitchensink-backbone's graph profile defines repo which cannot be loaded

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18581?page=com.atlassian.jira.plugi... ] Sande Gilda commented on JBIDE-18581: ------------------------------------- [~fbricon]: Sorry, I just saw the email. I am not familiar with this change. Is this a WFK quickstart? Is it resolved? If I don't respond in the future, please ping me on IRC. > jboss-kitchensink-backbone's graph profile defines repo which cannot be loaded > ------------------------------------------------------------------------------ > > Key: JBIDE-18581 > URL: https://issues.jboss.org/browse/JBIDE-18581 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.2.0.CR2 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.2.3.Beta1 > > > graph profile defines http://mvnplugins.fusesource.org/repo/releas which always timed out for me. Im unable to open in via browser either. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18979) Unable to run CordovaSim with Fedora 21 KDE

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18979?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18979: ------------------------------------- [~vpakan], what shall we do with this issue? It seems that it depends dramatically on some os updates / configs. Are you still facing it on Fedora 20? > Unable to run CordovaSim with Fedora 21 KDE > ------------------------------------------- > > Key: JBIDE-18979 > URL: https://issues.jboss.org/browse/JBIDE-18979 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.2.1.Final > Environment: JBDS 8.0.1.CR1-v20141207-0100-B352, Java Oracle 1.8 > Fedora 21 KDE 64 bit > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.3.0.Alpha1 > > Attachments: fedora.png, webkit.png > > > 1. Run default Hybrid Mobile app with CordovaSim > {noformat} > No bp log location saved, using default. > [000:000] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:000] Computer model: Not available > [000:000] Browser XEmbed support present: 1 > [000:000] Browser toolkit is Gtk2. > [000:003] Using Gtk2 toolkit > No bp log location saved, using default. > [000:000] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:001] Computer model: Not available > [000:497] Warning(optionsfile.cc:30): Load: Could not open file, err=2 > [000:497] No bp log location saved, using default. > [000:497] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:497] Computer model: Not available > [000:498] Browser XEmbed support present: 1 > [000:498] Browser toolkit is Gtk2. > [000:498] Using Gtk2 toolkit > [000:003] Warning(optionsfile.cc:30): Load: Could not open file, err=2 > [000:003] No bp log location saved, using default. > [000:004] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:004] Computer model: Not available > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x000000370a80c42b, pid=13580, tid=140558422947584 > # > # JRE version: Java(TM) SE Runtime Environment (8.0-b132) (build 1.8.0-b132) > # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.0-b70 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [ld-linux-x86-64.so.2+0xc42b] > # > # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again > # > # An error report file with more information is saved as: > # /home/vpakan/hs_err_pid13580.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.sun.com/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18900) CordovaSim: Can't run default FeedHenry app locally

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18900?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18900: ------------------------------------- [~vpakan], nightly has been updated. Could you please reinstall plugins and verify? > CordovaSim: Can't run default FeedHenry app locally > --------------------------------------------------- > > Key: JBIDE-18900 > URL: https://issues.jboss.org/browse/JBIDE-18900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.0.Alpha1 > > Attachments: configuration.png, cordovasimFH.png, FHshortcuts.png, hello_tom.png, newLaunch.png, preferences.png, ToolsProject-Cloud-App.zip, ToolsProject-Cordova-App.zip > > > Basically, the situation is the following: > 1. *ToolsProject-Cordova-App.zip* - is a basic FH hybrid app (all the app does is saying Hello + 'username' from the input field ) > 2. To run this app one simply needs to unpack the archive and import it as a cordova project to the studio > 3. The application will work with a *remote* server like a charm !hello_tom.png|thumbnail! > 4. However, there is an option to use *local* server instead of *remote* one > 5. *ToolsProject-Cloud-App.zip* - is a app for running local server via grunt task runner > 6. In order to run local server one needs: > - unpack the app > - run *npm install .* > - run *grunt serve* > Need to find the way to made CordovaSim use this *local* server -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19175) Console configuration hibernate not found error when generating JPA Entities with disabled console setting

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-19175: ------------------------------------ Summary: Console configuration hibernate not found error when generating JPA Entities with disabled console setting Key: JBIDE-19175 URL: https://issues.jboss.org/browse/JBIDE-19175 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.2.2.Final Environment: JBDS 8.0.2 GA, L64 Reporter: Jiri Peterka Priority: Critical Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 Console configuration hibernate not found error occurs when I try to generate entities without using hibernate console -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19153) Unable to use hibernate console when DTD is not accessible (hibernate.org down)

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19153?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-19153: -------------------------------------- Site down JIRA - https://hibernate.atlassian.net/browse/WEBSITE-252 > Unable to use hibernate console when DTD is not accessible (hibernate.org down) > ------------------------------------------------------------------------------- > > Key: JBIDE-19153 > URL: https://issues.jboss.org/browse/JBIDE-19153 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Final > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > > Inaccessible DTD causes blocking Hibernate Console usage (as DTD cannot be loaded) > If DTD is not accessible It would be more useful to disable DTD validation rather than block further usage and just show some warning. > {code} > org.hibernate.HibernateException: Could not parse configuration: C:\Users\jpeterka\workspace\tmp\hb\mvn-hibernate35\src\main\java\hibernate.cfg.xml > at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1586) > at org.hibernate.cfg.Configuration.configure(Configuration.java:1554) > at org.jboss.tools.hibernate.proxy.ConfigurationProxy.configure(ConfigurationProxy.java:94) > at org.hibernate.console.ConfigurationFactory.loadConfigurationXML(ConfigurationFactory.java:350) > at org.hibernate.console.ConfigurationFactory.configureStandardConfiguration(ConfigurationFactory.java:278) > at org.hibernate.console.ConfigurationFactory.buildConfiguration(ConfigurationFactory.java:175) > at org.hibernate.console.ConfigurationFactory.createConfiguration(ConfigurationFactory.java:97) > at org.hibernate.eclipse.console.common.HibernateExtension$5.execute(HibernateExtension.java:166) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.eclipse.console.common.HibernateExtension.execute(HibernateExtension.java:189) > at org.hibernate.eclipse.console.common.HibernateExtension.buildWith(HibernateExtension.java:163) > at org.hibernate.eclipse.console.common.HibernateExtension.build(HibernateExtension.java:134) > at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:189) > at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:43) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:98) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:233) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.dom4j.DocumentException: Server returned HTTP response code: 503 for URL: http://hibernate.org/dtd/hibernate-configuration-3.0.dtd Nested exception: Server returned HTTP response code: 503 for URL: http://hibernate.org/dtd/hibernate-configuration-3.0.dtd > at org.dom4j.io.SAXReader.read(SAXReader.java:484) > at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1576) > ... 17 more > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19174) Create and use Mars M5 target-platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19174?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-19174 at 2/5/15 2:27 AM: ---------------------------------------------------------------- [~fbricon] Does one of these feature need an update while moving to Mars M5? {code:xml} <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSource="true"> <repository location="http://download.jboss.org/jbosstools/updates/m2e-extensions/m2e-apt/1.1.1..."/> <unit id="org.jboss.tools.maven.apt.feature.feature.group" version="1.1.1.201411262015"/> </location> <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSource="true"> <repository location="http://download.jboss.org/jbosstools/updates/m2e-extensions/m2e-buildhelper/"/> <unit id="org.sonatype.m2e.buildhelper.feature.feature.group" version="0.15.0.201212120353"/> </location> <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSource="true"> <repository location="http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-egit/..."/> <unit id="org.sonatype.m2e.egit.feature.feature.group" version="0.14.0.201406241643"/> </location> <location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit"> <repository location="http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-maven..."/>  <unit id="org.sonatype.m2e.mavenarchiver.feature.feature.group" version="0.16.0.201409161210"/> </location> {code} was (Author: mickael_istria): [~fbricon] Does one of these feature need an update while moving to Mars M5? {code:xml} <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSource="true"> <repository location="http://download.jboss.org/jbosstools/updates/m2e-extensions/m2e-apt/1.1.1..."/> <unit id="org.jboss.tools.maven.apt.feature.feature.group" version="1.1.1.201411262015"/> </location> <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSource="true"> <repository location="http://download.jboss.org/jbosstools/updates/m2e-extensions/m2e-buildhelper/"/> <unit id="org.sonatype.m2e.buildhelper.feature.feature.group" version="0.15.0.201212120353"/> </location> <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSource="true"> <repository location="http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-egit/..."/> <unit id="org.sonatype.m2e.egit.feature.feature.group" version="0.14.0.201406241643"/> </location> <location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit"> <repository location="http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-maven..."/>  <unit id="org.sonatype.m2e.mavenarchiver.feature.feature.group" version="0.16.0.201409161210"/> </location> {code} > Create and use Mars M5 target-platform > -------------------------------------- > > Key: JBIDE-19174 > URL: https://issues.jboss.org/browse/JBIDE-19174 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > > Update current target-platform snapshot to use Mars M5. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19174) Create and use Mars M5 target-platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19174?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19174: ---------------------------------------- [~fbricon] Does one of these feature need an update while moving to Mars M5? {code:xml} <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSource="true"> <repository location="http://download.jboss.org/jbosstools/updates/m2e-extensions/m2e-apt/1.1.1..."/> <unit id="org.jboss.tools.maven.apt.feature.feature.group" version="1.1.1.201411262015"/> </location> <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSource="true"> <repository location="http://download.jboss.org/jbosstools/updates/m2e-extensions/m2e-buildhelper/"/> <unit id="org.sonatype.m2e.buildhelper.feature.feature.group" version="0.15.0.201212120353"/> </location> <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSource="true"> <repository location="http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-egit/..."/> <unit id="org.sonatype.m2e.egit.feature.feature.group" version="0.14.0.201406241643"/> </location> <location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit"> <repository location="http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-maven..."/>  <unit id="org.sonatype.m2e.mavenarchiver.feature.feature.group" version="0.16.0.201409161210"/> </location> {code} > Create and use Mars M5 target-platform > -------------------------------------- > > Key: JBIDE-19174 > URL: https://issues.jboss.org/browse/JBIDE-19174 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > > Update current target-platform snapshot to use Mars M5. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19174) Create and use Mars M5 target-platform

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-19174: -------------------------------------- Summary: Create and use Mars M5 target-platform Key: JBIDE-19174 URL: https://issues.jboss.org/browse/JBIDE-19174 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: target-platform Affects Versions: 4.3.0.Alpha1 Reporter: Mickael Istria Update current target-platform snapshot to use Mars M5. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14120) Can not debug OSGI Bundles deployed in JBoss EAP 6.1 with JBossTools 4.0.1

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14120?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-14120: ------------------------------------- I've also opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=459188 and attached a patch. The issue I'm currently experiencing seems to stem from InternalAntRunner using a HashMap (which allows null values) and passing the key/value in to (eventually) a HashTable, which does not allow null values. To be clear, this isn't the cause of this JIRA at all. This is just blocking me being able to debug it in runtime workbench. > Can not debug OSGI Bundles deployed in JBoss EAP 6.1 with JBossTools 4.0.1 > -------------------------------------------------------------------------- > > Key: JBIDE-14120 > URL: https://issues.jboss.org/browse/JBIDE-14120 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.0.1.Final > Reporter: Thomas Wiesner > Fix For: 4.2.x > > Attachments: eclipse_juno_jboss_tools_4.0.1_osgi_debug, scr.zip, standalone.xml > > > Starting JBoss EAP 6.1 in debug mode with JBoss Tools 4.0.1 in eclipse juno runs into following exception: > [0m[0m16:54:53,618 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "de.ebcot.osgi.web.war" (runtime-name: "de.ebcot.osgi.web.war") > [0m[0m16:54:53,618 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "de.ebcot.osgi.core.jar" (runtime-name: "de.ebcot.osgi.core.jar") > [0m[0m16:54:53,777 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011006: OSGi Framework - 2.1.0.CR12 > [0m[31m16:54:53,789 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."de.ebcot.osgi.core.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."de.ebcot.osgi.core.jar".PARSE: JBAS018733: Failed to process phase PARSE of deployment "de.ebcot.osgi.core.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05] > Caused by: java.lang.NullPointerException > at org.jboss.as.osgi.service.FrameworkActivator.activate(FrameworkActivator.java:76) > at org.jboss.as.osgi.deployment.FrameworkActivateProcessor.deploy(FrameworkActivateProcessor.java:72) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > ... 5 more > https://community.jboss.org/thread/223957?tstart=0 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19169) use Tycho 0.22 to build JBT 4.2.3 / JBDS 8.1.0

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19169?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19169: ---------------------------------------- I like the overall change. My only concern is about the create-full-site. Why not simply define it in parent pom? Also, I'm sending a notification to the mailing-list to make sure there will be no surprise. > use Tycho 0.22 to build JBT 4.2.3 / JBDS 8.1.0 > ---------------------------------------------- > > Key: JBIDE-19169 > URL: https://issues.jboss.org/browse/JBIDE-19169 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.2.1.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.2.3.Beta1 > > > Tycho 0.22 is out; we should use it to build JBT 4.3/JBDS 9, and see what new fun goodies we can take advantage of, too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 February 2015