April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-3345: ----------------------------------- > So if java -version shows JDK 7 then the server starts correctly JDK 8 then you will encounter problem which I reported I am not able to replicate this at all. my Path: [rob@localhost eclipse]$ echo $PATH /usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/rob/.rvm/bin:/home/rob/.local/bin:/home/rob/bin:/home/rob/.rvm/bin:/home/rob/.local/bin:/home/rob/bin My default java: [rob@localhost eclipse]$ java -version java version "1.8.0_31" Java(TM) SE Runtime Environment (build 1.8.0_31-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode) Eclipse is running with Java 8. I have configured my fsw6.0 runtime to use a java 7. It starts without error. My launch command: rob 7834 31.9 6.1 1725904 995624 pts/0 Sl+ 12:24 1:18 /home/rob/apps/java/jdk1.7.0_67/bin/java -Dprogram.name=JBossTools: JBoss Fuse Service Works 6.0 -server -Xms1024m -Xmx1024m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/rob/apps/jboss/fuse/fsw/installed/jboss-eap-6.1/standalone/log/boot.log -Dlogging.configuration=file:/home/rob/apps/jboss/fuse/fsw/installed/jboss-eap-6.1/standalone/configuration/logging.properties -Djboss.home.dir=/home/rob/apps/jboss/fuse/fsw/installed/jboss-eap-6.1 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=UTF-8 -classpath /home/rob/apps/jboss/fuse/fsw/installed/jboss-eap-6.1/jboss-modules.jar org.jboss.modules.Main -mp /home/rob/apps/jboss/fuse/fsw/installed/jboss-eap-6.1/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=/home/rob/apps/jboss/fuse/fsw/installed/jboss-eap-6.1/standalone I am not experiencing any error at all. > Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8 > ----------------------------------------------------------------- > > Key: JBDS-3345 > URL: https://issues.jboss.org/browse/JBDS-3345 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: server > Affects Versions: 8.0.2.GA > Environment: Fedora 21 x86_64 > JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71 > Reporter: Andrej Podhradsky > Priority: Critical > Attachments: compiler.png, console.png, errors.txt, error_log.txt, installed_jre.png, runtime_jre.png, server.log > > > FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file. > Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually. > Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19733) Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19733?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-19733: -------------------------------------- Assignee: Mickael Istria (was: Ilya Buziuk) > Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19733 > URL: https://issues.jboss.org/browse/JBIDE-19733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Len DiMaggio > Assignee: Mickael Istria > Attachments: Problems_before_import_completes.png > > > The sequence of user actions and import processing is such that, if an error occurs (for example - as described in JBIDE-19719), the error is reported after the import has been performed. Pressing cancel does not cancel/rollback the import. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19744) jbosstools-build has both 4.2.x and 4.2.X and with different content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19744?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19744: ------------------------------------ Given that the snapshot and the release version are bitwise identical in all ways except the name, and that 4.2.x is at EOD (unless we decide to do a 4.2.4 / 8.1.1), here's what I would do: a) fix parent pom in 4.2.x branch (lower case) to remove the -SNAPSHOT suffix on the target platform version. b) delete the 4.2.X (upper case) branch So say we all? Note: the only problem w/ the parent pom in 4.2.x (lower case) branch retaining the -SNAPSHOT suffix is that at some point the snapshot will be deleted from Nexus and so anyone using the 4.2.3.Final-SNAPSHOT parent pom will be unable to resolve the .target file. So because IS 8.x development is ongoing (and they should be using that parent pom, right [~pleacu] ?) therefore this needs to be fixed ASAP. > jbosstools-build has both 4.2.x and 4.2.X and with different content > -------------------------------------------------------------------- > > Key: JBIDE-19744 > URL: https://issues.jboss.org/browse/JBIDE-19744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Final > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.2.3.Final > > > Both https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.X and https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.x exist. > The difference is shown here: https://github.com/jbosstools/jbosstools-build/compare/jbosstools-4.2.x..... > indicating that 4.2.x builds are *not* using the released version of TP to build against - only snapshot (which should not be there if TP was released) > We should get the 4.2.X deleted, but before we do - what do we do about the missing commit on 4.2.x ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19732) Misleading error logged when a new hybrid mobile engine configured

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19732?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19732: ------------------------------------ Assignee: Gorkem Ercan > Misleading error logged when a new hybrid mobile engine configured > ------------------------------------------------------------------ > > Key: JBIDE-19732 > URL: https://issues.jboss.org/browse/JBIDE-19732 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Priority: Minor > > There's no functional impact, but the error message is confusing. > When a new mobile hybrid engine is configured, this error is logged: > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 14:38:54.071 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/3.7.1/framework/cordova-3.7.1.jar > The file, however, is right where it belongs: > ll /home/ldimaggi/.cordova/lib/android/cordova/3.7.1/framework/cordova-3.7.1.jar > -rw-rw-r--. 1 ldimaggi ldimaggi 357355 Apr 28 14:38 /home/ldimaggi/.cordova/lib/android/cordova/3.7.1/framework/cordova-3.7.1.jar -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19731) Selecting "remove" before a hybrid mobile engine is created logs exception - no feeback is provided to users in the UI

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19731?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19731: ------------------------------------ Assignee: Gorkem Ercan > Selecting "remove" before a hybrid mobile engine is created logs exception - no feeback is provided to users in the UI > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19731 > URL: https://issues.jboss.org/browse/JBIDE-19731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Priority: Minor > > To recreate: > * With no hybrid mobile engines defined > * Preferences->Hybrid Mobile-> Engines > * Click on "remove" and the exception is logged - no feedback is provided to the user in the UI > !ENTRY org.eclipse.ui 4 0 2015-04-28 14:30:25.700 > !MESSAGE Unhandled event loop exception > !STACK 0 > java.lang.ClassCastException: org.eclipse.thym.core.extensions.PlatformSupport cannot be cast to org.eclipse.thym.core.engine.HybridMobileEngine > at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection.handleRemoveEngine(AvailableCordovaEnginesSection.java:606) > at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection.access$4(AvailableCordovaEnginesSection.java:598) > at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection$5.handleEvent(AvailableCordovaEnginesSection.java:378) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) > at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19733) Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19733?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19733: ------------------------------------ Assignee: Ilya Buziuk > Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19733 > URL: https://issues.jboss.org/browse/JBIDE-19733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Len DiMaggio > Assignee: Ilya Buziuk > Attachments: Problems_before_import_completes.png > > > The sequence of user actions and import processing is such that, if an error occurs (for example - as described in JBIDE-19719), the error is reported after the import has been performed. Pressing cancel does not cancel/rollback the import. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19735) Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)"

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19735?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19735: ------------------------------------ Assignee: Fred Bricon > Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19735 > URL: https://issues.jboss.org/browse/JBIDE-19735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Attachments: jbosstools-diagnostics-20150428160436.zip > > > To recreate: > * Create from scratch a new AngularJS with Forge project. > * Have the project creation install AngularJS Eclipse > Observe this error reported in a dialog in the UI: > An error has occurred. See error log for more details. > invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" > The full .log is in the attached diagnostic file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19744) jbosstools-build has both 4.2.x and 4.2.X and with different content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19744?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19744: ------------------------------- Fix Version/s: 4.2.3.Final > jbosstools-build has both 4.2.x and 4.2.X and with different content > -------------------------------------------------------------------- > > Key: JBIDE-19744 > URL: https://issues.jboss.org/browse/JBIDE-19744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Final > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.2.3.Final > > > Both https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.X and https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.x exist. > The difference is shown here: https://github.com/jbosstools/jbosstools-build/compare/jbosstools-4.2.x..... > indicating that 4.2.x builds are *not* using the released version of TP to build against - only snapshot (which should not be there if TP was released) > We should get the 4.2.X deleted, but before we do - what do we do about the missing commit on 4.2.x ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19744) jbosstools-build has both 4.2.x and 4.2.X and with different content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19744?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19744: ---------------------------------- Assignee: Nick Boldt > jbosstools-build has both 4.2.x and 4.2.X and with different content > -------------------------------------------------------------------- > > Key: JBIDE-19744 > URL: https://issues.jboss.org/browse/JBIDE-19744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Final > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.2.3.Final > > > Both https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.X and https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.x exist. > The difference is shown here: https://github.com/jbosstools/jbosstools-build/compare/jbosstools-4.2.x..... > indicating that 4.2.x builds are *not* using the released version of TP to build against - only snapshot (which should not be there if TP was released) > We should get the 4.2.X deleted, but before we do - what do we do about the missing commit on 4.2.x ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19741) jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19741?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19741 at 4/30/15 11:20 AM: -------------------------------------------------------------- Reason I suggest we de-dupe here is that the jbosstools-src.zip [1] is over 300M in size, and 141M of that is from javaee's included jars. (I could also just filter out the jars, but then the tests' sources won't match what's actually in github.) [1] http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... I'm less concerned with cluttered history / large .git folder footprint than with making our published artifacts as small & efficient as possibru. was (Author: nickboldt): Reason I suggest we de-dupe here is that the jbosstools-src.zip is over 300M in size, and 141M of that is from javaee's included jars. (I could also just filter out the jars, but then the tests' sources won't match what's actually in github.) I'm less concerned with cluttered history / large .git folder footprint than with making our published artifacts as small & efficient as possibru. > jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this? > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19741 > URL: https://issues.jboss.org/browse/JBIDE-19741 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi, jsp/jsf/xml/html source editing, seam2 > Reporter: Nick Boldt > Attachments: jars.in.javaee.list.of.dupes.with.counts.txt, jars.in.javaee.txt > > > There are 141M of binaries in the jbosstools-javaee source tree. > See attached files for details. Would it be possible to pull these jars from Maven instead of having as many as *19* copies of the same jar in the source repo? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

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 April 2015