[JBoss JIRA] (JBIDE-16597) Server Adapter Editor: Open launch configuration cause error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16597?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16597:
-------------------------------------
Summary: Server Adapter Editor: Open launch configuration cause error (was: Server Adapter: Open launch configuration cause error)
> Server Adapter Editor: Open launch configuration cause error
> ------------------------------------------------------------
>
> Key: JBIDE-16597
> URL: https://issues.jboss.org/browse/JBIDE-16597
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: server_adapter_editor
> Fix For: 4.3.x
>
> Attachments: open_launch_config1.png, open_launch_config2.png, open_launch_config3.png
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> In OpenShift server adapter settings is Open launch configuration link. Throws error after click on it. See attached images and error log:
> {code:title=.log}
> !ENTRY org.eclipse.ui 4 0 2014-02-17 13:45:08.437
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.handleApplyPressed(LaunchConfigurationTabGroupViewer.java:1401)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$3.widgetSelected(LaunchConfigurationTabGroupViewer.java:308)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1154)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.open(LaunchConfigurationPropertiesDialog.java:213)
> at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:661)
> at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:638)
> at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart$9.linkActivated(OverviewEditorPart.java:594)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> 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:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18036) Decouple FTL target language syntax coloring
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18036?page=com.atlassian.jira.plugi... ]
Jiri Peterka commented on JBIDE-18036:
--------------------------------------
[~dgolovin], please check the attached screenshot and see the "mess" around <!-- comment -->
> Decouple FTL target language syntax coloring
> --------------------------------------------
>
> Key: JBIDE-18036
> URL: https://issues.jboss.org/browse/JBIDE-18036
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: freemarker
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 4.2.0.CR2
>
> Attachments: coloring-issues.png
>
>
> This issue covers the requirement formulated in point (1) of my earlier comment in [JBIDE-11287|https://issues.jboss.org/browse/JBIDE-11287?focusedCommentId=...].
> The present Freemarker plugin has a hard-coded XML/HTML syntax coloring. Although XML/HTML may well be the most common target language of an FTL template, it is clearly not the only possible target language. One can target virtually any language or even plaintext, where {{<}} and {{<!--}} may have completely different meanings or no meanigs at all. Hardcoding XML highlighting for every file opened by the FTL editor is thus simply incorrect.
> Let's define the present task as follows:
> (1) Decouple the syntax coloring of the target language of a FTL template by introducing an interface (call it {{TargetLanguageSupport}}) that will provide the general functionality needed for coloring of target languages.
> (2) At least two implementations of {{TargetLanguageSupport}} should be added:
> (2.1) XML/HTML and
> (2.2) plain text.
> (3) Some kind of target-language detection should be added, e.g. based on file extensions, making XML/HTML syntax coloring active for files ending with {{\*.xml.ftl}}, {{\*.xhtml.ftl}}, {{\*.html.ftl}} and {{\*.htm.ftl}}.
> (3.1) There should be a workspace-wide preference that will say for which file extensions will e.g. XML/HTML syntax coloring be active.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3034) add tern.java to JBDS target platform so that it can be resolved when building JBDS update site, including jst.jsdt
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3034?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3034:
--------------------------------------
Suggested newer PR for that: https://github.com/jbosstools/jbosstools-target-platforms/pull/89
p2diff incoming.
> add tern.java to JBDS target platform so that it can be resolved when building JBDS update site, including jst.jsdt
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3034
> URL: https://issues.jboss.org/browse/JBDS-3034
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: target-platform
> Affects Versions: 8.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Labels: respin-a
> Fix For: 8.0.0.CR1
>
>
> When we added tern to the JBT target platform, we forgot to add it to the JBDS one... because initially, it was just there to build JST, but wasn't needed at install time.
> Now, it's required to build the JBDS update site, which includes jst.jsdt, because jst.jsdt requires it. Without it, I get this:
> {code}
> [ERROR] Software being installed: com.jboss.devstudio.core.site raw:8.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):8.0.0-SNAPSHOT
> [ERROR] Missing requirement: org.jboss.tools.jst.jsdt 3.6.0.Beta2-v20140523-2229 requires 'bundle tern.core 0.2.0' but it could not be found
> [ERROR] Missing requirement: org.jboss.tools.jst.jsdt 3.6.0.Beta3-v20140523-1909-B631 requires 'bundle tern.core 0.2.0' but it could not be found
> [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.site raw:8.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):8.0.0-SNAPSHOT depends on: org.jboss.tools.aerogear.hybrid.feature.feature.group 0.0.0
> [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.hybrid.core 1.1.0.Beta2-v20140523-1436-B253 depends on: bundle org.jboss.tools.jst.jsdt 0.0.0
> [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.hybrid.feature.feature.group 1.1.0.Beta2-v20140523-1436-B253 depends on: org.jboss.tools.aerogear.hybrid.core [1.1.0.Beta2-v20140523-1436-B253]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3034) add tern.java to JBDS target platform so that it can be resolved when building JBDS update site, including jst.jsdt
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3034?page=com.atlassian.jira.plugin.... ]
Mickael Istria updated JBDS-3034:
---------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/89 (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/69)
> add tern.java to JBDS target platform so that it can be resolved when building JBDS update site, including jst.jsdt
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3034
> URL: https://issues.jboss.org/browse/JBDS-3034
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: target-platform
> Affects Versions: 8.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Labels: respin-a
> Fix For: 8.0.0.CR1
>
>
> When we added tern to the JBT target platform, we forgot to add it to the JBDS one... because initially, it was just there to build JST, but wasn't needed at install time.
> Now, it's required to build the JBDS update site, which includes jst.jsdt, because jst.jsdt requires it. Without it, I get this:
> {code}
> [ERROR] Software being installed: com.jboss.devstudio.core.site raw:8.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):8.0.0-SNAPSHOT
> [ERROR] Missing requirement: org.jboss.tools.jst.jsdt 3.6.0.Beta2-v20140523-2229 requires 'bundle tern.core 0.2.0' but it could not be found
> [ERROR] Missing requirement: org.jboss.tools.jst.jsdt 3.6.0.Beta3-v20140523-1909-B631 requires 'bundle tern.core 0.2.0' but it could not be found
> [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.site raw:8.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):8.0.0-SNAPSHOT depends on: org.jboss.tools.aerogear.hybrid.feature.feature.group 0.0.0
> [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.hybrid.core 1.1.0.Beta2-v20140523-1436-B253 depends on: bundle org.jboss.tools.jst.jsdt 0.0.0
> [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.hybrid.feature.feature.group 1.1.0.Beta2-v20140523-1436-B253 depends on: org.jboss.tools.aerogear.hybrid.core [1.1.0.Beta2-v20140523-1436-B253]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class
by fede pia (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ]
fede pia commented on JBIDE-18128:
----------------------------------
[~rob.stryker] Sorry Bob, I don't know what happened with the project content. I've attached it again it contains .java files. Please, let me know any trouble.
> Jboss Eclipse Luna plugin doesn't deploy all .class
> ---------------------------------------------------
>
> Key: JBIDE-18128
> URL: https://issues.jboss.org/browse/JBIDE-18128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: fede pia
> Assignee: Rob Stryker
> Priority: Blocker
> Attachments: jboss-test.zip, TestJboss-2014-09-03.zip
>
>
> The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException.
> I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random.
> For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean
> As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1.
> I also tried building the war outside Eclipse and deployed manually to JBoss and everything works fine.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17741) Embed wizard: Cartridge descriptions are not styled text (ex. light grey like in openshift explorer)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17741?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17741:
-------------------------------------
Estimated Difficulty: Low
> Embed wizard: Cartridge descriptions are not styled text (ex. light grey like in openshift explorer)
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17741
> URL: https://issues.jboss.org/browse/JBIDE-17741
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: embed_wizard
> Fix For: 4.3.x
>
> Attachments: cartridges_decorator.png
>
>
> Description label of the embeddable cartridges are not styled (decorated). This text should be styled (decorated) as on other places for tree items (e.g. cartridges). E.g. in following table could be for Cron cartridge label like "Cron 1.4" as non-styled text (classic font, black color) and "(cron-1.4)" could be brown/grey/... as styled text, bcs. it´s description/inner representation of cartridge.
> !cartridges_decorator.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17741) Embed wizard: Cartridge descriptions are not styled text (ex. light grey like in openshift explorer)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17741?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17741:
-------------------------------------
Labels: embed_wizard (was: )
> Embed wizard: Cartridge descriptions are not styled text (ex. light grey like in openshift explorer)
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17741
> URL: https://issues.jboss.org/browse/JBIDE-17741
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: embed_wizard
> Fix For: 4.3.x
>
> Attachments: cartridges_decorator.png
>
>
> Description label of the embeddable cartridges are not styled (decorated). This text should be styled (decorated) as on other places for tree items (e.g. cartridges). E.g. in following table could be for Cron cartridge label like "Cron 1.4" as non-styled text (classic font, black color) and "(cron-1.4)" could be brown/grey/... as styled text, bcs. it´s description/inner representation of cartridge.
> !cartridges_decorator.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months