[JBoss JIRA] (JBIDE-18244) org.eclipse.core.runtime.AssertionFailedException when editing ftl file
by Daniel Dekany (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18244?page=com.atlassian.jira.plugi... ]
Daniel Dekany commented on JBIDE-18244:
---------------------------------------
Where does the FreeMarker code replace exceptions with null-s and such? Or what do you mean by "freemarker code"?
> org.eclipse.core.runtime.AssertionFailedException when editing ftl file
> -----------------------------------------------------------------------
>
> Key: JBIDE-18244
> URL: https://issues.jboss.org/browse/JBIDE-18244
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.0.CR1
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Fix For: 4.3.0.Beta1
>
> Attachments: assertion-exception.ogv
>
>
> When editing ftl file I received assertion failed exception. See the screencast. What I did was to adding new line and then remove it by back key. Before it I was using code completion (might be related)
> {code}
> org.eclipse.core.runtime.AssertionFailedException: assertion failed:
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
> at org.eclipse.jface.text.Position.setLength(Position.java:185)
> at org.eclipse.jface.text.rules.FastPartitioner.computePartitioning(FastPartitioner.java:634)
> at org.eclipse.jface.text.AbstractDocument.computePartitioning(AbstractDocument.java:1430)
> at org.eclipse.jface.text.TextUtilities.computePartitioning(TextUtilities.java:431)
> at org.eclipse.jface.text.presentation.PresentationReconciler.createPresentation(PresentationReconciler.java:451)
> at org.eclipse.jface.text.presentation.PresentationReconciler.processDamage(PresentationReconciler.java:569)
> at org.eclipse.jface.text.presentation.PresentationReconciler.access$3(PresentationReconciler.java:567)
> at org.eclipse.jface.text.presentation.PresentationReconciler$InternalListener.textChanged(PresentationReconciler.java:227)
> at org.eclipse.jface.text.TextViewer.updateTextListeners(TextViewer.java:2830)
> at org.eclipse.jface.text.TextViewer$VisibleDocumentListener.documentChanged(TextViewer.java:403)
> at org.eclipse.jface.text.AbstractDocument.doFireDocumentChanged2(AbstractDocument.java:769)
> at org.eclipse.jface.text.AbstractDocument.doFireDocumentChanged(AbstractDocument.java:736)
> at org.eclipse.jface.text.AbstractDocument.doFireDocumentChanged(AbstractDocument.java:721)
> at org.eclipse.jface.text.AbstractDocument.fireDocumentChanged(AbstractDocument.java:796)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1191)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
> at org.eclipse.jface.text.DefaultDocumentAdapter.replaceTextRange(DefaultDocumentAdapter.java:248)
> at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7268)
> at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:8111)
> at org.eclipse.swt.custom.StyledText.doBackspace(StyledText.java:2285)
> at org.eclipse.swt.custom.StyledText.invokeAction(StyledText.java:7058)
> at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:5959)
> at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:5986)
> at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5663)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1424)
> at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:824)
> at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3269)
> at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:777)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2098)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5510)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4700)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9074)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2473)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3439)
> 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}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19579) Context vs Contexts
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19579?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-19579:
--------------------------------------
Assignee: Alexey Kazakov (was: Viacheslav Kabanovich)
> Context vs Contexts
> --------------------
>
> Key: JBIDE-19579
> URL: https://issues.jboss.org/browse/JBIDE-19579
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Alexey Kazakov
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> Just a small inconsistency - sometimes in JBT there's Context and Dependency Injection or Context*s* and Dependency Injection.
> Most references use Context not Context*s*. The correct one is the second one.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-19697:
---------------------------------------
The following is the code (https://github.com/jbosstools/jbosstools-base/blob/jbosstools-4.3.0.Alpha...):
{code}
...
private static final String LOCATIONS_FILE_NAME = "runtime_locations.properties"; //$NON-NLS-1$
private static final String LOCATIONS_FILE = "../../../../studio/" + LOCATIONS_FILE_NAME; //$NON-NLS-1$
private static final String LOCATIONS_FILE_CONFIGURATION = "../../studio/" + LOCATIONS_FILE_NAME; //$NON-NLS-1$
...
private static File findRuntimeFile() {
try {
String pluginLocation = FileLocator.resolve(RuntimeUIActivator.getDefault().getBundle().getEntry("/")).getPath(); //$NON-NLS-1$
File serversFile = new File(pluginLocation, LOCATIONS_FILE);
if (!serversFile.isFile()) {
String configuration = getConfiguration();
serversFile = new File(configuration, LOCATIONS_FILE_CONFIGURATION).getCanonicalFile();
} else {
serversFile = serversFile.getCanonicalFile();
}
if (!serversFile.isFile()) {
serversFile = new File(pluginLocation,LOCATIONS_FILE_NAME);
}
if (serversFile.isFile()) {
return serversFile;
}
} catch(IOException ioe) {
RuntimeUIActivator.pluginLog().logError(ioe);
}
return null;
}
{code}
I suppose you have
pluginLocation=/Users/rasp/jbossqa/JBDS/9.0.0/Eclipse-runtime-test.app/Contents/Eclipse/plugins/org.jboss.tools.runtime.ui_<VERSION>
configuration=/Users/rasp/jbossqa/JBDS/9.0.0/Eclipse-runtime-test.app/Eclipse-runtime-test.app/Contents/Eclipse/
> org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19697
> URL: https://issues.jboss.org/browse/JBIDE-19697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Snjezana Peco
>
> When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
> Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
> {code}
> This is inside the file:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
> eclipse.preferences.version=1
> runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
> {code}
> It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
> I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
> Can somebody explain what's going on?
> Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19579) Context vs Contexts
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19579?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19579:
-----------------------------------
Sprint: Sprint #2 April 2015
> Context vs Contexts
> --------------------
>
> Key: JBIDE-19579
> URL: https://issues.jboss.org/browse/JBIDE-19579
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> Just a small inconsistency - sometimes in JBT there's Context and Dependency Injection or Context*s* and Dependency Injection.
> Most references use Context not Context*s*. The correct one is the second one.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19571) Add FSW to downloadable runtimes
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19571?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19571:
-------------------------------------
False alarm. Apparently I had an incomplete installation because it couldn't find 'keytool' so while it had all the proper jars and could start fine from commandline, it was missing its various config files.
This seems very very strange to me, but, once I fixed the keytool issue I get a proper installation.
> Add FSW to downloadable runtimes
> --------------------------------
>
> Key: JBIDE-19571
> URL: https://issues.jboss.org/browse/JBIDE-19571
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> FSW 6.0 is not available in download runtimes
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-18752) Freemarker plugin does not work for square bracket (since JBT 4.2.0.Final)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18752?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-18752:
----------------------------------
Story Points: 1 (was: 2)
> Freemarker plugin does not work for square bracket (since JBT 4.2.0.Final)
> --------------------------------------------------------------------------
>
> Key: JBIDE-18752
> URL: https://issues.jboss.org/browse/JBIDE-18752
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Affects Versions: 4.2.0.Final
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.Beta1
>
>
> From https://github.com/jbosstools/jbosstools-freemarker/issues/26
> {quote}
> When using the plugin to edit freemarker files that use the square bracket syntax the editor fails to highlight the syntax (this is happening in JBoss Tools 4.20 Final).
> I think the file: src / org / jboss / ide / eclipse / freemarker / editor / DocumentProvider.java
> on line 70 is causing the syntax highlighting problem:
> {code}if (ch != LexicalConstants.SQUARE_SYNTAX_MARKER.charAt(i)) {
> return SyntaxMode.ANGLE;
> }
> SQUARE_SYNTAX_MARKER.charAt(i)
> {code}
> It should start in 0 and have a different index than i (the index of the file content) to have a proper string matching. Also, SQUARE_SYNTAX_MARKER is [#ftl, not all files start with a ftl tag, so I don't see the need for "ftl" at the end, so that's why in the following example fix I put j < 2.
> e.g.
> {code}
> int j =0;
> for (; i < docLength && j < 2; i++) {
> char ch = document.getChar(i);
> if (ch != LexicalConstants.SQUARE_SYNTAX_MARKER.charAt(j)) {
> return SyntaxMode.ANGLE;
> }
> j++;
> }
> {code}
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-18902) Add Ceylon IDE to JBoss Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18902?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-18902:
-------------------------------------
I tested it works with JBDS 9.0.0.Alpha2.
Ceylon plugins installed :
{quote}
com.redhat.ceylon.common_1.1.0.v20141013-1414
com.redhat.ceylon.compiler.java_1.1.0.v20141013-1414
com.redhat.ceylon.compiler.js_1.1.0.v20141013-1414
com.redhat.ceylon.dist.repo_1.1.0.v20141013-1416
com.redhat.ceylon.dist_1.1.0.v20141013-1416
com.redhat.ceylon.eclipse.android.plugin_1.1.0.v20141013-1438-Final.jar
com.redhat.ceylon.eclipse.ui_1.1.0.v20141013-1438-Final
com.redhat.ceylon.maven-support_2.0.0
com.redhat.ceylon.module-resolver_1.1.0.v20141013-1414
com.redhat.ceylon.test.eclipse.plugin_1.1.0.v20141013-1438-Final.jar
com.redhat.ceylon.typechecker_1.1.0.v20141013-1414
{quote}
Features
{quote}
com.redhat.ceylon.dist.feature_1.1.0.v20141013-1416
com.redhat.ceylon.eclipse.android.feature_1.1.0.v20141013-1438-Final
com.redhat.ceylon.eclipse.feature_1.1.0.v20141013-1438-Final
{quote}
Haven't tested performance issues though
> Add Ceylon IDE to JBoss Central
> -------------------------------
>
> Key: JBIDE-18902
> URL: https://issues.jboss.org/browse/JBIDE-18902
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Affects Versions: 4.2.0.Final
> Reporter: Fred Bricon
> Assignee: Max Rydahl Andersen
> Fix For: 4.2.x
>
>
> It's probably time to consider adding Ceylon IDE to JBoss Central, provided it doesn't break anything.
> Questions are :
> - Early Access or not?
> - should JBDS get it?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months