August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-310) Fuse: Extend server tests

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-310?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-310: ------------------------------- Priority: Minor (was: Major) > Fuse: Extend server tests > ------------------------- > > Key: JBTIS-310 > URL: https://issues.jboss.org/browse/JBTIS-310 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Minor > Original Estimate: 4 days > Remaining Estimate: 4 days > > Extend all server tests to cover every available server's type (not only the latest JBoss Fuse Server). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-300) JBDS-IS 8.0.0.Alpha1 contains old version of bpmn2 modeler

by Marek Baluch (JIRA)

[ https://issues.jboss.org/browse/JBTIS-300?page=com.atlassian.jira.plugin.... ] Marek Baluch commented on JBTIS-300: ------------------------------------ The BPMN2 editor has not received an update for a long time. Please pick up a newer version as soon as possible. Thank you. > JBDS-IS 8.0.0.Alpha1 contains old version of bpmn2 modeler > ---------------------------------------------------------- > > Key: JBTIS-300 > URL: https://issues.jboss.org/browse/JBTIS-300 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 8.0.0.Alpha1 > Environment: JBDS 8.0.0.Beta3 > Reporter: Jozef Marko > Priority: Critical > > Current version of bpmn2 modeler is 1.0.2. Desired version is 1.1.0 [1] which works well with eclipse luna. > [1] http://download.eclipse.org/bpmn2-modeler/updates/luna/1.1.0/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-310) Fuse: Extend server tests

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-310: ---------------------------------- Summary: Fuse: Extend server tests Key: JBTIS-310 URL: https://issues.jboss.org/browse/JBTIS-310 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Components: QE Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík Extend all server tests to cover every available server's type (not only the latest JBoss Fuse Server). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-300) JBDS-IS 8.0.0.Alpha1 contains old version of bpmn2 modeler

by Marek Baluch (JIRA)

[ https://issues.jboss.org/browse/JBTIS-300?page=com.atlassian.jira.plugin.... ] Marek Baluch updated JBTIS-300: ------------------------------- Priority: Critical (was: Major) > JBDS-IS 8.0.0.Alpha1 contains old version of bpmn2 modeler > ---------------------------------------------------------- > > Key: JBTIS-300 > URL: https://issues.jboss.org/browse/JBTIS-300 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 8.0.0.Alpha1 > Environment: JBDS 8.0.0.Beta3 > Reporter: Jozef Marko > Priority: Critical > > Current version of bpmn2 modeler is 1.0.2. Desired version is 1.1.0 [1] which works well with eclipse luna. > [1] http://download.eclipse.org/bpmn2-modeler/updates/luna/1.1.0/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-309) Fuse: test new version (8.0.0.Alpha1) of the tooling

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-309?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík resolved JBTIS-309. -------------------------------- Resolution: Done > Fuse: test new version (8.0.0.Alpha1) of the tooling > ---------------------------------------------------- > > Key: JBTIS-309 > URL: https://issues.jboss.org/browse/JBTIS-309 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Original Estimate: 1 week > Time Spent: 1 week > Remaining Estimate: 0 minutes > > TCMS: https://tcms.engineering.redhat.com/run/168077 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-309) Fuse: test new version (8.0.0.Alpha1) of the tooling

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-309: ---------------------------------- Summary: Fuse: test new version (8.0.0.Alpha1) of the tooling Key: JBTIS-309 URL: https://issues.jboss.org/browse/JBTIS-309 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Components: QE Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík TCMS: https://tcms.engineering.redhat.com/run/168077 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2847) Java EE 7 Tech Preview

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2847?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2847: ------------------------------------------- here is my current attempt on removing/reducing the groovy impact: https://github.com/maxandersen/javaee7-samples/tree/reduce_groovy_impact this one should import without requiring groovy - need to move the groovy stuff lower down. > Java EE 7 Tech Preview > ---------------------- > > Key: JBDS-2847 > URL: https://issues.jboss.org/browse/JBDS-2847 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Burr Sutter > Assignee: Xavier Coulon > Labels: JBDS80_Approved_Scope > Fix For: 8.0.0.CR1 > > > Successfully/cleanly import the Java EE 7 Samples that have been migrated/ported to Wildfly > https://github.com/javaee-samples/javaee7-samples > They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17264) Forge Console crashes when auto-completing values

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17264?page=com.atlassian.jira.plugi... ] Vineet Reynolds commented on JBIDE-17264: ----------------------------------------- I'm not sure if I've tracked this down completely, but the stack trace is quite clear on whether the above reported exception by George is thrown: {code} public abstract class AbstractCommand implements Command { public abstract CommandType getType(); public void handle(Document document) { AeshCorePlugin.log(new Throwable("Unimplemented command: " + getType())); } } {code} The {{org.jboss.tools.aesh.core.internal.ansi.CursorUp}} and other similar commands including the reported {{org.jboss.tools.aesh.core.internal.ansi.DeviceStatusReport}} all implement the same {{handle(Document)}} method through the super type {{AbstractCommand}}, which is to log the created {{Throwable}}. Other ANSI escape sequences like Cursor Back or Cursor Horizontal Absolute have valid implementations. However, I don't see this as the root cause. The console is capable of accepting input from the user after this. My current suspicion is that the underlying JFace document location is not in sync with the console location. And hence I sometimes see the following exception being logged (after I hit the enter key in the hung state): {code} !ENTRY org.jboss.tools.forge.aesh.ui 4 1 2014-08-26 12:48:38.189 !MESSAGE Error logged from Aesh UI Plugin: !STACK 0 org.eclipse.jface.text.BadLocationException at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1179) at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210) at org.jboss.tools.aesh.ui.internal.document.DocumentImpl$3.run(DocumentImpl.java:103) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) 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:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) 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.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) {code} Note that the command if valid is executed by Forge. > Forge Console crashes when auto-completing values > ------------------------------------------------- > > Key: JBIDE-17264 > URL: https://issues.jboss.org/browse/JBIDE-17264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: George Gastaldi > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.0.CR1 > > Attachments: jstack.txt > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support

by Mikhail Kalkov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Mikhail Kalkov commented on JBIDE-2720: --------------------------------------- [~maxandersen], I'm not clear about the difference between "visual page editor" and "html preview". I've been using the Visual/Source tab JBoss Tools HTML Editor (org.jboss.tools.jst.jsp.jspeditor.HTMLTextEditor). Additionally, I sometimes have BrowserSim opened with LiveReload on to see changes more like they are going to appear for an end user. If you meant the Preview tab of the same editor, I guess it should be OK as long as it can be detached from the source code editor so I can see both at the same time. > Need 64-bit windows support > --------------------------- > > Key: JBIDE-2720 > URL: https://issues.jboss.org/browse/JBIDE-2720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha > Reporter: Samuel Mendenhall > Assignee: Konstantin Marmalyukov > Fix For: 4.2.x > > Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png > > > If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for Windows 64-bit. > *Update:* > In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr... > {color:red}*Known problems:*{color} > * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK > *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:* > * Try to uninstall Intel OpenCL SDK > * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio) > If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2635: -------------------------------- Fix Version/s: 9.0.0.Alpha1 (was: 8.0.0.CR1) > Installation sometimes fail with bundle was not found on Windows > ---------------------------------------------------------------- > > Key: JBDS-2635 > URL: https://issues.jboss.org/browse/JBDS-2635 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.Beta1 > Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07 > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 9.0.0.Alpha1 > > Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log > > > For the first time JBDS 7.0.0.Beta1 failed on windows8: > {code} > An error occurred while installing the items > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction). > The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found. > Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log > {code} -- 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 August 2014