April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-621) Rework and Finalize Article about Generating a HTML5 Web App

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-621?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-621: ------------------------------------ I have added my edits directly into the text file (no images received) and sent the file back to Supriya. > Rework and Finalize Article about Generating a HTML5 Web App > ------------------------------------------------------------ > > Key: TOOLSDOC-621 > URL: https://issues.jboss.org/browse/TOOLSDOC-621 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > Attachments: generate_HTML5_web_app.adoc > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18570) Creating EJB 3.x bean is asking EJB 2.x values

by Arun Gupta (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18570?page=com.atlassian.jira.plugi... ] Arun Gupta commented on JBIDE-18570: ------------------------------------ EJB 2.x labeling is fine for now. We can revisit if somebody else reports this. > Creating EJB 3.x bean is asking EJB 2.x values > ---------------------------------------------- > > Key: JBIDE-18570 > URL: https://issues.jboss.org/browse/JBIDE-18570 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: ejb3, upstream > Reporter: Arun Gupta > Assignee: Rob Stryker > Fix For: 4.3.x > > Attachments: Screen Shot 2014-10-09 at 9.41.39 pm.png > > > Creating a singleton EJB using 3.x wizard and its asking for home and component interfaces from 2.x. This is confusing and redundant. > Image coming in attachment next. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-19716. ---------------------------------- Resolution: Rejected resolving. Len please open a new one to TOOLSDOC > JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK > -------------------------------------------------------------------- > > Key: JBIDE-19716 > URL: https://issues.jboss.org/browse/JBIDE-19716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: Android_SDK.png, sdk_change.png > > > With 4.3.0.Alpha2: > * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz > * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android > * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19719: -------------------------------------- I have removed the logging upstream > EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-19719: --------------------------------- Component/s: (was: aerogear-hybrid) > EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19719: -------------------------------------- I do not see the purpose of tracing this one, I guess we can remove the logging if it is a bother. Warning is not needed either because as I have explained these are logged because of a chain of calls and we will ask user to fix the problem when it is a blocker > EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19727) An error of "0" is displayed to the user after a failed Cordova mobile engine install

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19727?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-19727. ---------------------------------- Resolution: Duplicate Issue Duppos are great, gives a false sense of achievement :) > An error of "0" is displayed to the user after a failed Cordova mobile engine install > ------------------------------------------------------------------------------------- > > Key: JBIDE-19727 > URL: https://issues.jboss.org/browse/JBIDE-19727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: error.png, jbosstools-diagnostics-20150428131923.zip > > > When trying to install a 4.0 Cordova mobile engine, this error dialog is displayed: > An error has occurred. See error log for more details. > 0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19726) Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19726?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19726: -------------------------------------- Yeah, we can not support 4.0.0 because cordova.js file has been relocated on the 4.0.0 distro. We have not run into this case because we had a white list of versions we can support in the past but with npm change that can not happen anymore. In any case, I will check and show a proper dialog for these cases. > Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19726 > URL: https://issues.jboss.org/browse/JBIDE-19726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Fix For: 4.3.0.Beta1 > > Attachments: IMG_2768.MOV > > > Attempts to configure Cordova version 4.0 fail - another case of changes in directory tree - the errors are written to the .log, and are not communicated to the user via the UI > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/cordova-4.0.0.jar > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/assets/www/cordova.js > !ENTRY org.eclipse.thym.ios.core 4 0 2015-04-28 11:28:43.882 > !MESSAGE Can not detect version. VERSION file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19726) Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19726?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-19726: --------------------------------- Fix Version/s: 4.3.0.Beta1 > Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19726 > URL: https://issues.jboss.org/browse/JBIDE-19726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Fix For: 4.3.0.Beta1 > > Attachments: IMG_2768.MOV > > > Attempts to configure Cordova version 4.0 fail - another case of changes in directory tree - the errors are written to the .log, and are not communicated to the user via the UI > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/cordova-4.0.0.jar > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/assets/www/cordova.js > !ENTRY org.eclipse.thym.ios.core 4 0 2015-04-28 11:28:43.882 > !MESSAGE Can not detect version. VERSION file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19737) Add template info page after template list in create from app flow

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19737?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-19737: ------------------------------------- Assignee: Jeff Cantrill > Add template info page after template list in create from app flow > ------------------------------------------------------------------ > > Key: JBIDE-19737 > URL: https://issues.jboss.org/browse/JBIDE-19737 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > > Add a template info page that identifies key aspects of a template that a user has choosen so they can ensure they want to continue -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[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, 12 months

1
0
0 / 0

