[JBoss JIRA] (JBIDE-14807) Don't maven update the project on maven example project import, if not necessary
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14807?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-14807.
---------------------------------
Resolution: Done
Fixed in master. Creating an html5 project from central is now twice faster (from the moment you click on finish in the wizard to the moment the dialog requesting to open the readme pops up)
> Don't maven update the project on maven example project import, if not necessary
> --------------------------------------------------------------------------------
>
> Key: JBIDE-14807
> URL: https://issues.jboss.org/browse/JBIDE-14807
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven, project-examples
> Affects Versions: 4.1.0.Beta1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.1.0.Beta2
>
>
> Currently, after we import a maven project example, we run a maven update project right after, to prevent some random m2e out-of-date red markers from popping up.
> That slows imports down considerably, taking almost 50% longer to create a project from central.
> We should only trigger that project update if some "out of date" markers are actually added on the project.
--
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, 10 months
[JBoss JIRA] (JBIDE-14808) NPE when refreshing the JAX-RS UI after building a project
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14808?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-14808:
----------------------------------
Attachment: JBIDE-14808-logs.txt
Logs from Eclipse during the builds
> NPE when refreshing the JAX-RS UI after building a project
> ----------------------------------------------------------
>
> Key: JBIDE-14808
> URL: https://issues.jboss.org/browse/JBIDE-14808
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 4.1.0.Beta1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
> Attachments: JBIDE-14808-logs.txt
>
>
> Context: imported an existing html5 kitchensink project in a clean workspace. After initial import, there was no Endpoint.
> After a new build (project>build), the following error occurred:
> {code}
> !ENTRY org.jboss.tools.ws.jaxrs.core 4 0 2013-06-10 11:02:37.377
> !MESSAGE Failed to build or refresh the JAX-RS metamodel for projet jboss-html5-webapp
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.ui.cnf.UriMappingsContentProvider.refreshContent(UriMappingsContentProvider.java:194)
> at org.jboss.tools.ws.jaxrs.ui.cnf.UriMappingsContentProvider.notifyEndpointChanged(UriMappingsContentProvider.java:156)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.notifyListeners(JaxrsMetamodel.java:356)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.update(JaxrsMetamodel.java:737)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsEndpoint.update(JaxrsEndpoint.java:166)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processAddition(JaxrsElementChangedProcessorDelegate.java:112)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processEvent(JaxrsElementChangedProcessorDelegate.java:48)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processElementChange(JaxrsMetamodel.java:706)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.add(JaxrsMetamodel.java:693)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsBaseElement.joinMetamodel(JaxrsBaseElement.java:86)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsJavaApplication$Builder.build(JaxrsJavaApplication.java:124)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:167)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:64)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processResourceChange(JaxrsMetamodel.java:619)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processProject(JaxrsMetamodel.java:553)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:67){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, 10 months
[JBoss JIRA] (JBIDE-14808) NPE when refreshing the JAX-RS UI after building a project
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-14808:
-------------------------------------
Summary: NPE when refreshing the JAX-RS UI after building a project
Key: JBIDE-14808
URL: https://issues.jboss.org/browse/JBIDE-14808
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 4.1.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Priority: Critical
Fix For: 4.1.0.Beta2
Context: imported an existing html5 kitchensink project in a clean workspace. After initial import, there was no Endpoint.
After a new build (project>build), the following error occurred:
{code}
!ENTRY org.jboss.tools.ws.jaxrs.core 4 0 2013-06-10 11:02:37.377
!MESSAGE Failed to build or refresh the JAX-RS metamodel for projet jboss-html5-webapp
!STACK 0
java.lang.NullPointerException
at org.jboss.tools.ws.jaxrs.ui.cnf.UriMappingsContentProvider.refreshContent(UriMappingsContentProvider.java:194)
at org.jboss.tools.ws.jaxrs.ui.cnf.UriMappingsContentProvider.notifyEndpointChanged(UriMappingsContentProvider.java:156)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.notifyListeners(JaxrsMetamodel.java:356)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.update(JaxrsMetamodel.java:737)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsEndpoint.update(JaxrsEndpoint.java:166)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processAddition(JaxrsElementChangedProcessorDelegate.java:112)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processEvent(JaxrsElementChangedProcessorDelegate.java:48)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processElementChange(JaxrsMetamodel.java:706)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.add(JaxrsMetamodel.java:693)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsBaseElement.joinMetamodel(JaxrsBaseElement.java:86)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsJavaApplication$Builder.build(JaxrsJavaApplication.java:124)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:167)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:64)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processResourceChange(JaxrsMetamodel.java:619)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processProject(JaxrsMetamodel.java:553)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:67){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, 10 months
[JBoss JIRA] (JBIDE-13987) Improve project wizards in JBoss Central : Proxy Wizards
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13987?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-13987:
------------------------------------
I'm trying this on JBT. Will try on JBDS today.
> Improve project wizards in JBoss Central : Proxy Wizards
> --------------------------------------------------------
>
> Key: JBIDE-13987
> URL: https://issues.jboss.org/browse/JBIDE-13987
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Max Rydahl Andersen
> Labels: new_and_noteworthy, respin-b
> Fix For: 4.1.0.Beta1
>
> Attachments: www.tar.gz
>
>
> The "Start from scratch" section (formerly known as Project section) in JBoss Central needs to support the following requirements :
> - wizard list (label/order/description) must be updateable remotely
> - show wizards (including the proper icon) even if their contributing plugins are missing
> - when clicking on the wizard link in JBoss Central, if the wizard is available then open it, else, install the required plugins
> The general idea here is to use some kind of proxy wizard. A proxy wizard model should have the following attributes :
> - id : the proxy wizard id
> - label : the proxy wizard label shown in JBoss Central
> - wizardId : the real wizard id used by Central to open the wizard dialog
> - iconPath : the path to the wizard icon (independent of required connector)
> - description : the description shown in Central when hovering over the wizard link
> - requiredConnectorIds : the connector ids to install if the real wizard is not available
> - priority : order in which the wizard is displayed in JBoss Central
> The proxy wizards will be declared in the jboss-discovery.jar plugin.xml (to minimize build / maintenance overhead). The jar will also include the required icons.
> The jar will be fetched remotely by the discovery mechanism but a cached version must be kept for offline usage.
--
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, 10 months
[JBoss JIRA] (JBIDE-14790) Unable to create Seam Web Project
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14790?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-14790:
------------------------------------
I'm experiencing this on instance of JBT 4.1.0.Beta1 installed from eclipse marketplace to eclipse 4.3.M7
I tried today fresh instance of JBT 4.1.0.Beta1 installed from marketplace, but I'm unable to reproduce this issue there.
I must have updated that eclipse from somewhere. Here is diff of features:
{noformat}
$ diff temp/broken temp/ok
5,6c5,6
< org.eclipse.datatools.connectivity.feature (1.11.0.v201302211047-7C7k98Et1byqRCfljSoSHcUXJ3K) "Data Tools Platform Connectivity Plug-in"
< org.eclipse.datatools.connectivity.oda.designer.core.feature (1.11.0.v201302211047-7B7C7UCcNBGWEXDhDbYg) "DTP ODA Designer UI Framework Plug-in"
---
> org.eclipse.datatools.connectivity.feature (1.11.0.v201302211047-7C7k97Et1bxqU9criVj_D_bWEuR) "Data Tools Platform Connectivity Plug-in"
> org.eclipse.datatools.connectivity.oda.designer.core.feature (1.11.0.v201302211047-7B7C7UCcNBGWEVDkCf_g) "DTP ODA Designer UI Framework Plug-in"
8c8
< org.eclipse.datatools.connectivity.oda.feature (1.11.0.v201302211047-7H7D7WCcNBHRCfIfDfUc) "DTP Open Data Access"
---
> org.eclipse.datatools.connectivity.oda.feature (1.11.0.v201302211047-7H7C7ZCcNBHPCdFkDYHj) "DTP Open Data Access"
29c29
< org.eclipse.datatools.sqldevtools.feature (1.11.0.v201302211047-7N8I7IFDri5nhCyg6O46XaTte7m0) "Eclipse Data Tools Platform SQL Tools Common UI Plug-in"
---
> org.eclipse.datatools.sqldevtools.feature (1.11.0.v201302211047-7N8I7IFDri5mhCyg6O43UgSwbFm0) "Eclipse Data Tools Platform SQL Tools Common UI Plug-in"
35,53c35,53
< org.eclipse.emf (2.9.0.v20130603-0742) "EMF - Eclipse Modeling Framework Runtime and Tools"
< org.eclipse.emf.codegen (2.9.0.v20130603-0742) "EMF Code Generation"
< org.eclipse.emf.codegen.ecore (2.9.0.v20130603-0742) "EMF Ecore Code Generator"
< org.eclipse.emf.codegen.ecore.ui (2.9.0.v20130603-0742) "EMF Ecore Code Generator UI"
< org.eclipse.emf.codegen.ui (2.7.0.v20130603-0742) "EMF Code Generation UI"
< org.eclipse.emf.common (2.9.0.v20130528-0742) "EMF Common"
< org.eclipse.emf.common.ui (2.8.0.v20130603-0742) "EMF Common UI"
< org.eclipse.emf.converter (2.9.0.v20130603-0742) "EMF Model Converter"
< org.eclipse.emf.databinding (1.3.0.v20130603-0742) "EMF Data Binding"
< org.eclipse.emf.databinding.edit (1.3.0.v20130603-0742) "EMF Edit Data Binding"
< org.eclipse.emf.ecore (2.9.0.v20130528-0742) "EMF Ecore"
< org.eclipse.emf.ecore.edit (2.8.0.v20130603-0742) "EMF Ecore Edit"
< org.eclipse.emf.ecore.editor (2.9.0.v20130603-0742) "EMF Sample Ecore Editor"
< org.eclipse.emf.edit (2.9.0.v20130603-0742) "EMF Edit"
< org.eclipse.emf.edit.ui (2.9.0.v20130603-0742) "EMF Edit UI"
< org.eclipse.emf.mapping (2.7.0.v20130603-0742) "EMF Mapping"
< org.eclipse.emf.mapping.ecore (2.7.0.v20130603-0742) "EMF Ecore Mapping"
< org.eclipse.emf.mapping.ecore.editor (2.8.0.v20130603-0742) "EMF Ecore Mapping Editor"
< org.eclipse.emf.mapping.ui (2.7.0.v20130603-0742) "EMF Mapping UI"
---
> org.eclipse.emf (2.9.0.v20130506-0438) "EMF - Eclipse Modeling Framework Runtime and Tools"
> org.eclipse.emf.codegen (2.9.0.v20130506-0438) "EMF Code Generation"
> org.eclipse.emf.codegen.ecore (2.9.0.v20130506-0438) "EMF Ecore Code Generator"
> org.eclipse.emf.codegen.ecore.ui (2.9.0.v20130506-0438) "EMF Ecore Code Generator UI"
> org.eclipse.emf.codegen.ui (2.7.0.v20130506-0438) "EMF Code Generation UI"
> org.eclipse.emf.common (2.9.0.v20130430-1108) "EMF Common"
> org.eclipse.emf.common.ui (2.8.0.v20130506-0438) "EMF Common UI"
> org.eclipse.emf.converter (2.9.0.v20130506-0438) "EMF Model Converter"
> org.eclipse.emf.databinding (1.3.0.v20130506-0438) "EMF Data Binding"
> org.eclipse.emf.databinding.edit (1.3.0.v20130506-0438) "EMF Edit Data Binding"
> org.eclipse.emf.ecore (2.9.0.v20130430-1108) "EMF Ecore"
> org.eclipse.emf.ecore.edit (2.8.0.v20130506-0438) "EMF Ecore Edit"
> org.eclipse.emf.ecore.editor (2.9.0.v20130506-0438) "EMF Sample Ecore Editor"
> org.eclipse.emf.edit (2.9.0.v20130506-0438) "EMF Edit"
> org.eclipse.emf.edit.ui (2.9.0.v20130506-0438) "EMF Edit UI"
> org.eclipse.emf.mapping (2.7.0.v20130506-0438) "EMF Mapping"
> org.eclipse.emf.mapping.ecore (2.7.0.v20130506-0438) "EMF Ecore Mapping"
> org.eclipse.emf.mapping.ecore.editor (2.8.0.v20130506-0438) "EMF Ecore Mapping Editor"
> org.eclipse.emf.mapping.ui (2.7.0.v20130506-0438) "EMF Mapping UI"
58c58
< org.eclipse.jdt (3.9.0.v20130530-1629) "Eclipse Java Development Tools"
---
> org.eclipse.jdt (3.9.0.v20130502-0800) "Eclipse Java Development Tools"
61c61
< org.eclipse.jpt.common.feature (1.3.0.v201210121950-67A-AkF7BI7UCR9SIV) "Dali Java Persistence Tools - Common"
---
> org.eclipse.jpt.common.feature (1.3.0.v201210121950-67A-AkF7BI7SEL9HJU) "Dali Java Persistence Tools - Common"
66c66
< org.eclipse.jpt.jpa.feature (3.3.0.v201305142100-7V7_0FC7sRe5TNiKb1Vrdd3c) "Dali Java Persistence Tools - JPA Support"
---
> org.eclipse.jpt.jpa.feature (3.3.0.v201304302343-7X7e0FD3wTh7VRjZ_7-SIF39) "Dali Java Persistence Tools - JPA Support"
72c72
< org.eclipse.m2e.feature (1.4.0.20130601-0317) "Maven Integration for Eclipse"
---
> org.eclipse.m2e.feature (1.4.0.20130318-1103) "Maven Integration for Eclipse"
94,101c94,101
< org.eclipse.rse (3.5.0.201305311734) "Remote System Explorer End-User Runtime"
< org.eclipse.rse.core (3.4.100.201305201712) "RSE Core"
< org.eclipse.rse.dstore (3.4.100.201305311734) "RSE DStore Services"
< org.eclipse.rse.ftp (3.2.0.201305152119) "RSE FTP Service"
< org.eclipse.rse.local (2.1.500.201305211438) "RSE Local Services"
< org.eclipse.rse.ssh (3.0.500.201305201712) "RSE SSH Services"
< org.eclipse.rse.telnet (2.3.100.201305201712) "RSE Telnet Service"
< org.eclipse.rse.terminals (1.2.100.201305201712) "RSE Terminals UI"
---
> org.eclipse.rse (3.4.1.201305031537) "Remote System Explorer End-User Runtime"
> org.eclipse.rse.core (3.4.1.201305031537) "RSE Core"
> org.eclipse.rse.dstore (3.4.1.201305031537) "RSE DStore Services"
> org.eclipse.rse.ftp (3.1.0.201302062102) "RSE FTP Service"
> org.eclipse.rse.local (2.1.400.201302062104) "RSE Local Services"
> org.eclipse.rse.ssh (3.0.400.201205062159) "RSE SSH Services"
> org.eclipse.rse.telnet (2.3.0.201205241511) "RSE Telnet Service"
> org.eclipse.rse.terminals (1.2.1.201305031537) "RSE Terminals UI"
103c103
< org.eclipse.tm.terminal (3.2.100.201305201712) "Target Management Terminal Widget"
---
> org.eclipse.tm.terminal (3.2.2.201305031537) "Target Management Terminal Widget"
109,110c109,110
< org.eclipse.wst.web_ui.feature (3.5.0.v201209252144-7O7QG-6EMkBQ3BbbkeW0v80T4Kg8QYEUELicbYyf) "Eclipse Web Developer Tools"
< org.eclipse.wst.xml_ui.feature (3.5.0.v201301022000-7H7IFisDxumVt037ridXmVSgs8DdRZKtSyS6PL) "Eclipse XML Editors and Tools"
---
> org.eclipse.wst.web_ui.feature (3.5.0.v201209252144-7O7QG-6EMkBQ3A-bjcZ0x5QBPrhj48Zz-Bojv422) "Eclipse Web Developer Tools"
> org.eclipse.wst.xml_ui.feature (3.5.0.v201301022000-7H7IFisDxumVt037ridXmTt0LZaO8hpKrQxT5SU) "Eclipse XML Editors and Tools"
{noformat}
If you don't want to investigate this issue, resolve as Cannot reproduce. I'm ok with that, because my installation is obviously incorrect.
If you want more info just ask ;-)
> Unable to create Seam Web Project
> ---------------------------------
>
> Key: JBIDE-14790
> URL: https://issues.jboss.org/browse/JBIDE-14790
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam 2
> Affects Versions: 4.1.0.Beta1
> Environment: JBT 4.1.0.Beta1 installed from eclipse marketplace
> Reporter: Radim Hopp
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Beta2
>
>
> I'm unable to create Seam Web Project (File->New->Other->Seam->Seam Web Project)
> This exception appears immediately, when New Seam Project wizard is shown:
> {noformat}
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoClassDefFoundError: Could not initialize class org.jboss.tools.seam.ui.internal.project.facet.SeamInstallWizardPage)
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:259)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:85)
> 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)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:231)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:212)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:165)
> 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.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
> 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:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1109)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> 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.NoClassDefFoundError: Could not initialize class org.jboss.tools.seam.ui.internal.project.facet.SeamInstallWizardPage
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
> at java.lang.Class.newInstance0(Class.java:374)
> at java.lang.Class.newInstance(Class.java:327)
> at org.eclipse.wst.common.project.facet.ui.internal.ProjectFacetsUiManagerImpl.create(ProjectFacetsUiManagerImpl.java:170)
> at org.eclipse.wst.common.project.facet.ui.internal.ProjectFacetsUiManagerImpl.getWizardPages(ProjectFacetsUiManagerImpl.java:148)
> at org.eclipse.wst.common.project.facet.ui.internal.ProjectFacetsUiManagerImpl.getWizardPages(ProjectFacetsUiManagerImpl.java:108)
> at org.eclipse.wst.common.project.facet.ui.ProjectFacetsUiManager.getWizardPages(ProjectFacetsUiManager.java:30)
> at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.handleSelectedFacetsChangedEvent(ModifyFacetedProjectWizard.java:712)
> at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.access$0(ModifyFacetedProjectWizard.java:670)
> at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$1$1.run(ModifyFacetedProjectWizard.java:166)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 51 more
> {noformat}
> And this one when clicking on Finish button:
> {noformat}
> java.lang.NullPointerException
> at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.performFinish(SeamProjectWizard.java:340)
> 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:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:259)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:85)
> 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)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:231)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:212)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:165)
> 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.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
> 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:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1109)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> 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)
> {noformat}
--
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, 10 months
[JBoss JIRA] (JBDS-1234) Installer could check OS architecture
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-1234:
--------------------------------------
[~dgolovin]: It seems to me that newer versions of installer are multiplatform and install the right platform on the right OS. If so, can we close this issue?
> Installer could check OS architecture
> -------------------------------------
>
> Key: JBDS-1234
> URL: https://issues.jboss.org/browse/JBDS-1234
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 3.0.1.GA
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Fix For: LATER
>
>
> Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation.
--
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, 10 months
[JBoss JIRA] (JBDS-1608) Feature set selection during installation
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-1608?page=com.atlassian.jira.plugin.... ]
Mickael Istria updated JBDS-1608:
---------------------------------
Priority: Minor (was: Major)
Reducing priority has I haven't heard about it for the last 15 monthes.
> Feature set selection during installation
> -----------------------------------------
>
> Key: JBDS-1608
> URL: https://issues.jboss.org/browse/JBDS-1608
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 4.0.0.GA
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: LATER
>
>
> There are many wishes to make JBDS more modular so one way would be to allow feature selection during installation known from othere application where you can select what features/plugins should be installed during installation process and according to user selection final installation is done.
--
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, 10 months
[JBoss JIRA] (JBDS-1574) What's up with the "ISO downloads" of JBDS PE 2.x and 3.x?
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-1574?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-1574:
--------------------------------------
[~myarboro] [~maxandersen]: Is this ticket still relevant? Can we close it?
> What's up with the "ISO downloads" of JBDS PE 2.x and 3.x?
> ----------------------------------------------------------
>
> Key: JBDS-1574
> URL: https://issues.jboss.org/browse/JBDS-1574
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Reporter: Nick Boldt
> Assignee: mark yarborough
> Fix For: 5.x, LATER
>
> Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot.png, software_downloads_rhn.png
>
>
> Found some interestingly described JBDS 3.0 and earlier downloads in the CSP.
> Steps to repro:
> 1. Log in here: https://www.redhat.com/wapps/sso/login.html
> 2. Click "Red Hat Network Preferences" -> https://rhn.redhat.com/network/my_account/my_prefs.pxt
> 3. Click the "Download software" icon/button on the left-hand side of the site:
> !software_downloads_rhn.png!
> 4. Observe list of downloads - CTRL-F to search for Developer Studio
> https://rhn.redhat.com/rhn/software/downloads/SupportedISOs.do
> !Screenshot-1.png!
> 5. Click on one of the entries, such as "JBoss Developer Studio - Portfolio Edition for Linux ", and get here:
> https://rhn.redhat.com/rhn/software/channel/downloads/Download.do?cid=9103
> "ISO Image Downloads
> NOTE: By downloading this software, you agree to the terms and conditions of the applicable License Agreement (available at http://www.redhat.com/licenses/)
> Not sure how to download and use these images? Check out our ISO Download Help.
> Latest Release
> Below please find the complete set of ISO images for the latest release of JBoss Developer Studio - Portfolio Edition for Linux. Depending on the variant of JBoss Developer Studio - Portfolio Edition for Linux you'd like to install, you may only need a subset of these discs. (more information) "
> !Screenshot-2.png!
> 6. Have a WTF moment as you consider how a jarred installer can be classified as an ISO image.
--
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, 10 months
[JBoss JIRA] (JBIDE-13372) improve usability of jiralint emails
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13372?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-13372:
-----------------------------------
Priority: Minor (was: Major)
> improve usability of jiralint emails
> ------------------------------------
>
> Key: JBIDE-13372
> URL: https://issues.jboss.org/browse/JBIDE-13372
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Priority: Minor
> Fix For: 4.1.x
>
>
> Could these be reformatted to list the names of the offenders at the top of the email, so we don't have to waste time scanning to see whose name is associated w/ the incorrectly versioned jiras?
> Better, can they simply be sent to the people who've set bad fixVersions, rather than the whole list? The only person who needs to see the email below is Snjezana.
> {code}
> -------- Original Message --------
> Subject: Weekly jira sanity check - jbosstools-jiralint - Build # 138 - Still Unstable!
> Date: Sun, 13 Jan 2013 00:01:28 -0500 (EST)
> From: ci-builds(a)redhat.com
> To: external-exadel-list(a)redhat.com
> This is the weekly check for jira problems.
> Please fix the issues outlined below if there are any. Thank you!
> jbosstools-jiralint - Build # 138 - Still Unstable:
> Check console output at http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint/138/ to view the results.
> 1 tests 1 failure(s) / -2
> 1 tests failed.
> FAILED: ToolsIllegalFixVersion.ToolsIllegalFixVersion.JBIDE-13332_snjeza
> Error Message:
> https://jira.jboss.org/browse/JBIDE-13332 (last update: 22 days, 10:21:51.551414) -> Issue have been resolved with an illegal fix version, i.e. an .x version, LATER or no fix version at all. This means it will not be shown in the right release notes so neither developers or users can see where things happend. Please adjust the issue so it correctly states the proper fix version! Thank you! See http://bit.ly/aTUeGq for how to track down right fix versions.
> Stack Trace:
> JBIDE-13332: Update list of quickstarts to be consistent with current goals(https://jira.jboss.org/browse/JBIDE-13332)
>
> {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, 10 months
[JBoss JIRA] (JBIDE-2805) Ease uninstall/update operations through Eclipse update framework
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2805?page=com.atlassian.jira.plugin... ]
Mickael Istria commented on JBIDE-2805:
---------------------------------------
[~maxandersen] This looks quite old and seems fine in newer JBT version. Can we close this ticket?
> Ease uninstall/update operations through Eclipse update framework
> -----------------------------------------------------------------
>
> Key: JBIDE-2805
> URL: https://issues.jboss.org/browse/JBIDE-2805
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng
> Affects Versions: 3.0.0.alpha
> Reporter: Denis Golovin
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: LATER
>
> Attachments: JBossToolsFeatures.png
>
>
> Now we have several features (see attached pictures). There is no common prefix for them and that doesn't help to ease update/uninstall. Now they are
> scattered between installed items and it is difficult to find them in Installed Software list.
> So my proposition is to have prefix JBT or JBoss Tools for all features to keep them together in Installed Software list. Another solution is to have pattern for feature names, for instance, JBoss <component name> Tools, so list would look like:
> JBoss ESB Tools
> JBoss Seam Tools
> JBoss Protlet Tools
> JBoss Struts Tools
> JBoss ReachFaces Tools
> JBoss WS Tools
> JBoss Hibernate Console
> JBoss AS Tools
> e.t.c.
--
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, 10 months