June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19951) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [integration-tests]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19951?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19951: --------------------------------------- Awesome! :) > For JBIDE 4.3.0.Beta1: Code Freeze + Branch [integration-tests] > --------------------------------------------------------------- > > Key: JBIDE-19951 > URL: https://issues.jboss.org/browse/JBIDE-19951 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Beta1 [Central Discovery]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1; > {code} > mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta1x > git push origin jbosstools-4.3.0.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and > * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19973) Build with Tycho 0.23 (or wait for 0.24?)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19973?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19973 at 6/8/15 10:57 AM: ------------------------------------------------------------- The only reason to NOT move to 0.23 is this: {quote} The embedded p2 version has been updated to Mars RC2a. Noteworthy p2 changes: * {color:red}*(INCOMPATIBLE CHANGE)*{color} Due to a change in p2 publishers, MacOS products can no longer be built using p2 repositories older than eclipse Mars. Make sure you use Mars and configure a product installation root folder ending with ".app" (see Tycho demo project: http://git.eclipse.org/c/tycho/org.eclipse.tycho-demo.git/tree/itp04-rcp/... ). If you build a MacOS product (like JBDS or JBDS IS installers) and can't update to Mars (yet), you will probably have to skip this Tycho release. We intend to add a compatibility workaround in the next release of Tycho - https://bugs.eclipse.org/bugs/show_bug.cgi?id=463670 {quote} was (Author: nickboldt): The only reason to NOT move to 0.23 is this: {quote} The embedded p2 version has been updated to Mars RC2a. Noteworthy p2 changes: * {color:red}*(INCOMPATIBLE CHANGE)*{color} Due to a change in p2 publishers, MacOS products can no longer be built using p2 repositories older than eclipse Mars. Make sure you use Mars and configure a product installation root folder ending with ".app" (see Tycho demo project: http://git.eclipse.org/c/tycho/org.eclipse.tycho-demo.git/tree/itp04-rcp/.... If you build a MacOS product and can't update to Mars (yet), you will probably have to skip this Tycho release. We intend to add a compatibility workaround in the next release of Tycho - https://bugs.eclipse.org/bugs/show_bug.cgi?id=463670 {quote} > Build with Tycho 0.23 (or wait for 0.24?) > ----------------------------------------- > > Key: JBIDE-19973 > URL: https://issues.jboss.org/browse/JBIDE-19973 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Tycho 0.23 is released [1]. > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 > We should move parent pom, target platform builds, and other places where tychoVersion or tycho-version is set) to use the latest version. > This would also include releasing a new version of repo-utils and everything else in jbosstools-maven-plugins [2]. > [2] https://github.com/jbosstools/jbosstools-maven-plugins/tree/master/tycho-... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19973) Build with Tycho 0.23 (or wait for 0.24?)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19973?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19973 at 6/8/15 10:56 AM: ------------------------------------------------------------- The only reason to NOT move to 0.23 is this: {quote} The embedded p2 version has been updated to Mars RC2a. Noteworthy p2 changes: * {color:red}*(INCOMPATIBLE CHANGE)*{color} Due to a change in p2 publishers, MacOS products can no longer be built using p2 repositories older than eclipse Mars. Make sure you use Mars and configure a product installation root folder ending with ".app" (see Tycho demo project: http://git.eclipse.org/c/tycho/org.eclipse.tycho-demo.git/tree/itp04-rcp/.... If you build a MacOS product and can't update to Mars (yet), you will probably have to skip this Tycho release. We intend to add a compatibility workaround in the next release of Tycho - https://bugs.eclipse.org/bugs/show_bug.cgi?id=463670 {quote} was (Author: nickboldt): The embedded p2 version has been updated to Mars RC2a. Noteworthy p2 changes: * {color:red}*(INCOMPATIBLE CHANGE)*{color} Due to a change in p2 publishers, MacOS products can no longer be built using p2 repositories older than eclipse Mars. Make sure you use Mars and configure a product installation root folder ending with ".app" (see Tycho demo project: http://git.eclipse.org/c/tycho/org.eclipse.tycho-demo.git/tree/itp04-rcp/.... If you build a MacOS product and can't update to Mars (yet), you will probably have to skip this Tycho release. We intend to add a compatibility workaround in the next release of Tycho - https://bugs.eclipse.org/bugs/show_bug.cgi?id=463670 > Build with Tycho 0.23 (or wait for 0.24?) > ----------------------------------------- > > Key: JBIDE-19973 > URL: https://issues.jboss.org/browse/JBIDE-19973 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Tycho 0.23 is released [1]. > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 > We should move parent pom, target platform builds, and other places where tychoVersion or tycho-version is set) to use the latest version. > This would also include releasing a new version of repo-utils and everything else in jbosstools-maven-plugins [2]. > [2] https://github.com/jbosstools/jbosstools-maven-plugins/tree/master/tycho-... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19690) CheckboxTable and the select buttons are not being disabled

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19690?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-19690: ------------------------------------ Hi [~gastaldi], can you please provide some steps how to verify this issue? Thanks! > CheckboxTable and the select buttons are not being disabled > ------------------------------------------------------------ > > Key: JBIDE-19690 > URL: https://issues.jboss.org/browse/JBIDE-19690 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.0.Alpha2 > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Minor > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19954) Connecting to a server configured for basic auth with Oauth scheme provides no indication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19954?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19954: ------------------------------------- Priority: Critical (was: Major) > Connecting to a server configured for basic auth with Oauth scheme provides no indication > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19954 > URL: https://issues.jboss.org/browse/JBIDE-19954 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Priority: Critical > > Stand-up an openshift server configured to basic auth > Using JBT try to create a connection and retrieve an oauth token > Tooling performs some action but provides no indication that the attempt fails. > It previously worked until we had to alter the 'retrieve' browser to utilize external. This may be resolved if we can re-introduce the original browser dialog -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19796) Forge editor changes are not applied after changing font preferences

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19796?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19796. ------------------------------ Verified in JBT 4.3.0.Beta1. > Forge editor changes are not applied after changing font preferences > -------------------------------------------------------------------- > > Key: JBIDE-19796 > URL: https://issues.jboss.org/browse/JBIDE-19796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.0.Alpha2 > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.3.0.Beta1 > > > 1. Start the Forge console > 2. Go to Eclipse Settings -> General -> Appearance -> Colors and Fonts > 3. Choose the _Forge Console Font_ under the Forge category > 4. Apply changes > 5. Forge console editor should have been changed to match your settings, but it does not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19973) Build with Tycho 0.23 (or wait for 0.24?)

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19973?page=com.atlassian.jira.plugi... ] Paul Leacu commented on JBIDE-19973: ------------------------------------ +1 - go for it - rather find any issues earlier rather than later.... > Build with Tycho 0.23 (or wait for 0.24?) > ----------------------------------------- > > Key: JBIDE-19973 > URL: https://issues.jboss.org/browse/JBIDE-19973 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Tycho 0.23 is released [1]. > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 > We should move parent pom, target platform builds, and other places where tychoVersion or tycho-version is set) to use the latest version. > This would also include releasing a new version of repo-utils and everything else in jbosstools-maven-plugins [2]. > [2] https://github.com/jbosstools/jbosstools-maven-plugins/tree/master/tycho-... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19699) jpa new entity: java.lang.IllegalArgumentException

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19699?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19699. ------------------------------ Verified in JBT 4.3.0.Beta1. > jpa new entity: java.lang.IllegalArgumentException > --------------------------------------------------- > > Key: JBIDE-19699 > URL: https://issues.jboss.org/browse/JBIDE-19699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.0.Alpha2 > Environment: forge 2.16.0 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.3.0.Beta1 > > > {code} > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException) > at org.eclipse.swt.SWT.error(SWT.java:4481) > at org.eclipse.swt.SWT.error(SWT.java:4396) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3997) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3674) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:210) > at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:102) > at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog$1$1.handleElementSelected(UICommandListDialog.java:233) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:322) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:312) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents$1.keyPressed(QuickAccessContents.java:343) > 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:4203) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1504) > at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1634) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1500) > at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1600) > at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1060) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5757) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) > at org.eclipse.swt.widgets.Widget.superKeyDown(Widget.java:1908) > at org.eclipse.swt.widgets.Widget.keyDown(Widget.java:1085) > at org.eclipse.swt.widgets.Control.keyDown(Control.java:2406) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5667) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) > at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2105) > at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2337) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5729) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5166) > at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5315) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3669) > 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: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) > Caused by: java.lang.IllegalArgumentException > at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.AST.newName(AST.java:1938) > at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setPackage(AbstractJavaSource.java:521) > at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setPackage(AbstractJavaSource.java:56) > at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.buildJavaSource(AbstractJavaSourceCommand.java:192) > at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.classExists(AbstractJavaSourceCommand.java:162) > at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.access$100(AbstractJavaSourceCommand.java:58) > at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:100) > at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:92) > at org.jboss.forge.furnace.util.Callables.call(Callables.java:43) > at org.jboss.forge.addon.ui.impl.input.AbstractInputComponent.isEnabled(AbstractInputComponent.java:99) > at sun.reflect.GeneratedMethodAccessor319.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103) > at org.jboss.forge.addon.facets.AbstractFaceted_$$_javassist_73339967-8f00-406f-8f86-d626f933e158.isEnabled(AbstractFaceted_$$_javassist_73339967-8f00-406f-8f86-d626f933e158.java) > at sun.reflect.GeneratedMethodAccessor325.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) > at org.jboss.forge.addon.facets.AbstractFaceted_$$_javassist_58de67b1-36c3-4a0d-b29d-b8b860d2a3f0.isEnabled(AbstractFaceted_$$_javassist_58de67b1-36c3-4a0d-b29d-b8b860d2a3f0.java) > at org.jboss.tools.forge.ui.internal.ext.control.ControlBuilder.updateState(ControlBuilder.java:192) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage.updatePageState(ForgeWizardPage.java:203) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage.validatePage(ForgeWizardPage.java:237) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage.access$5(ForgeWizardPage.java:233) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage$1$1.run(ForgeWizardPage.java:180) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > ... 60 more > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19774) Visual Editor: XulRunner Engine on Linux is always used if browser was opened before Visual Editor

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19774?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-19774: ------------------------------------- Test cases are defined within JBIDE-1973 > Visual Editor: XulRunner Engine on Linux is always used if browser was opened before Visual Editor > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19774 > URL: https://issues.jboss.org/browse/JBIDE-19774 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha2 > Environment: Linux > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.3.0.Beta1 > > > While testing new Central I notice that if Central was opened before visual editor, XulRunner engine is always used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19401) remove Seam & Portlet from JBT 4.3 default install

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19401?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19401. ------------------------------- Verified with JBT 4.3.0.Beta1-v20150605-1926-B3 > remove Seam & Portlet from JBT 4.3 default install > --------------------------------------------------- > > Key: JBIDE-19401 > URL: https://issues.jboss.org/browse/JBIDE-19401 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein, seam2 > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Recently we removed Seams and Portlet from the default JBDS 9 install. Max said today we should do the same for JBT 4.3. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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