[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, 12 months

1
0
0 / 0

[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, 12 months

1
0
0 / 0

[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, 12 months

1
0
0 / 0

[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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19740) Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19740?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-19740. ----------------------------------- Resolution: Done Logging for exceptions released to master. > Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions > ---------------------------------------------------------------------------------- > > Key: JBIDE-19740 > URL: https://issues.jboss.org/browse/JBIDE-19740 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: freemarker > Affects Versions: 4.2.3.Final, 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[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: ------------------------------------- Only thing that bothers me is the Ceylon project being shown as a primary wizard, see https://github.com/ceylon/ceylon-ide-eclipse/issues/1337 > 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.3.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, 12 months

1
0
0 / 0

[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, 12 months

1
0
0 / 0

[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 updated JBIDE-18902: -------------------------------- Fix Version/s: 4.3.x (was: 4.2.x) > 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.3.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, 12 months

1
0
0 / 0

[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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19740) Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19740?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19740: ---------------------------------- Issue Type: Task (was: Bug) > Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions > ---------------------------------------------------------------------------------- > > Key: JBIDE-19740 > URL: https://issues.jboss.org/browse/JBIDE-19740 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: freemarker > Affects Versions: 4.2.3.Final, 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19740) Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19740?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19740: ---------------------------------- Story Points: 1 > Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions > ---------------------------------------------------------------------------------- > > Key: JBIDE-19740 > URL: https://issues.jboss.org/browse/JBIDE-19740 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.3.Final, 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18036) Decouple FTL target language syntax coloring

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18036?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-18036: ------------------------------------- Assignee: Denis Golovin (was: Max Rydahl Andersen) > 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: Denis Golovin > Fix For: 4.3.0.Beta1 > > 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.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18243) Freemarker syntax highlight requires file reopening

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18243?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-18243: ------------------------------------- Assignee: Denis Golovin > Freemarker syntax highlight requires file reopening > --------------------------------------------------- > > Key: JBIDE-18243 > URL: https://issues.jboss.org/browse/JBIDE-18243 > 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 > > > When pasting some code into ftl file, syntax highlight is not activated until file is saved closed and reopened. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18337) After some editing freemarker outline is not visible

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18337?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-18337: ------------------------------------- Assignee: Denis Golovin > After some editing freemarker outline is not visible > ---------------------------------------------------- > > Key: JBIDE-18337 > URL: https://issues.jboss.org/browse/JBIDE-18337 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1, L64 > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > Attachments: freemarker-outline-missing.ogv > > > After editing freemarker outline is not visible (see attached screencast) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18245) Freemarker syntax highlight issues

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18245?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-18245: ------------------------------------- Assignee: Denis Golovin > Freemarker syntax highlight issues > ---------------------------------- > > Key: JBIDE-18245 > URL: https://issues.jboss.org/browse/JBIDE-18245 > 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: syntax-highlight-issue.png > > > Create ftl file and paste: > {code} > <html> > <head> > <title>Welcome!</title> > </head> > <body> > <h1>Welcome ${user}!</h1> > <p>Our latest product: > <a href="${latestProduct.url}">${latestProduct.name}</a> > <#assign x = 1 />. > <#assign y = 1 /> > <#assign z = 1 /> > </body> > </html> > {code} > Syntax highlighting works very strange, see screenshot and make some atttempts, you will see it for your own. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8526) Freemarker content assist doesn't work when inside a tag or tag attribute

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8526?page=com.atlassian.jira.plugin... ] Denis Golovin reassigned JBIDE-8526: ------------------------------------ Assignee: Denis Golovin (was: Peter Palaga) > Freemarker content assist doesn't work when inside a tag or tag attribute > ------------------------------------------------------------------------- > > Key: JBIDE-8526 > URL: https://issues.jboss.org/browse/JBIDE-8526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 3.3.x > Environment: Windows XP, > Reporter: Ehrann Mehdan > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > > In Freemarker 1.1.0.v20110303-1225-H55-Alpha1 > Eclipse platform version: 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi > Build id: M20110210-1200 > This code will not trigger content assist when pressing ctrl+space with a context named data that has property "someValue" > <tag attribute="${data.someValue}">... > This code will (removed opening tag bracket) > tag attribute="${data.someValue}">... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18244) org.eclipse.core.runtime.AssertionFailedException when editing ftl file

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18244?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-18244: --------------------------------------- original exception is below, it is just ignored in released code {code}org.eclipse.jface.text.BadLocationException at org.eclipse.jface.text.AbstractDocument.getChar(AbstractDocument.java:806) at org.jboss.ide.eclipse.freemarker.editor.Editor.keyPressed(Editor.java:342) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167) 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.Widget.sendEvent(Widget.java:1346) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1331) at org.eclipse.swt.widgets.Widget.sendIMKeyEvent(Widget.java:1408) at org.eclipse.swt.widgets.Control.gtk_commit(Control.java:3084) at org.eclipse.swt.widgets.Canvas.gtk_commit(Canvas.java:163) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2001) at org.eclipse.swt.widgets.Control.windowProc(Control.java:5541) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4707) at org.eclipse.swt.internal.gtk.OS._gtk_im_context_filter_keypress(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_im_context_filter_keypress(OS.java:8634) at org.eclipse.swt.widgets.Control.filterKey(Control.java:2409) at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3302) at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:780) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2020) at org.eclipse.swt.widgets.Control.windowProc(Control.java:5541) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4707) 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:9241) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1250) 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:2421) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3423) 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){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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18244) org.eclipse.core.runtime.AssertionFailedException when editing ftl file

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18244?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18244: ---------------------------------- Story Points: 5 > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19740) Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19740?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-19740: ------------------------------------- Assignee: Denis Golovin > Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions > ---------------------------------------------------------------------------------- > > Key: JBIDE-19740 > URL: https://issues.jboss.org/browse/JBIDE-19740 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.3.Final, 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18244) org.eclipse.core.runtime.AssertionFailedException when editing ftl file

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18244?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-18244: --------------------------------------- I suspect AssertionErrors are result of poor exception handling in freemarker code. Basically it ignores exceptions in various ways and replaces them with null or default values everywhere to go further in code. Then it calls eclipse text framework with what it got. Result is AssertionFiledExceptions without a trace of original problem. I'll push fix for this as part of JBIDE-19740. > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19740) Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19740?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19740: ---------------------------------- Fix Version/s: 4.3.0.Beta1 > Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions > ---------------------------------------------------------------------------------- > > Key: JBIDE-19740 > URL: https://issues.jboss.org/browse/JBIDE-19740 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.3.Final, 4.3.0.Alpha2 > Reporter: Denis Golovin > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19740) Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19740?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19740: ---------------------------------- Sprint: Sprint #2 April 2015 > Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions > ---------------------------------------------------------------------------------- > > Key: JBIDE-19740 > URL: https://issues.jboss.org/browse/JBIDE-19740 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.3.Final, 4.3.0.Alpha2 > Reporter: Denis Golovin > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19740) Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19740?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19740: ---------------------------------- Summary: Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions (was: Fix exception handling ) > Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions > ---------------------------------------------------------------------------------- > > Key: JBIDE-19740 > URL: https://issues.jboss.org/browse/JBIDE-19740 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.2.3.Final, 4.3.0.Alpha2 > Reporter: Denis Golovin > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19740) Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19740?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19740: ---------------------------------- Component/s: freemarker > Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions > ---------------------------------------------------------------------------------- > > Key: JBIDE-19740 > URL: https://issues.jboss.org/browse/JBIDE-19740 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.3.Final, 4.3.0.Alpha2 > Reporter: Denis Golovin > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19740) Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19740?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19740: ---------------------------------- Affects Version/s: 4.3.0.Alpha2 4.2.3.Final > Fix exception handling in freemarker to reveal origin of AssertionFailedExceptions > ---------------------------------------------------------------------------------- > > Key: JBIDE-19740 > URL: https://issues.jboss.org/browse/JBIDE-19740 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.3.Final, 4.3.0.Alpha2 > Reporter: Denis Golovin > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19740) Fix exception handling

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-19740: ------------------------------------- Summary: Fix exception handling Key: JBIDE-19740 URL: https://issues.jboss.org/browse/JBIDE-19740 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Denis Golovin -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18244) org.eclipse.core.runtime.AssertionFailedException when editing ftl file

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18244?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-18244: ------------------------------------- Assignee: Denis Golovin > 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, 12 months

1
0
0 / 0

