[JBoss JIRA] (JBIDE-15318) Import Maven Archetype Project Example ignores JBoss Maven Integration preferences
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15318?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-15318:
--------------------------------
Fix Version/s: (was: 4.1.1.Final)
> Import Maven Archetype Project Example ignores JBoss Maven Integration preferences
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-15318
> URL: https://issues.jboss.org/browse/JBIDE-15318
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, project-examples
> Affects Versions: 4.1.0.Beta2
> Reporter: Denis Golovin
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.2.0.Alpha1
>
>
> Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI.
> This bag is regression of JBIDE-14807 where mandatory execution [Maven->Update Project...] was replaced to update only for projects with "out of date" markers. ArchetypeExamplesWizardPage.finishPage() method disable all configurators before importing projects into workspace and with fix of JBIDE-14807 it leads to new problem when configurators are never being called.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15364) CLONE - Import Maven Archetype Project Example ignores JBoss Maven Integration preferences
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15364?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-15364:
--------------------------------
Fix Version/s: 4.1.1.Final
(was: 4.2.0.Alpha1)
> CLONE - Import Maven Archetype Project Example ignores JBoss Maven Integration preferences
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-15364
> URL: https://issues.jboss.org/browse/JBIDE-15364
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, project-examples
> Affects Versions: 4.1.0.Beta2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.1.1.Final
>
>
> Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI.
> This bag is regression of JBIDE-14807 where mandatory execution [Maven->Update Project...] was replaced to update only for projects with "out of date" markers. ArchetypeExamplesWizardPage.finishPage() method disable all configurators before importing projects into workspace and with fix of JBIDE-14807 it leads to new problem when configurators are never being called.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15364) CLONE - Import Maven Archetype Project Example ignores JBoss Maven Integration preferences
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-15364:
-----------------------------------
Summary: CLONE - Import Maven Archetype Project Example ignores JBoss Maven Integration preferences
Key: JBIDE-15364
URL: https://issues.jboss.org/browse/JBIDE-15364
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven, project-examples
Affects Versions: 4.1.0.Beta2
Reporter: Fred Bricon
Assignee: Fred Bricon
Priority: Critical
Fix For: 4.2.0.Alpha1
Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI.
This bag is regression of JBIDE-14807 where mandatory execution [Maven->Update Project...] was replaced to update only for projects with "out of date" markers. ArchetypeExamplesWizardPage.finishPage() method disable all configurators before importing projects into workspace and with fix of JBIDE-14807 it leads to new problem when configurators are never being called.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15364) CLONE - Import Maven Archetype Project Example ignores JBoss Maven Integration preferences
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15364?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-15364:
--------------------------------
Description:
Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI.
This bug is regression of JBIDE-14807 where mandatory execution [Maven->Update Project...] was replaced to update only for projects with "out of date" markers. ArchetypeExamplesWizardPage.finishPage() method disable all configurators before importing projects into workspace and with fix of JBIDE-14807 it leads to new problem when configurators are never being called.
was:
Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI.
This bag is regression of JBIDE-14807 where mandatory execution [Maven->Update Project...] was replaced to update only for projects with "out of date" markers. ArchetypeExamplesWizardPage.finishPage() method disable all configurators before importing projects into workspace and with fix of JBIDE-14807 it leads to new problem when configurators are never being called.
> CLONE - Import Maven Archetype Project Example ignores JBoss Maven Integration preferences
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-15364
> URL: https://issues.jboss.org/browse/JBIDE-15364
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, project-examples
> Affects Versions: 4.1.0.Beta2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.1.1.Final
>
>
> Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI.
> This bug is regression of JBIDE-14807 where mandatory execution [Maven->Update Project...] was replaced to update only for projects with "out of date" markers. ArchetypeExamplesWizardPage.finishPage() method disable all configurators before importing projects into workspace and with fix of JBIDE-14807 it leads to new problem when configurators are never being called.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15318) Import Maven Archetype Project Example ignores JBoss Maven Integration preferences
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15318?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-15318:
-----------------------------------
Assignee: Fred Bricon
> Import Maven Archetype Project Example ignores JBoss Maven Integration preferences
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-15318
> URL: https://issues.jboss.org/browse/JBIDE-15318
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, project-examples
> Affects Versions: 4.1.0.Beta2
> Reporter: Denis Golovin
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.1.1.Final, 4.2.0.Alpha1
>
>
> Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI.
> This bag is regression of JBIDE-14807 where mandatory execution [Maven->Update Project...] was replaced to update only for projects with "out of date" markers. ArchetypeExamplesWizardPage.finishPage() method disable all configurators before importing projects into workspace and with fix of JBIDE-14807 it leads to new problem when configurators are never being called.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15151) NullPointerException reported in Eclipse Error view after using "Materialize Library..." on uninitialized classpath container
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15151?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-15151.
---------------------------------
Resolution: Done
NPE Fixed in master. An error dialog would show up if the classpath container is not initialized.
I have no idea how to reproduce the issue though.
> NullPointerException reported in Eclipse Error view after using "Materialize Library..." on uninitialized classpath container
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15151
> URL: https://issues.jboss.org/browse/JBIDE-15151
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, maven
> Reporter: Denis Golovin
> Assignee: Fred Bricon
> Fix For: 4.2.0.Alpha1
>
>
> {code}
> org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> 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:213)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
> 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:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> 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: java.lang.NullPointerException
> at org.jboss.tools.common.jdt.ui.buildpath.dialog.MaterializeLibraryDialog.<init>(MaterializeLibraryDialog.java:102)
> at org.jboss.tools.common.jdt.ui.buildpath.handlers.MaterializeLibraryHandler.execute(MaterializeLibraryHandler.java:80)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> ... 37 more{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
12 years, 7 months
[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBDS-2734:
-----------------------------------------
Summary: Forge 2 in JBDS
Key: JBDS-2734
URL: https://issues.jboss.org/browse/JBDS-2734
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Burr Sutter
Is Forge 2 ready to be included in JBDS ?
--
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
12 years, 7 months