[JBoss JIRA] (JBIDE-19513) multiple versions of jetty and java.servlet plugins in JBDS 9
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19513?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-19513:
---------------------------------------
[~maxandersen], [~ibuziuk], [~mickael_istria],
+1: once the TP contains all the bundles I need for LiveReload, I'll migrate the code.
> multiple versions of jetty and java.servlet plugins in JBDS 9
> -------------------------------------------------------------
>
> Key: JBIDE-19513
> URL: https://issues.jboss.org/browse/JBIDE-19513
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa, target-platform, updatesite
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Ilya Buziuk
> Fix For: 4.3.0.Alpha2
>
>
> These plugins versions are included in JBDS 9 with multiple versions. We need to decide if this is acceptable / intentional, or something to fix.
> {code}
> org.eclipse.jetty.http_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.servlet_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.server_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.security_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.continuation_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.util_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.io_8.1.14.v20131031 and 9.2.5
> - and -
> javax.servlet_3.1.0.v201410161800 and 3.0.0{code}
> Pre-existing ignored/known issues:
> {code}
> org.eclipse.jdt.annotation_1.1.100.v20140704-0625
> com.jcraft.jsch_0.1.50.v201403120620
> org.apache.commons.logging_1.0.4.v201101211617
> javax.wsdl_1.5.1.v201012040544 {code}
> See detailed reports here:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19511) RuntimeException in error log when choosing decorated interface by double click
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19511?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-19511:
------------------------------------------
Reported to bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=463176
> RuntimeException in error log when choosing decorated interface by double click
> -------------------------------------------------------------------------------
>
> Key: JBIDE-19511
> URL: https://issues.jboss.org/browse/JBIDE-19511
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.x
>
>
> {code}
> java.lang.RuntimeException
> at org.eclipse.jface.viewers.ColumnViewer.checkBusy(ColumnViewer.java:760)
> at org.eclipse.jface.viewers.AbstractTableViewer.replace(AbstractTableViewer.java:1016)
> at org.eclipse.ui.dialogs.FilteredItemsSelectionDialog$ContentProvider.updateElement(FilteredItemsSelectionDialog.java:2800)
> at org.eclipse.jface.viewers.AbstractTableViewer$VirtualManager$1.handleEvent(AbstractTableViewer.java:83)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1437)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1422)
> at org.eclipse.swt.widgets.Table.checkData(Table.java:284)
> at org.eclipse.swt.widgets.Table.cellDataProc(Table.java:223)
> at org.eclipse.swt.widgets.Display.cellDataProc(Display.java:761)
> at org.eclipse.swt.internal.gtk.OS._gtk_list_store_set(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_list_store_set(OS.java:9042)
> at org.eclipse.swt.widgets.TableItem.setText(TableItem.java:1164)
> at org.eclipse.jface.viewers.TableViewerRow.setText(TableViewerRow.java:114)
> at org.eclipse.jface.viewers.ViewerCell.setText(ViewerCell.java:159)
> at org.eclipse.ui.dialogs.FilteredItemsSelectionDialog$ItemsListLabelProvider.update(FilteredItemsSelectionDialog.java:1674)
> at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:154)
> at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:385)
> at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:473)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.refreshItem(StructuredViewer.java:1573)
> at org.eclipse.jface.viewers.AbstractTableViewer.replace(AbstractTableViewer.java:1019)
> at org.eclipse.ui.dialogs.FilteredItemsSelectionDialog$ContentProvider.updateElement(FilteredItemsSelectionDialog.java:2800)
> at org.eclipse.jface.viewers.AbstractTableViewer.getVirtualSelection(AbstractTableViewer.java:489)
> at org.eclipse.jface.viewers.AbstractTableViewer.getSelectionFromWidget(AbstractTableViewer.java:460)
> at org.eclipse.jface.viewers.StructuredViewer.getSelection(StructuredViewer.java:1040)
> at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1732)
> at org.eclipse.jface.viewers.TableViewer.setSelection(TableViewer.java:162)
> at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:388)
> at org.eclipse.ui.dialogs.FilteredItemsSelectionDialog.refresh(FilteredItemsSelectionDialog.java:961)
> at org.eclipse.ui.dialogs.FilteredItemsSelectionDialog$RefreshJob.runInUIThread(FilteredItemsSelectionDialog.java:1391)
> at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:97)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3793)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3431)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.jdt.internal.ui.dialogs.FilteredTypesSelectionDialog.open(FilteredTypesSelectionDialog.java:512)
> at org.eclipse.jdt.ui.wizards.NewTypeWizardPage.chooseSuperInterfaces(NewTypeWizardPage.java:2046)
> at org.eclipse.jdt.ui.wizards.NewTypeWizardPage.typePageCustomButtonPressed(NewTypeWizardPage.java:1093)
> at org.eclipse.jdt.ui.wizards.NewTypeWizardPage.access$1(NewTypeWizardPage.java:1091)
> at org.eclipse.jdt.ui.wizards.NewTypeWizardPage$TypeFieldsAdapter.customButtonPressed(NewTypeWizardPage.java:1037)
> at org.eclipse.jdt.internal.ui.wizards.dialogfields.ListDialogField.buttonPressed(ListDialogField.java:209)
> at org.eclipse.jdt.internal.ui.wizards.dialogfields.ListDialogField.doButtonSelected(ListDialogField.java:478)
> at org.eclipse.jdt.internal.ui.wizards.dialogfields.ListDialogField.access$0(ListDialogField.java:474)
> at org.eclipse.jdt.internal.ui.wizards.dialogfields.ListDialogField$2.widgetSelected(ListDialogField.java:440)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3818)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3818)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19513) multiple versions of jetty and java.servlet plugins in JBDS 9
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19513?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-19513:
-------------------------------------
[~maxandersen] I'm totally fine with jetty 8 removal once PR for JBIDE-19497 and changes for JBIDE-18804 (all is done just waiting for TP update for creating PRs) will be applied.
4.3.0.Alpha2 sounds like a good time for doing this clean-up.
> multiple versions of jetty and java.servlet plugins in JBDS 9
> -------------------------------------------------------------
>
> Key: JBIDE-19513
> URL: https://issues.jboss.org/browse/JBIDE-19513
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa, target-platform, updatesite
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Ilya Buziuk
>
> These plugins versions are included in JBDS 9 with multiple versions. We need to decide if this is acceptable / intentional, or something to fix.
> {code}
> org.eclipse.jetty.http_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.servlet_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.server_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.security_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.continuation_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.util_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.io_8.1.14.v20131031 and 9.2.5
> - and -
> javax.servlet_3.1.0.v201410161800 and 3.0.0{code}
> Pre-existing ignored/known issues:
> {code}
> org.eclipse.jdt.annotation_1.1.100.v20140704-0625
> com.jcraft.jsch_0.1.50.v201403120620
> org.apache.commons.logging_1.0.4.v201101211617
> javax.wsdl_1.5.1.v201012040544 {code}
> See detailed reports here:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19513) multiple versions of jetty and java.servlet plugins in JBDS 9
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19513?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-19513:
-------------------------------------------
Assignee: Ilya Buziuk
[~ibuziuk] and [~xcoulon] I believe you are the ones using jetty directly.
Is there anything preventing us to move livereload and browsersim to Jetty 9 ?
Assuming no, what is the ETA for us having moving things to Jetty 9 so we can try remove Jetty 8 and get this cleaned up ?
> multiple versions of jetty and java.servlet plugins in JBDS 9
> -------------------------------------------------------------
>
> Key: JBIDE-19513
> URL: https://issues.jboss.org/browse/JBIDE-19513
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa, target-platform, updatesite
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Ilya Buziuk
>
> These plugins versions are included in JBDS 9 with multiple versions. We need to decide if this is acceptable / intentional, or something to fix.
> {code}
> org.eclipse.jetty.http_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.servlet_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.server_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.security_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.continuation_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.util_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.io_8.1.14.v20131031 and 9.2.5
> - and -
> javax.servlet_3.1.0.v201410161800 and 3.0.0{code}
> Pre-existing ignored/known issues:
> {code}
> org.eclipse.jdt.annotation_1.1.100.v20140704-0625
> com.jcraft.jsch_0.1.50.v201403120620
> org.apache.commons.logging_1.0.4.v201101211617
> javax.wsdl_1.5.1.v201012040544 {code}
> See detailed reports here:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3208 at 3/25/15 10:54 PM:
------------------------------------------------------------
New snapshots folder for builds w/ dynamic generation of latest symlinks and automated cleanup:
http://download.jboss.org/jbosstools/mars/snapshots/builds/
New composite sites:
http://download.jboss.org/jbosstools/mars/snapshots/builds/_composite_/co...
http://download.jboss.org/jbosstools/mars/snapshots/builds/_composite_/co...
New update sites:
http://download.jboss.org/jbosstools/mars/snapshots/updates/
New discovery sites:
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
(TODO: need to figure out where to also publish these as /mars/snapshots/discovery/ ?)
was (Author: nickboldt):
New snapshots folder for builds w/ dynamic generation of latest symlinks and automated cleanup:
http://download.jboss.org/jbosstools/mars/snapshots/builds/
New composite sites:
http://download.jboss.org/jbosstools/mars/snapshots/builds/_composite_/co...
http://download.jboss.org/jbosstools/mars/snapshots/builds/_composite_/co...
New update sites:
http://download.jboss.org/jbosstools/mars/snapshots/updates/
New discovery sites:
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
(TODO: need to fix missing /latest/ symlinks and enable cleanup here too; also need to figure out where to also publish these as /mars/snapshots/discovery/ ?)
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> Latest suggestion:
> * /\{mars,9.0}/
> ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
> *** /*updates*/
> **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
> ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
> *** /*builds*/
> **** /<job-name>/
> ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/
> ---
> Older idea:
> {code}
> <download.jboss.org,devstudio.redhat.com>
> <earlyaccess,updates,discovery>/<mars,9.0>
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last N builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBDS-3379) Error message in JBDS when installing into existing folder needs work
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3379?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-3379:
--------------------------------
Assignee: Denis Golovin (was: Nick Boldt)
> Error message in JBDS when installing into existing folder needs work
> ---------------------------------------------------------------------
>
> Key: JBDS-3379
> URL: https://issues.jboss.org/browse/JBDS-3379
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 9.0.0.Alpha2
>
> Attachments: over-the-top-message-JBDS8.1Beta1.png
>
>
> Got an error message trying to install JBDS into an existing JBDS folder:
> {quote}You can't upgrade by installing over the top (sic){quote}
> !over-the-top-message-JBDS8.1Beta1.png!
> We should consider fixing this message in JBDS 9. Perhaps something like this?
> {quote}Specified folder already contains a JBoss Developer Studio installation. One does not simply install into an existing install folder. Choose another folder or cancel this installer and run JBoss Developer Studio to perform an update.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months