[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: ------------------------------------- I can fix the issue with the installer, but there's something else going on here that's very strange. I have on my disk an installation of fsw 6.0.0 that matches our server bean loader, but the downloaded one does not. It seems the downloaded one has a slot=eap rather than soa, and no layers.conf, and no sramp. Something is very very wrong here. I know for a fact I've tested this before, and I have an installation that *does* match properly, so I have no idea why the two installations are so different. > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3322) JSR-356: Websockets. Content-assist for annotations

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3322?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3322: --------------------------------- Sprint: (was: Sprint #3 May 2015) > JSR-356: Websockets. Content-assist for annotations > --------------------------------------------------- > > Key: JBDS-3322 > URL: https://issues.jboss.org/browse/JBDS-3322 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Minor > Labels: websockets > Fix For: 9.0.0.Beta1 > > > As a Java EE developer, I wish to take advantage of the new Websockets capability. > Content-assist for annotations such as @ServerEndpoint, @OnMessage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3322) JSR-356: Websockets. Content-assist for annotations

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3322?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3322: ------------------------------------ Assignee: Alexey Kazakov (was: Viacheslav Kabanovich) > JSR-356: Websockets. Content-assist for annotations > --------------------------------------------------- > > Key: JBDS-3322 > URL: https://issues.jboss.org/browse/JBDS-3322 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Minor > Labels: websockets > Fix For: 9.0.0.Beta1 > > > As a Java EE developer, I wish to take advantage of the new Websockets capability. > Content-assist for annotations such as @ServerEndpoint, @OnMessage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19739) Websockets: Content assist for endpoint classes

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19739?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19739: ----------------------------------- Description: Content assist for classes annotated @ServerEndpoint or @ClientEndpoint with the following proposals: - Add @OnMessage method (if not present yet) - Add @OnOpen method - Add @OnClose method - Add @OnError method Labels: new_and_noteworthy (was: ) > Websockets: Content assist for endpoint classes > ----------------------------------------------- > > Key: JBIDE-19739 > URL: https://issues.jboss.org/browse/JBIDE-19739 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > > Content assist for classes annotated @ServerEndpoint or @ClientEndpoint with the following proposals: > - Add @OnMessage method (if not present yet) > - Add @OnOpen method > - Add @OnClose method > - Add @OnError method -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19739) Websockets: Content assist for endpoint classes

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-19739: -------------------------------------- Summary: Websockets: Content assist for endpoint classes Key: JBIDE-19739 URL: https://issues.jboss.org/browse/JBIDE-19739 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webservices Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.3.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13727) Enable generation of tests for Seam components

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13727?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-13727. ------------------------------------ Fix Version/s: 4.3.0.Beta1 (was: 4.3.x) Resolution: Won't Fix > Enable generation of tests for Seam components > ---------------------------------------------- > > Key: JBIDE-13727 > URL: https://issues.jboss.org/browse/JBIDE-13727 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: seam2 > Affects Versions: 4.0.0.Final, 4.1.0.Beta1 > Environment: JBDS 6.0.0.GA, JBDS 7.0.0.Beta1. JBDS 7.1.0.GA > Reporter: Tomas Remes > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > > Currently the test generation for Seam Action, Form is disabled (but not properly - see JBIDE-13596) because of previous Seam version (I guess 2.3.0.Final). In latest Seam version test can be already generated by seam-gen and are even valid and usable. > JBDS should enable and support this functionality again. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19704) Visual part of Visual/Source tab is empty for HTML page when JSF support enabled

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19704?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-19704: ------------------------------------- reproduced same behavior on RHEL 7 86_64 This simple page is not parsed by vpe with xulrunner However, *index.html* from jboss-as-kitchensink-html5-mobile is parsed like a charm. Pretty weird behavior > Visual part of Visual/Source tab is empty for HTML page when JSF support enabled > -------------------------------------------------------------------------------- > > Key: JBIDE-19704 > URL: https://issues.jboss.org/browse/JBIDE-19704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 19 64bit, JBDS 9.0.0.Alpha2-v20150421-1151-B25, Oracle JDK 1.7 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > > 1. Set Visual Editor to use JSF support > 2. Create simple HTML page like this and open it in VPE editor > {code:html} > <!DOCTYPE html> > <html> > <body> > <h1>test heading</h1> > </body> > </html> > {code} > ERROR: Visual part of Visual/Source tab of VPE is empty. > Visual tab of VPE renders page properly. > When HTML support is enabled it works fine. > I'm not sure if this is issue or expected behavior so if it's not an issue just mark it as won't fix please. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[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: ------------------------------------- Verified that this is, indeed, the installer jar. damn. > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19342) Update code to cope with generics added to org.eclipse.core.runtime package API

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19342?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19342: --------------------------------------- Building IAdapter hierarchy is not working for me fails with error explained here [451352|https://bugs.eclipse.org/bugs/show_bug.cgi?id=451352]. > Update code to cope with generics added to org.eclipse.core.runtime package API > -------------------------------------------------------------------------------- > > Key: JBIDE-19342 > URL: https://issues.jboss.org/browse/JBIDE-19342 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid, archives, batch, bean-validation, birt, browsersim, cdi, cdi-extensions, central, common/jst/core, cordovasim, forge, hibernate, integration-platform, jmx, jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Reporter: Fred Bricon > Priority: Minor > Fix For: 4.3.x > > > We need to detect and address any part of our code affected by generics added to the org.eclipse.core.runtime package API. > From https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11590.html : > {quote} > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021 > Markus Keller wrote up an nice summary of what consumers should do to fix any warnings that may be caused by this change at https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021#c25 > Here is a copy of the recommendations if you are going to compile against the latest version of org.eclipse.equinox.common: > 1. In MANIFEST.MF, update your Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.11.0,4.0.0)", or org.eclipse.equinox.common;bundle-version="[3.7.0,4.0.0)", or update your Import-Package: org.eclipse.core.runtime; version="[3.5,4.0)" > 2. If your bundle re-exports one of these bundles, then you also have to make sure the minor version is incremented. > 3. Remove unnecessary casts (Clean Up, or Problems view > Quick Fix > Select All) > 4. Update implementations of IAdaptable#getAdapter(Class<T>), unless you override another implementation of that method that still uses the old signature. > Typical change: > Old: > {code} > public Object getAdapter(Class adapter) { > if (ICompilationUnit.class.equals(adapter)) > return getCompilationUnit(); > return null; > } > {code} > New: > {code} > public <T> T getAdapter(Class<T> adapter) { > if (ICompilationUnit.class.equals(adapter)) > return adapter.cast(getCompilationUnit()); > return null; > } > {code} > 5. Update implementations of IAdapterFactory > Hint for 4. & 5.: > - Open Type Hierarchy on IAdaptable, etc. > - In the view menu, select a working set that contains your projects > - In the methods list of the Type Hierarchy view, select the methods, and then click the first toolbar button (Lock View and Show Members in Hierarchy) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18355) Unexpected chars in freemarker editor

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18355?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18355: ---------------------------------- Story Points: 0 Sprint: Sprint #2 April 2015 > Unexpected chars in freemarker editor > ------------------------------------- > > Key: JBIDE-18355 > URL: https://issues.jboss.org/browse/JBIDE-18355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1b, L64 > Reporter: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Beta1 > > Attachments: freemarker-strange-char.ogv, html-template.ftl > > > Strange characters occurs when editing ftl file (check the screencast) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-35) Add jboss-dmr 1.2.2.Final to locus

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/LOCUS-35?page=com.atlassian.jira.plugin.s... ] Rob Stryker commented on LOCUS-35: ---------------------------------- It ... seems to work? I removed the as.dmr plugin dependencies from as.core / as.ui and replaced it with the locus.dmr. So I guess I +1 this... though cautiously. > Add jboss-dmr 1.2.2.Final to locus > ---------------------------------- > > Key: LOCUS-35 > URL: https://issues.jboss.org/browse/LOCUS-35 > Project: JBoss Tools Locus > Issue Type: Feature Request > Reporter: Fred Bricon > Assignee: Mickael Istria > Fix For: 1.2.0 > > > We need to have provide jboss-dmr 1.2.2.Final as part of locus http://search.maven.org/#artifactdetails%7Corg.jboss%7Cjboss-dmr%7C1.2.2.... > {noformat}<dependency> > <groupId>org.jboss</groupId> > <artifactId>jboss-dmr</artifactId> > <version>1.2.2.Final</version> > </dependency>{noformat} > This will be consumed by foundation, server, central and probably other components -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18570) Creating EJB 3.x bean is asking EJB 2.x values

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18570?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18570: ------------------------------------- > and I'm sure Rob will be happy to reconsider It's not about me reconsidering ;) These are WTP wizards, so I'd need a compelling argument to get them to change their UI, which has been stable for a long time. > Creating EJB 3.x bean is asking EJB 2.x values > ---------------------------------------------- > > Key: JBIDE-18570 > URL: https://issues.jboss.org/browse/JBIDE-18570 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: ejb3, upstream > Reporter: Arun Gupta > Assignee: Rob Stryker > Fix For: 4.3.x > > Attachments: Screen Shot 2014-10-09 at 9.41.39 pm.png > > > Creating a singleton EJB using 3.x wizard and its asking for home and component interfaces from 2.x. This is confusing and redundant. > Image coming in attachment next. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19704) Visual part of Visual/Source tab is empty for HTML page when JSF support enabled

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19704?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-19704: ------------------------------------- However, that simple html should be parsed without any problems even with obsolete xulrunner IMO > Visual part of Visual/Source tab is empty for HTML page when JSF support enabled > -------------------------------------------------------------------------------- > > Key: JBIDE-19704 > URL: https://issues.jboss.org/browse/JBIDE-19704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 19 64bit, JBDS 9.0.0.Alpha2-v20150421-1151-B25, Oracle JDK 1.7 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > > 1. Set Visual Editor to use JSF support > 2. Create simple HTML page like this and open it in VPE editor > {code:html} > <!DOCTYPE html> > <html> > <body> > <h1>test heading</h1> > </body> > </html> > {code} > ERROR: Visual part of Visual/Source tab of VPE is empty. > Visual tab of VPE renders page properly. > When HTML support is enabled it works fine. > I'm not sure if this is issue or expected behavior so if it's not an issue just mark it as won't fix please. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19704) Visual part of Visual/Source tab is empty for HTML page when JSF support enabled

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19704?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-19704: ------------------------------------- I believe this is expected behavior - http://tools.jboss.org/documentation/faq/visualeditor.html#platform-speci... > Visual part of Visual/Source tab is empty for HTML page when JSF support enabled > -------------------------------------------------------------------------------- > > Key: JBIDE-19704 > URL: https://issues.jboss.org/browse/JBIDE-19704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 19 64bit, JBDS 9.0.0.Alpha2-v20150421-1151-B25, Oracle JDK 1.7 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > > 1. Set Visual Editor to use JSF support > 2. Create simple HTML page like this and open it in VPE editor > {code:html} > <!DOCTYPE html> > <html> > <body> > <h1>test heading</h1> > </body> > </html> > {code} > ERROR: Visual part of Visual/Source tab of VPE is empty. > Visual tab of VPE renders page properly. > When HTML support is enabled it works fine. > I'm not sure if this is issue or expected behavior so if it's not an issue just mark it as won't fix please. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19342) Update code to cope with generics added to org.eclipse.core.runtime package API

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19342?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19342: --------------------------------------- freemarker is not affected. > Update code to cope with generics added to org.eclipse.core.runtime package API > -------------------------------------------------------------------------------- > > Key: JBIDE-19342 > URL: https://issues.jboss.org/browse/JBIDE-19342 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid, archives, batch, bean-validation, birt, browsersim, cdi, cdi-extensions, central, common/jst/core, cordovasim, forge, hibernate, integration-platform, jmx, jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Reporter: Fred Bricon > Priority: Minor > Fix For: 4.3.x > > > We need to detect and address any part of our code affected by generics added to the org.eclipse.core.runtime package API. > From https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11590.html : > {quote} > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021 > Markus Keller wrote up an nice summary of what consumers should do to fix any warnings that may be caused by this change at https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021#c25 > Here is a copy of the recommendations if you are going to compile against the latest version of org.eclipse.equinox.common: > 1. In MANIFEST.MF, update your Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.11.0,4.0.0)", or org.eclipse.equinox.common;bundle-version="[3.7.0,4.0.0)", or update your Import-Package: org.eclipse.core.runtime; version="[3.5,4.0)" > 2. If your bundle re-exports one of these bundles, then you also have to make sure the minor version is incremented. > 3. Remove unnecessary casts (Clean Up, or Problems view > Quick Fix > Select All) > 4. Update implementations of IAdaptable#getAdapter(Class<T>), unless you override another implementation of that method that still uses the old signature. > Typical change: > Old: > {code} > public Object getAdapter(Class adapter) { > if (ICompilationUnit.class.equals(adapter)) > return getCompilationUnit(); > return null; > } > {code} > New: > {code} > public <T> T getAdapter(Class<T> adapter) { > if (ICompilationUnit.class.equals(adapter)) > return adapter.cast(getCompilationUnit()); > return null; > } > {code} > 5. Update implementations of IAdapterFactory > Hint for 4. & 5.: > - Open Type Hierarchy on IAdaptable, etc. > - In the view menu, select a working set that contains your projects > - In the methods list of the Type Hierarchy view, select the methods, and then click the first toolbar button (Lock View and Show Members in Hierarchy) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19342) Update code to cope with generics added to org.eclipse.core.runtime package API

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19342?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19342: ---------------------------------- Component/s: (was: freemarker) > Update code to cope with generics added to org.eclipse.core.runtime package API > -------------------------------------------------------------------------------- > > Key: JBIDE-19342 > URL: https://issues.jboss.org/browse/JBIDE-19342 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid, archives, batch, bean-validation, birt, browsersim, cdi, cdi-extensions, central, common/jst/core, cordovasim, forge, hibernate, integration-platform, jmx, jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Reporter: Fred Bricon > Priority: Minor > Fix For: 4.3.x > > > We need to detect and address any part of our code affected by generics added to the org.eclipse.core.runtime package API. > From https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11590.html : > {quote} > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021 > Markus Keller wrote up an nice summary of what consumers should do to fix any warnings that may be caused by this change at https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021#c25 > Here is a copy of the recommendations if you are going to compile against the latest version of org.eclipse.equinox.common: > 1. In MANIFEST.MF, update your Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.11.0,4.0.0)", or org.eclipse.equinox.common;bundle-version="[3.7.0,4.0.0)", or update your Import-Package: org.eclipse.core.runtime; version="[3.5,4.0)" > 2. If your bundle re-exports one of these bundles, then you also have to make sure the minor version is incremented. > 3. Remove unnecessary casts (Clean Up, or Problems view > Quick Fix > Select All) > 4. Update implementations of IAdaptable#getAdapter(Class<T>), unless you override another implementation of that method that still uses the old signature. > Typical change: > Old: > {code} > public Object getAdapter(Class adapter) { > if (ICompilationUnit.class.equals(adapter)) > return getCompilationUnit(); > return null; > } > {code} > New: > {code} > public <T> T getAdapter(Class<T> adapter) { > if (ICompilationUnit.class.equals(adapter)) > return adapter.cast(getCompilationUnit()); > return null; > } > {code} > 5. Update implementations of IAdapterFactory > Hint for 4. & 5.: > - Open Type Hierarchy on IAdaptable, etc. > - In the view menu, select a working set that contains your projects > - In the methods list of the Type Hierarchy view, select the methods, and then click the first toolbar button (Lock View and Show Members in Hierarchy) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8526) Freemarker content assist doesn't work when inside a tag or tag attribute

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8526?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-8526: --------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.2.x) (was: 4.3.x) > Freemarker content assist doesn't work when inside a tag or tag attribute > ------------------------------------------------------------------------- > > Key: JBIDE-8526 > URL: https://issues.jboss.org/browse/JBIDE-8526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 3.3.x > Environment: Windows XP, > Reporter: Ehrann Mehdan > Assignee: Peter Palaga > Fix For: 4.3.0.Beta1 > > > In Freemarker 1.1.0.v20110303-1225-H55-Alpha1 > Eclipse platform version: 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi > Build id: M20110210-1200 > This code will not trigger content assist when pressing ctrl+space with a context named data that has property "someValue" > <tag attribute="${data.someValue}">... > This code will (removed opening tag bracket) > tag attribute="${data.someValue}">... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8526) Freemarker content assist doesn't work when inside a tag or tag attribute

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8526?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-8526: --------------------------------- Sprint: Sprint #3 May 2015 > Freemarker content assist doesn't work when inside a tag or tag attribute > ------------------------------------------------------------------------- > > Key: JBIDE-8526 > URL: https://issues.jboss.org/browse/JBIDE-8526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 3.3.x > Environment: Windows XP, > Reporter: Ehrann Mehdan > Assignee: Peter Palaga > Fix For: 4.3.0.Beta1 > > > In Freemarker 1.1.0.v20110303-1225-H55-Alpha1 > Eclipse platform version: 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi > Build id: M20110210-1200 > This code will not trigger content assist when pressing ctrl+space with a context named data that has property "someValue" > <tag attribute="${data.someValue}">... > This code will (removed opening tag bracket) > tag attribute="${data.someValue}">... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18036) Decouple FTL target language syntax coloring

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18036?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18036: ---------------------------------- Sprint: Sprint #3 May 2015 > 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: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > 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.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18245) Freemarker syntax highlight issues

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18245?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18245: ---------------------------------- Sprint: Sprint #3 May 2015 > Freemarker syntax highlight issues > ---------------------------------- > > Key: JBIDE-18245 > URL: https://issues.jboss.org/browse/JBIDE-18245 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1 > Reporter: Jiri Peterka > Fix For: 4.3.0.Beta1 > > Attachments: syntax-highlight-issue.png > > > Create ftl file and paste: > {code} > <html> > <head> > <title>Welcome!</title> > </head> > <body> > <h1>Welcome ${user}!</h1> > <p>Our latest product: > <a href="${latestProduct.url}">${latestProduct.name}</a> > <#assign x = 1 />. > <#assign y = 1 /> > <#assign z = 1 /> > </body> > </html> > {code} > Syntax highlighting works very strange, see screenshot and make some atttempts, you will see it for your own. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18036) Decouple FTL target language syntax coloring

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18036?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18036: ---------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.x) > 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: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > 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.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18243) Freemarker syntax highlight requires file reopening

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18243?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18243: ---------------------------------- Sprint: Sprint #3 May 2015 > Freemarker syntax highlight requires file reopening > --------------------------------------------------- > > Key: JBIDE-18243 > URL: https://issues.jboss.org/browse/JBIDE-18243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1 > Reporter: Jiri Peterka > Fix For: 4.3.0.Beta1 > > > When pasting some code into ftl file, syntax highlight is not activated until file is saved closed and reopened. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19183) Constant AssertionFailedExceptions from FreeMarker Editor

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19183?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-19183. --------------------------------- Resolution: Duplicate Issue > Constant AssertionFailedExceptions from FreeMarker Editor > --------------------------------------------------------- > > Key: JBIDE-19183 > URL: https://issues.jboss.org/browse/JBIDE-19183 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.3.0.Alpha1 > Environment: Eclipse 4.4.1 > Linux > Reporter: Eric Sirianni > Fix For: 4.3.0.Beta1 > > > I get constant "assertion failed" errors in the freemarker editor. The error is associated with the following stack trace in my eclipse log: > {noformat} > !ENTRY org.eclipse.ui 4 0 2015-02-06 12:28:37.974 > !MESSAGE Unhandled event loop exception > !STACK 0 > 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.invalidateTextPresentation(TextViewer.java:3501) > at org.jboss.ide.eclipse.freemarker.editor.Editor.resetRange(Editor.java:282) > at org.jboss.ide.eclipse.freemarker.editor.Editor.highlightRelatedRegions(Editor.java:257) > at org.jboss.ide.eclipse.freemarker.editor.Editor.handleCursorPositionChanged(Editor.java:174) > at org.jboss.ide.eclipse.freemarker.editor.Editor.mouseUp(Editor.java:200) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) > {noformat} > This happens across multiple FreeMarker templates, all with very basic syntax. > I am using version 1.4.1.Final of the FreeMarker plugin. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18244) org.eclipse.core.runtime.AssertionFailedException when editing ftl file

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18244?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18244: ---------------------------------- Sprint: Sprint #3 May 2015 > 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 > 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, 12 months

