[JBoss JIRA] (JBIDE-13786) Can't create JSF 1.2 project for JBoss AS 7.1 runtime
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13786?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-13786:
-----------------------------------------------
Runtime does not matter. The issue is reproduced only when project name coincides with that of a previously deleted project without deleting it from disk. Wizard tries to prompt user with a dialog asking if he wants to overwrite the old project. Since a modification done 5 months ago, operation is run out of UI thread, which causes the exception. The fix will run this part of the operation in UI thread.
> Can't create JSF 1.2 project for JBoss AS 7.1 runtime
> -----------------------------------------------------
>
> Key: JBIDE-13786
> URL: https://issues.jboss.org/browse/JBIDE-13786
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF
> Affects Versions: 4.1.0.Alpha2
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
> Fix For: 4.1.0.Alpha2
>
>
> If I try to create a JSF 1.2 project with libs for AS 7.1. I got the following exception when press finish (it works ok with AS 6.1):
> {code}
> java.lang.reflect.InvocationTargetException
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028)
> at org.jboss.tools.jst.web.ui.wizards.project.NewWebProjectWizard.performFinish(NewWebProjectWizard.java:66)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> 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.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3705)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3326)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:117)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3705)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3326)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1057)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:941)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: org.eclipse.core.runtime.AssertionFailedException: null argument:The dialog should be created in UI thread
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.jface.dialogs.IconAndMessageDialog.getSWTImage(IconAndMessageDialog.java:282)
> at org.eclipse.jface.dialogs.IconAndMessageDialog.getWarningImage(IconAndMessageDialog.java:242)
> at org.eclipse.jface.dialogs.MessageDialog.<init>(MessageDialog.java:193)
> at org.jboss.tools.common.model.ui.wizards.one.ServiceDialogImpl.showDialog(ServiceDialogImpl.java:62)
> at org.jboss.tools.jst.web.ui.operation.WebProjectCreationOperation.checkOverwrite(WebProjectCreationOperation.java:193)
> at org.jboss.tools.jst.web.ui.operation.WebNatureOperation.clearProjectRoot(WebNatureOperation.java:280)
> at org.jboss.tools.jst.web.ui.operation.WebNatureOperation.run(WebNatureOperation.java:216)
> at org.eclipse.ui.actions.WorkspaceModifyDelegatingOperation.execute(WorkspaceModifyDelegatingOperation.java:69)
> at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13788) mvn package
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13788?page=com.atlassian.jira.plugi... ]
Burr Sutter updated JBIDE-13788:
--------------------------------
Attachment: Screen Shot 2013-03-13 at 5.39.10 PM.png
2013-03-13_1738.png
> mvn package
> -----------
>
> Key: JBIDE-13788
> URL: https://issues.jboss.org/browse/JBIDE-13788
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Burr Sutter
> Attachments: 2013-03-13_1738.png, Screen Shot 2013-03-13 at 5.39.10 PM.png
>
>
> In Java EE land you tend to use "mvn package", but that is not listed in the menu, nor is it visible in the dialog. Not too mention, having the Maven commands under the Run menu option, instead of the Maven menu is counter-intuitive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13788) mvn package
by Burr Sutter (JIRA)
Burr Sutter created JBIDE-13788:
-----------------------------------
Summary: mvn package
Key: JBIDE-13788
URL: https://issues.jboss.org/browse/JBIDE-13788
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Burr Sutter
In Java EE land you tend to use "mvn package", but that is not listed in the menu, nor is it visible in the dialog. Not too mention, having the Maven commands under the Run menu option, instead of the Maven menu is counter-intuitive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBTIS-2) ensure all ten (10) JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-2?page=com.atlassian.jira.plugin.sy... ]
Nick Boldt reassigned JBTIS-2:
------------------------------
Assignee: Paul Leacu (was: Nick Boldt)
Is this a done issue?
> ensure all ten (10) JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-2
> URL: https://issues.jboss.org/browse/JBTIS-2
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Nick Boldt
> Assignee: Paul Leacu
>
> For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/.
> This issue should be a container for child issues assigned to each project's releng person.
> Most important part of this is the documentation of process / rules / expecations / nomenclature, and creation of tooling to make it simple for project leads to publish & promote their bits:
> * JBIDE-12220 create generic publishing job which takes as input three parameters
> Done:
> * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw...
> * Modeshape Tools - JBBUILD-720, MODE-1506
> *- http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooli... and
> *- http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling...
> Publishes elsewhere, manually symlinked:
> * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr...
> Publishes elsewhere:
> * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/
> * pi4soa - http://pi4soa.sourceforge.net/updates/
> Publishes as zip only:
> * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi...
> No publishing or archiving strategy (staging only):
> * SOA Runtime Detection - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
> * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
> * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
> --> see also https://issues.jboss.org/browse/JBIDE-12631
> * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
> ---
> Once all the components are publishing sites, they can
> a) easily link to those individual sites from their download pages on www.jboss.org/{projectname}
> b) easily composite those sites into a single site and reference that site from www.jboss.org/tools/
> c) more easily aggregate the components into a single site & zip, proving that the content can be co-installed via p2 and that there are no unmet or conflicting dependencies
> d) (with a through c met) therefore provide additional stability checking for JBDS SOA/BRMS tooling, provided individually via JBDS Central.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years