[JBoss JIRA] (JBIDE-19469) java.lang.IllegalStateException: A project is required in the current context
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-19469:
----------------------------------
Summary: java.lang.IllegalStateException: A project is required in the current context
Key: JBIDE-19469
URL: https://issues.jboss.org/browse/JBIDE-19469
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.2.3.CR1
Reporter: Pavol Srna
Priority: Critical
{code}
java.lang.IllegalStateException: A project is required in the current context
at org.jboss.forge.addon.projects.ui.AbstractProjectCommand.getSelectedProject(AbstractProjectCommand.java:78)
at org.jboss.forge.addon.as.ui.AbstractASWizardImpl.getSelectedProvider(AbstractASWizardImpl.java:82)
at org.jboss.forge.addon.as.ui.AbstractASWizardImpl.isEnabled(AbstractASWizardImpl.java:61)
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:497)
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.as.ui.ASShutdownWizardImpl_$$_javassist_ab26a278-6cdf-48c3-8310-63c36d4f93cb.isEnabled(ASShutdownWizardImpl_$$_javassist_ab26a278-6cdf-48c3-8310-63c36d4f93cb.java)
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:497)
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.ui.wizard.UIWizard_$$_javassist_6536f3f8-f9ef-4b61-af8f-308725a51e37.isEnabled(UIWizard_$$_javassist_6536f3f8-f9ef-4b61-af8f-308725a51e37.java)
at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.getAllCandidatesAsList(WizardDialogHelper.java:65)
at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog.getProviders(UICommandListDialog.java:255)
at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog.access$1(UICommandListDialog.java:251)
at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog$1.run(UICommandListDialog.java:195)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog.createDialogArea(UICommandListDialog.java:184)
at org.eclipse.jface.dialogs.PopupDialog.createContents(PopupDialog.java:715)
at org.eclipse.jface.window.Window.create(Window.java:435)
at org.eclipse.jface.dialogs.PopupDialog.open(PopupDialog.java:1159)
at org.jboss.tools.forge.ui.internal.ext.handlers.ForgeCommandHandler$1$1.run(ForgeCommandHandler.java:55)
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:3774)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3412)
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: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:497)
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)
11 years, 1 month
[JBoss JIRA] (JBDS-3306) Create Deployment from Template
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3306?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3306:
-----------------------------
CDW docs_ack: ?
CDW devel_ack: ?
> Create Deployment from Template
> -------------------------------
>
> Key: JBDS-3306
> URL: https://issues.jboss.org/browse/JBDS-3306
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift, requirements
> Reporter: Burr Sutter
> Priority: Blocker
> Fix For: 9.0.0.Beta1
>
>
> Use Case #3
> Create Deployment from Template
> a) Assume OpenShift is started remotely and provides an entrypoint URL
> b) Assume end-user is logged in (ignore auth for now)
> c) Eclipse user will open a dialog and enter the URL from step a
> d) Eclipse user will then be presented with a list of templates from the template library
> (initially a set of files on the local filesystem until openshift has a real template library api)
> e) The template list should allow sorting so that higher priority items are at the top
> We will likely need some form of categorization for templates also
> f) The template list should be searchable by keyword
> g) Eclipse user will select a particular template and
> h) Create a new openshift deployment based on selected template
> i) follow steps JBDS-3297 f through j (clone, import, project facets, etc)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBDS-3306) Create Deployment from Template
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3306?page=com.atlassian.jira.plugin.... ]
Burr Sutter updated JBDS-3306:
------------------------------
CDW pm_ack: + (was: ?)
> Create Deployment from Template
> -------------------------------
>
> Key: JBDS-3306
> URL: https://issues.jboss.org/browse/JBDS-3306
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift, requirements
> Reporter: Burr Sutter
> Priority: Blocker
> Fix For: 9.0.0.Beta1
>
>
> Use Case #3
> Create Deployment from Template
> a) Assume OpenShift is started remotely and provides an entrypoint URL
> b) Assume end-user is logged in (ignore auth for now)
> c) Eclipse user will open a dialog and enter the URL from step a
> d) Eclipse user will then be presented with a list of templates from the template library
> (initially a set of files on the local filesystem until openshift has a real template library api)
> e) The template list should allow sorting so that higher priority items are at the top
> We will likely need some form of categorization for templates also
> f) The template list should be searchable by keyword
> g) Eclipse user will select a particular template and
> h) Create a new openshift deployment based on selected template
> i) follow steps JBDS-3297 f through j (clone, import, project facets, etc)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3273:
------------------------------------
Unresolved QE ambiguity review question - preventing QE from acking:
What will users see when this is implemented? Will they be able to search (how?) for quickstarts?
> JBoss Central: Automatic upstream quickstart integration
> ---------------------------------------------------------
>
> Key: JBDS-3273
> URL: https://issues.jboss.org/browse/JBDS-3273
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 9.0.0.Alpha2
>
>
> Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month