1
0
0 / 0

[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 reassigned JBIDE-18752: ------------------------------------- Assignee: Denis Golovin (was: Max Rydahl Andersen) > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18355) Unexpected chars in freemarker editor

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18355?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-18355. ----------------------------------- Resolution: Rejected This is Eclipse quick diff ruler marks current unsaved changes. Rejecting > Unexpected chars in freemarker editor > ------------------------------------- > > Key: JBIDE-18355 > URL: https://issues.jboss.org/browse/JBIDE-18355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1b, L64 > Reporter: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Beta1 > > Attachments: freemarker-strange-char.ogv, html-template.ftl > > > Strange characters occurs when editing ftl file (check the screencast) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[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: 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: Max Rydahl Andersen > 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, 12 months

1
0
0 / 0

[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: ---------------------------------- Sprint: Sprint #2 April 2015 (was: Sprint #3 May 2015) > 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: Max Rydahl Andersen > 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, 12 months

1
0
0 / 0

[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: ---------------------------------- Sprint: Sprint #3 May 2015 > 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: Max Rydahl Andersen > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3628) Plugins should be packed jars not unpacked directories for efficiency sake

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3628?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-3628: --------------------------------- Component/s: (was: freemarker) > Plugins should be packed jars not unpacked directories for efficiency sake > -------------------------------------------------------------------------- > > Key: JBIDE-3628 > URL: https://issues.jboss.org/browse/JBIDE-3628 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common/jst/core, hibernate, jsf, visual-page-editor-core > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.x > > Attachments: exception.log > > > 65 of our plugins are bundled exploded instead of a .jar > Some are probably just mistakes and can easily be packed others are because of legacy code assuming it can access the files directly and even store data in the plugins - that should be fixed. > What should be fixed: > 1. The way how plug-ins use images in plugin.xml, in java code and in .meta xmodel files > 2. Plug-ins that loads resources should be aware that they are in jar now (VPE should be able to load templates from plugin jar files) > 3. Some plug-ins contain resources registered in XML catalog > 4. common.projecttemplates contains resources that is used as template for new projects > 5. Help content that is stored in zip files should be unpacked > 6. TBD -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18547) Generate index.html in default Dynamic Web Project

by Arun Gupta (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18547?page=com.atlassian.jira.plugi... ] Arun Gupta commented on JBIDE-18547: ------------------------------------ Sure, that would be fine too. > Generate index.html in default Dynamic Web Project > -------------------------------------------------- > > Key: JBIDE-18547 > URL: https://issues.jboss.org/browse/JBIDE-18547 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: upstream > Reporter: Arun Gupta > Assignee: Daniel Azarov > Fix For: 4.3.x > > Attachments: HtmlTemplates.png, screenshot-1.png > > > Default Dynamic Web Project does not contain index.html and so running it on a server always require to generate this file first. That's a very typical scenario and should be fixed for a more seamless experience. > Accessing the application at http://localhost:8080/helloworld/ shows "Forbidden" as shown in the attachment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18547) Generate index.html in default Dynamic Web Project

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18547?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-18547: --------------------------------------- Roberto Sanchez Herrera asks at Bugzilla: "why not generating an HTML 5 file? Just courious. I'm OK with what you propose." [~ArunGupta], could you comment this? > Generate index.html in default Dynamic Web Project > -------------------------------------------------- > > Key: JBIDE-18547 > URL: https://issues.jboss.org/browse/JBIDE-18547 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: upstream > Reporter: Arun Gupta > Assignee: Daniel Azarov > Fix For: 4.3.x > > Attachments: HtmlTemplates.png, screenshot-1.png > > > Default Dynamic Web Project does not contain index.html and so running it on a server always require to generate this file first. That's a very typical scenario and should be fixed for a more seamless experience. > Accessing the application at http://localhost:8080/helloworld/ shows "Forbidden" as shown in the attachment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-19605: ------------------------------------------- [~xcoulon] Any ideas on the test failures? Since everything seems to pass in the latest Jenkins builds, I suspect it may be something local? > Avoid need for multiple javax.servlet > ------------------------------------- > > Key: JBIDE-19605 > URL: https://issues.jboss.org/browse/JBIDE-19605 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Brian Fitzpatrick > Fix For: LATER > > Attachments: org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElement11ChangedProcessingTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessingTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.Jaxrs11ElementFactoryTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.Jaxrs20EndpointTestCase.txt > > > We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1. > {code} > On 04/15/2015 11:56 PM, Nick Boldt wrote: > > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and > > 3.1.0 in JBDS. > > More importantly... SHOULD we be including both? Or can we just include > > 3.1.0 and drop 3.0.0? > I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both). > So I've tried the ultimate test: > $ cd jbdevstudio-9.0.0.Alpha2/studio > $ rm plugins/javax.servlet_3.0.0* > $ ./jbdevstudio > And saw > !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967] > Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)" > at org.eclipse.osgi.container.Module.start(Module.java:434) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0. > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-19605: -------------------------------------- Attachment: org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElement11ChangedProcessingTestCase.txt org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.txt org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessingTestCase.txt org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.Jaxrs11ElementFactoryTestCase.txt org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.Jaxrs20EndpointTestCase.txt > Avoid need for multiple javax.servlet > ------------------------------------- > > Key: JBIDE-19605 > URL: https://issues.jboss.org/browse/JBIDE-19605 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Brian Fitzpatrick > Fix For: LATER > > Attachments: org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElement11ChangedProcessingTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessingTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.Jaxrs11ElementFactoryTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.Jaxrs20EndpointTestCase.txt > > > We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1. > {code} > On 04/15/2015 11:56 PM, Nick Boldt wrote: > > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and > > 3.1.0 in JBDS. > > More importantly... SHOULD we be including both? Or can we just include > > 3.1.0 and drop 3.0.0? > I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both). > So I've tried the ultimate test: > $ cd jbdevstudio-9.0.0.Alpha2/studio > $ rm plugins/javax.servlet_3.0.0* > $ ./jbdevstudio > And saw > !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967] > Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)" > at org.eclipse.osgi.container.Module.start(Module.java:434) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0. > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-19605: ------------------------------------------- Removed the following lines from the MANIFEST.MF for org.jboss.tools.ws.ui {code} javax.servlet;version="[2.4.0,3.0.0)", javax.servlet.http;version="[2.4.0,3.0.0)", {code} And it builds ok, and all the main JAX-WS tests pass fine but I have test failures in JAX-RS (org.jboss.tools.ws.jaxrs.core.test). Will attach the surefire logs. > Avoid need for multiple javax.servlet > ------------------------------------- > > Key: JBIDE-19605 > URL: https://issues.jboss.org/browse/JBIDE-19605 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Brian Fitzpatrick > Fix For: LATER > > > We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1. > {code} > On 04/15/2015 11:56 PM, Nick Boldt wrote: > > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and > > 3.1.0 in JBDS. > > More importantly... SHOULD we be including both? Or can we just include > > 3.1.0 and drop 3.0.0? > I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both). > So I've tried the ultimate test: > $ cd jbdevstudio-9.0.0.Alpha2/studio > $ rm plugins/javax.servlet_3.0.0* > $ ./jbdevstudio > And saw > !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967] > Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)" > at org.eclipse.osgi.container.Module.start(Module.java:434) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0. > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2044: ------------------------------------- I've tested devstudio build without references to org.eclipse.platform feature to check if it still has all product related feature. I removed everything related to platform feature and feature itself and ran the product build. Build and installation were fine no errors no .eclipseproduct file, but devstudio failed to start with error {code}!ENTRY org.eclipse.e4.ui.workbench 4 0 2015-04-28 11:25:37.892 !MESSAGE Unable to load resource platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi !STACK 0 org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: java.io.IOException: Unable to resolve plug-in "platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi". at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.handleDemandLoadException(ResourceSetImpl.java:319) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:278) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:406) at org.eclipse.e4.ui.internal.workbench.ResourceHandler.getResource(ResourceHandler.java:350) at org.eclipse.e4.ui.internal.workbench.ResourceHandler.loadResource(ResourceHandler.java:326) at org.eclipse.e4.ui.internal.workbench.ResourceHandler.loadMostRecentModel(ResourceHandler.java:243) at org.eclipse.e4.ui.internal.workbench.swt.E4Application.loadApplicationModel(E4Application.java:398) at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:255) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:620) 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) Caused by: java.io.IOException: Unable to resolve plug-in "platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi". at org.eclipse.core.internal.runtime.PlatformURLPluginConnection.parse(PlatformURLPluginConnection.java:65) at org.eclipse.core.internal.runtime.PlatformURLPluginConnection.resolve(PlatformURLPluginConnection.java:77) at org.eclipse.core.internal.boot.PlatformURLHandler.openConnection(PlatformURLHandler.java:69) at org.eclipse.osgi.internal.url.URLStreamHandlerProxy.openConnection(URLStreamHandlerProxy.java:114) at java.net.URL.openConnection(URL.java:971) at org.eclipse.emf.ecore.resource.impl.URIHandlerImpl.createInputStream(URIHandlerImpl.java:200) at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.createInputStream(ExtensibleURIConverterImpl.java:360) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1269) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:259) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:274) ... 24 more {code} After I added reference to org.eclipse.platform bundle everything went back to normal and no .eclipseproduct file. Only m2e* features has references to org.eclipse.platform feature and that is the reason we cannot include our own marker file with right product id in it. But as I said before that really doesn't harm anyone, because equinox will generate unique location to store its state info based on installation folder hash. So it is really optional issue to fix. > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Labels: discuss > Fix For: 8.x > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15481) setup of vwatch for jboss tools installations

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15481?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15481: ------------------------------- Description: 1. use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed. usecases: * find missing/weird versions * duplicate components * get list of potential unnecessary plugins in TP 2. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches – pre-existing doc here: http://download.jboss.org/jbosstools/updates/scripted-installation/ https://devstudio.redhat.com/download/scripted-install/ 3. test #2 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report 4. create new jobs (or extend existing ones) to provide reports about JBT, JBT+Central, JBT+Central+EA; repeat for JBDS combinations. Maybe migrate jobs to matrixes? Additionally, now that jbdevstudio-qa/vwatch has moved to jbosstools-versionwatch, we should also do these two things: 5. remove all refs to QA Jenkins file paths to make *.sh scripts more generic 6. migrate those internal file paths into jenkins config.xml files so they're not stored in public repos was: 1. use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed. usecases: * find missing/weird versions * duplicate components * get list of potential unnecessary plugins in TP 2. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches – pre-existing doc here: http://download.jboss.org/jbosstools/updates/scripted-installation/ https://devstudio.redhat.com/download/scripted-install/ 3. test #2 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report 4. create new jobs (or extend existing ones) to provide reports about JBT, JBT+Central, JBT+Central+EA; repeat for JBDS combinations. Maybe migrate jobs to matrixes? > setup of vwatch for jboss tools installations > --------------------------------------------- > > Key: JBIDE-15481 > URL: https://issues.jboss.org/browse/JBIDE-15481 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > Attachments: jbide15481.png > > > 1. use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed. > usecases: > * find missing/weird versions > * duplicate components > * get list of potential unnecessary plugins in TP > 2. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches – pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 3. test #2 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report > 4. create new jobs (or extend existing ones) to provide reports about JBT, JBT+Central, JBT+Central+EA; repeat for JBDS combinations. Maybe migrate jobs to matrixes? > Additionally, now that jbdevstudio-qa/vwatch has moved to jbosstools-versionwatch, we should also do these two things: > 5. remove all refs to QA Jenkins file paths to make *.sh scripts more generic > 6. migrate those internal file paths into jenkins config.xml files so they're not stored in public repos -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-35) Add jboss-dmr 1.2.2.Final to locus

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/LOCUS-35?page=com.atlassian.jira.plugin.s... ] Fred Bricon commented on LOCUS-35: ---------------------------------- mmm I see that 1.3.0.Final was released last week. http://search.maven.org/#artifactdetails%7Corg.jboss%7Cjboss-dmr%7C1.3.0..... We might as well use that instead. I'll see if it works for my plugins > Add jboss-dmr 1.2.2.Final to locus > ---------------------------------- > > Key: LOCUS-35 > URL: https://issues.jboss.org/browse/LOCUS-35 > Project: JBoss Tools Locus > Issue Type: Feature Request > Reporter: Fred Bricon > Assignee: Mickael Istria > Fix For: 1.2.0 > > > We need to have provide jboss-dmr 1.2.2.Final as part of locus http://search.maven.org/#artifactdetails%7Corg.jboss%7Cjboss-dmr%7C1.2.2.... > {noformat}<dependency> > <groupId>org.jboss</groupId> > <artifactId>jboss-dmr</artifactId> > <version>1.2.2.Final</version> > </dependency>{noformat} > This will be consumed by foundation, server, central and probably other components -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-431) Designer requires a new luna IS-TP complete with new version of LOCUS

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/JBTIS-431?page=com.atlassian.jira.plugin.... ] Paul Richardson commented on JBTIS-431: --------------------------------------- 4.2.3.CR1a - good for TD. Pushed update into TD master branch to build with this TP. > Designer requires a new luna IS-TP complete with new version of LOCUS > --------------------------------------------------------------------- > > Key: JBTIS-431 > URL: https://issues.jboss.org/browse/JBTIS-431 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Final-TP > Reporter: Paul Richardson > > https://issues.jboss.org/browse/LOCUS-23 defines a new requirement in locus that results in a new version of the locus update site. > Once a new build is available, Teiid Designer will need this locus version integrated into a new LUNA build of the IS-TP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18570) Creating EJB 3.x bean is asking EJB 2.x values

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18570?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18570: --------------------------------------- [~ArunGupta], I don't have an opinion on this, but if you still think this shouldn't be there or should be handled differently, let us know (including some arguments) and I'm sure Rob will be happy to reconsider :) Otherwise I will close this JIRA. > Creating EJB 3.x bean is asking EJB 2.x values > ---------------------------------------------- > > Key: JBIDE-18570 > URL: https://issues.jboss.org/browse/JBIDE-18570 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: ejb3, upstream > Reporter: Arun Gupta > Assignee: Rob Stryker > Fix For: 4.3.x > > Attachments: Screen Shot 2014-10-09 at 9.41.39 pm.png > > > Creating a singleton EJB using 3.x wizard and its asking for home and component interfaces from 2.x. This is confusing and redundant. > Image coming in attachment next. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-35) Add jboss-dmr 1.2.2.Final to locus

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/LOCUS-35?page=com.atlassian.jira.plugin.s... ] Fred Bricon commented on LOCUS-35: ---------------------------------- I built PR#39 locally and used the locus dmr plugin in the example plugin, everything compiles as expected > Add jboss-dmr 1.2.2.Final to locus > ---------------------------------- > > Key: LOCUS-35 > URL: https://issues.jboss.org/browse/LOCUS-35 > Project: JBoss Tools Locus > Issue Type: Feature Request > Reporter: Fred Bricon > Assignee: Mickael Istria > Fix For: 1.2.0 > > > We need to have provide jboss-dmr 1.2.2.Final as part of locus http://search.maven.org/#artifactdetails%7Corg.jboss%7Cjboss-dmr%7C1.2.2.... > {noformat}<dependency> > <groupId>org.jboss</groupId> > <artifactId>jboss-dmr</artifactId> > <version>1.2.2.Final</version> > </dependency>{noformat} > This will be consumed by foundation, server, central and probably other components -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19453) Remote host information does not fit in the server editor

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19453?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-19453: ---------------------------------- Attachment: server-editor-linux.png I tried the same on Linux (RHEL 7 with Gnome) and it is better, but the buttons are still a bit cut off: !server-editor-linux.png! Again, if I made the window wide enough, it will eventually show up correctly. So the minimal width of the column needs to be wider and it should be same on OS X and Linux - I thought it more or less was that way in the past. > Remote host information does not fit in the server editor > --------------------------------------------------------- > > Key: JBIDE-19453 > URL: https://issues.jboss.org/browse/JBIDE-19453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: remote-runtime-does-not-fit.png, server-editor-2.png, server-editor-linux.png > > > Today I noticed this. When I set up a remote server and then open it in the Server editor, the part under Server Behavior where it shows the remote host configuration (e.g. Remote Server Home) does not fix - it needs more space to the right, but it's hidden and there is no way to scroll to view it. > !remote-runtime-does-not-fit.png! > The same problem applies to both JBDS 8.1.0.Beta1 and JBDS 9.0.0.Alpha1. So you may want to clone this for 4.3.x. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19453) Remote host information does not fit in the server editor

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19453?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19453: --------------------------------------- OK, Max is right - when I make the window really really big then it's shown correctly. I counted that you need the window to be at least ~1030 pixels wide to show all the content properly. If I then start resizing the window to a smaller width, the two main columns will be getting smaller (cutting off more and more of the Browse buttons for the remote host) and eventually at the width of around 850 pixels, the horizontal scrollbar will appear and the columns will stay at this width even if you make the window smaller. > Remote host information does not fit in the server editor > --------------------------------------------------------- > > Key: JBIDE-19453 > URL: https://issues.jboss.org/browse/JBIDE-19453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: remote-runtime-does-not-fit.png, server-editor-2.png > > > Today I noticed this. When I set up a remote server and then open it in the Server editor, the part under Server Behavior where it shows the remote host configuration (e.g. Remote Server Home) does not fix - it needs more space to the right, but it's hidden and there is no way to scroll to view it. > !remote-runtime-does-not-fit.png! > The same problem applies to both JBDS 8.1.0.Beta1 and JBDS 9.0.0.Alpha1. So you may want to clone this for 4.3.x. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3430) Creating a AngularJS project from scratch fails with an error installing tern

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3430?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3430. ---------------------------- Fix Version/s: 9.0.0.Beta1 Resolution: Rejected Please stop using this pre-Alpha2 build from April 05. You're having problems because you're mixing old crap (April 05 pre-Alpha2 built in master branch) with new crap (April 17 Alpha2 actual bits built from Alpha2x branch). BTW, to know if you've mixed streams, compare the build numbers. B2918 (large number) = master. B13 (small number) = stable branch (Alpha2x). If you perform an update of JBDS first, you will be then able to install whatever Tern stuff you need. But because we hard code the version of Tern we require into the JST plugins, and that version is aligned to the version of JBDS, you have to update JBDS at the same time as installing Tern/JST. > Creating a AngularJS project from scratch fails with an error installing tern > ----------------------------------------------------------------------------- > > Key: JBDS-3430 > URL: https://issues.jboss.org/browse/JBDS-3430 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > > The error is: > Your original request has been modified. > "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead. > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150417-0104-B13) > Software currently installed: JBoss Developer Studio (Branded Product) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.package 9.0.0.Alpha2-v20150405-1144-B2918) > Only one of the following can be installed at once: > JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822) > JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150417-0104-B13) > Cannot satisfy dependency: > From: JBoss Developer Studio (Core Features) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.feature.feature.group 9.0.0.Alpha2-v20150405-1144-B2918) > To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha2-v20150322-0547-B822] > Cannot satisfy dependency: > From: JBoss Developer Studio (Branded Product) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.package 9.0.0.Alpha2-v20150405-1144-B2918) > To: com.jboss.devstudio.core.feature.feature.group [9.0.0.Alpha2-v20150405-1144-B2918] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822) > To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150417-0104-B13) > To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150417-0104-B13] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19049) Enable JBoss servers to run with java 9

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19049?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19049: --------------------------------------- I checked with latest nightly and indeed it works as Rob described. I would probably agree that it's not necessary to restrict the versions in the dialog. > Enable JBoss servers to run with java 9 > --------------------------------------- > > Key: JBIDE-19049 > URL: https://issues.jboss.org/browse/JBIDE-19049 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: Java9 > Fix For: 4.3.0.Beta1 > > > I briefly tried to use java 9 for our tooling and to run servers. > I downloaded it from here: > https://jdk9.java.net/download/ > {code} > nattura:8.0.2 rasp$ java -version > java version "1.9.0-ea" > Java(TM) SE Runtime Environment (build 1.9.0-ea-b45) > Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode) > {code} > I use OS X 10.10 Yosemite. > There are a couple of problems: > 1. When I add a WildFly 8.2 server into JBDS 8.0.2, I cannot change the runtime to use java 9 - it seems we restrict that. > 2. Even if I could, we need to make sure -XX:MaxPermSize is not used in the server launch command. When I tried to run WildFly 8.2 from the terminal, it wouldn't work unless I removed the max perm size argument. Apparently java 9 does not just ignore this parameter (as java 8 did), but it does not allow it at all. > {code} > nattura:bin rasp$ ./standalone.sh > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final > JAVA: /Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/bin/java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > Unrecognized VM option 'MaxPermSize=256m' > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {code} > Of course it's questionable if we should allow java 9 for current servers at all as they don't support it officially. But I would say there is no need to restrict it if it works. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19697: --------------------------------------- OK, so the mystery remains :) The Eclipse instance I was running when this happened is in: /Users/rasp/jbossqa/JBDS/9.0.0/Eclipse-runtime-test.app So how can one of these: $ECLIPSE_HOME/../../../../studio/runtime_locations.properties or in $ECLIPSE_HOME/../../studio/runtime_locations.properties. result in one of these /Users/rasp/jbossqa/JBDS/9.0.0/jbdevstudio-9.0.0.Alpha1-java8/studio/runtime_locations.properties /Users/rasp/jbossqa/JBDS/9.0.0/jbdevstudio-9.0.0.Alpha2-24/studio/runtime_locations.properties ? Remember my $ECLIPSE_HOME does not contain either jbdevstudio-9.0.0.Alpha1-java8 or jbdevstudio-9.0.0.Alpha2-24. That's just weird. > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19571) Add FSW to downloadable runtimes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19571?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19571: --------------------------------------- Actually it seems that the link downloads the FSW installer jar and not zip. So that might explain the problem. Indeed, I can only see the jar available on jboss.org: https://www.jboss.org/products/fsw/download/ So if they don't have a zip, that might be a no-go for us. > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19571) Add FSW to downloadable runtimes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19571?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19571: --------------------------------------- Of course if this is really the wrong link in stacks, then the JDF JIRA needs to be reopened, too. But I'll leave that to you - I'm not 100 % sure now that it's the link. > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19571) Add FSW to downloadable runtimes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19571?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-19571: ---------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19738) Failed runtime download offers no error message

by Martin Malina (JIRA)

Martin Malina created JBIDE-19738: ------------------------------------- Summary: Failed runtime download offers no error message Key: JBIDE-19738 URL: https://issues.jboss.org/browse/JBIDE-19738 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.2.3.Final Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.3.0.Beta1 While verifying JBIDE-19571 the runtime download failed and there was no error whatsoever. The download of FSW 6.0 almost started, but after a few seconds on the progress bar an error window showed up for a moment and then disappeared again and the download window was gone, too. After this, there was no error in the error view or the workspace log. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[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: --------------------------------------- No,it won't. JBosTools/JBDS doesn't search ECLIPSE_HOME/../*. It has found your EAP 6.3 in $ECLIPSE_HOME/../../../../studio/runtime_locations.properties or in $ECLIPSE_HOME/../../studio/runtime_locations.properties. > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9563?page=com.atlassian.jira.plugin... ] Martin Malina closed JBIDE-9563. -------------------------------- Thanks, Max :) And closing once more :) > AS7 does not pick hot-deployed jsp files > ---------------------------------------- > > Key: JBIDE-9563 > URL: https://issues.jboss.org/browse/JBIDE-9563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 4.2.0.Final > > > When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9563?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen resolved JBIDE-9563. ---------------------------------------- Fix Version/s: 4.2.0.Final Resolution: Done marking this as resolved against 4.2.0.Final where we added WF 8.2 support. Thanks for verifying [~mmalina] and Happy Birthday :) > AS7 does not pick hot-deployed jsp files > ---------------------------------------- > > Key: JBIDE-9563 > URL: https://issues.jboss.org/browse/JBIDE-9563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 4.2.0.Final > > > When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9563?page=com.atlassian.jira.plugin... ] Martin Malina commented on JBIDE-9563: -------------------------------------- And BTW I did want to check if WildFly just is set up for jsp devel mode by default, but I couldn't find it in standalone.xml and then I realized there is Undertow there, so it's all different. > AS7 does not pick hot-deployed jsp files > ---------------------------------------- > > Key: JBIDE-9563 > URL: https://issues.jboss.org/browse/JBIDE-9563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Priority: Minor > > When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9563?page=com.atlassian.jira.plugin... ] Martin Malina closed JBIDE-9563. -------------------------------- Closing again. > AS7 does not pick hot-deployed jsp files > ---------------------------------------- > > Key: JBIDE-9563 > URL: https://issues.jboss.org/browse/JBIDE-9563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Priority: Minor > > When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9563?page=com.atlassian.jira.plugin... ] Martin Malina resolved JBIDE-9563. ---------------------------------- Resolution: Done Resolving again. > AS7 does not pick hot-deployed jsp files > ---------------------------------------- > > Key: JBIDE-9563 > URL: https://issues.jboss.org/browse/JBIDE-9563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Priority: Minor > > When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9563?page=com.atlassian.jira.plugin... ] Martin Malina commented on JBIDE-9563: -------------------------------------- ok, so indeed it seems to have been fixed. I checked these three servers with JBDS 8.1.0.GA: JBoss AS 7.1.1 - hot deployment does not work - once you change the config according to AS7-659 (jsp devel mode) it works JBoss EAP 6.3.0 - same as above - hot deployment does not work - once I changed the config to jsp devel mode, it worked WildFly 8.2 - hot deployment works out of the box To be clear, this is what I did: 1. Set up a server in JBDS using runtime detection 2. Start the server 3. Deploy a dynamic web project with a jsp file 4. Check the jsp page in a browser 5. Change some text in the jsp, save 6. Check the jsp page in a browser again Assert: Is the change visible in the browser? So it seems all is good then. > AS7 does not pick hot-deployed jsp files > ---------------------------------------- > > Key: JBIDE-9563 > URL: https://issues.jboss.org/browse/JBIDE-9563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Priority: Minor > > When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19476) Add label validation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19476?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19476: ------------------------------------------ [~jcantrill] Can you please add steps so that QE [~mlabuda] can reproduce and verify this? > Add label validation > -------------------- > > Key: JBIDE-19476 > URL: https://issues.jboss.org/browse/JBIDE-19476 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > Add label key and value validations to the 'label' page in accordance of what is valid in Kubernetes. This should be part of the 'edit label' page that will be presented to a user -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19476) Add label validation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19476?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19476: ------------------------------------------ corrected minors, merged and pushed to upstream/master > Add label validation > -------------------- > > Key: JBIDE-19476 > URL: https://issues.jboss.org/browse/JBIDE-19476 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > Add label key and value validations to the 'label' page in accordance of what is valid in Kubernetes. This should be part of the 'edit label' page that will be presented to a user -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19291) "Unable to execute early startup code ..." exception after starup.

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19291?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-19291 at 4/29/15 5:39 AM: ---------------------------------------------------------------- I can still see this in my installation of JBDS 9.0.0.Alpha2 BYOE inside Eclipse Mars M6. So reopening. You might prefer reopening the other JIRA, but this one accurately shows the error message. Edit: Same thing happens in nightly installed today. was (Author: mmalina): I can still see this in my installation of JBDS 9.0.0.Alpha2 BYOE inside Eclipse Mars M6. So reopening. You might prefer reopening the other JIRA, but this one accurately shows the error message. > "Unable to execute early startup code ..." exception after starup. > ------------------------------------------------------------------ > > Key: JBIDE-19291 > URL: https://issues.jboss.org/browse/JBIDE-19291 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > After startup in error log there is this error: > {noformat:title=Unable to execute early startup code for the org.eclipse.ui.IStartup extension contributed by the 'org.jboss.ide.eclipse.as.ui' plug-in.} > org.eclipse.core.runtime.CoreException: Executable extension definition for "class" not found. > at org.eclipse.core.internal.registry.ConfigurationElement.throwException(ConfigurationElement.java:62) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:222) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) > at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:288) > at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:102) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:54) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2801) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19590: --------------------------------------------- sounds good! > Update module's README.md files with information about dependencies to other modules > ------------------------------------------------------------------------------------ > > Key: JBIDE-19590 > URL: https://issues.jboss.org/browse/JBIDE-19590 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > > For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development: > 1. Set up target platform in preferences > 2. Import JBT module sources into workspace > 3. Import required JBT module sources into worksapce > (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19190: --------------------------------------------- I thought we said we would keep as is for now and then do the extraction when needed ? I would say close this issue as done and add whatever cleanup is needed when JBIDE-15481 gets done ? > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Beta1 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 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 April 2015