[JBoss JIRA] (JBIDE-19603) NPE in openshift application wizard after several attempts to remember credentials
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19603?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-19603 at 4/16/15 8:31 AM:
-------------------------------------------------------------------
[~dgolovin] I guess that you were trying to import an existing application, right? Can you please tell me when exactly the NPE occurred? If your password is wrong you shouldnt get past the 1st wizard page with the credentials? In an ideal world steps to reproduce this would help.
was (Author: adietish):
[~dgolovin] I guess that you were trying to import an existing application, right? Can you please tell me when exactly the NPE occurred? If your password is wrong you shouldnt get past the 1st wizard page with the credentials?
> NPE in openshift application wizard after several attempts to remember credentials
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-19603
> URL: https://issues.jboss.org/browse/JBIDE-19603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Environment: Linux
> Reporter: Denis Golovin
> Assignee: Andre Dietisheim
>
> I was trying to recover my password with try and fail method and finally succeeded to recover it but next step I got NPE's after pushing Browse button.
> Authorization error was:
> {code}com.openshift.client.InvalidCredentialsOpenShiftException: Your credentials are not authorized to access "https://openshift.redhat.com/broker/rest/user"
> at com.openshift.internal.client.RestService.request(RestService.java:114)
> at com.openshift.internal.client.RestService.request(RestService.java:92)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:143)
> at com.openshift.internal.client.APIResource$GetUserRequest.execute(APIResource.java:400)
> at com.openshift.internal.client.APIResource.getUser(APIResource.java:101)
> at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.doCreateUser(ExpressConnection.java:221)
> at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.createUser(ExpressConnection.java:206)
> at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.connect(ExpressConnection.java:183)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:316)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:459)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.openshift.internal.client.httpclient.UnauthorizedException: HTTP Basic: Access denied.
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:165)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:144)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:103)
> at com.openshift.internal.client.RestService.request(RestService.java:160)
> at com.openshift.internal.client.RestService.request(RestService.java:107)
> ... 11 more
> Caused by: java.io.IOException: Server returned HTTP response code: 401 for URL: https://openshift.redhat.com/broker/rest/user
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1627)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:161)
> ... 15 more{code}
> and then NPE:
> {code}java.lang.NullPointerException
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.loadDomains(SelectApplicationWizardPageModel.java:71)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.loadOpenShiftResources(SelectApplicationWizardPageModel.java:67)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPage.onPageActivated(SelectApplicationWizardPage.java:135)
> at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$1.pageChanged(AbstractOpenShiftWizardPage.java:87)
> at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1505)
> 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.wizard.WizardDialog.firePageChanged(WizardDialog.java:1502)
> at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1308)
> at org.eclipse.jface.wizard.WizardDialog.showStartingPage(WizardDialog.java:1258)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:599)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.eclipse.jface.window.Window.open(Window.java:792)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.ApplicationTemplateWizardPage$2.widgetSelected(ApplicationTemplateWizardPage.java:237)
> 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:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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:152)
> 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:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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}
> and then one more NPE:
> {code}java.lang.NullPointerException
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.refreshDomains(SelectApplicationWizardPageModel.java:49)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.refresh(SelectApplicationWizardPageModel.java:44)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPage$2$1.run(SelectApplicationWizardPage.java:148)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}
> Then I pushed Back and Next and was able to see cartridges and browse my old applications.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19603) NPE in openshift application wizard after several attempts to remember credentials
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19603?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19603:
------------------------------------------
[~dgolovin] I guess that you were trying to import an existing application, right? Can you please tell me when exactly the NPE occurred? If your password is wrong you shouldnt get past the 1st wizard page with the credentials?
> NPE in openshift application wizard after several attempts to remember credentials
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-19603
> URL: https://issues.jboss.org/browse/JBIDE-19603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Environment: Linux
> Reporter: Denis Golovin
> Assignee: Andre Dietisheim
>
> I was trying to recover my password with try and fail method and finally succeeded to recover it but next step I got NPE's after pushing Browse button.
> Authorization error was:
> {code}com.openshift.client.InvalidCredentialsOpenShiftException: Your credentials are not authorized to access "https://openshift.redhat.com/broker/rest/user"
> at com.openshift.internal.client.RestService.request(RestService.java:114)
> at com.openshift.internal.client.RestService.request(RestService.java:92)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:143)
> at com.openshift.internal.client.APIResource$GetUserRequest.execute(APIResource.java:400)
> at com.openshift.internal.client.APIResource.getUser(APIResource.java:101)
> at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.doCreateUser(ExpressConnection.java:221)
> at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.createUser(ExpressConnection.java:206)
> at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.connect(ExpressConnection.java:183)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:316)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:459)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.openshift.internal.client.httpclient.UnauthorizedException: HTTP Basic: Access denied.
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:165)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:144)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:103)
> at com.openshift.internal.client.RestService.request(RestService.java:160)
> at com.openshift.internal.client.RestService.request(RestService.java:107)
> ... 11 more
> Caused by: java.io.IOException: Server returned HTTP response code: 401 for URL: https://openshift.redhat.com/broker/rest/user
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1627)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:161)
> ... 15 more{code}
> and then NPE:
> {code}java.lang.NullPointerException
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.loadDomains(SelectApplicationWizardPageModel.java:71)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.loadOpenShiftResources(SelectApplicationWizardPageModel.java:67)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPage.onPageActivated(SelectApplicationWizardPage.java:135)
> at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$1.pageChanged(AbstractOpenShiftWizardPage.java:87)
> at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1505)
> 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.wizard.WizardDialog.firePageChanged(WizardDialog.java:1502)
> at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1308)
> at org.eclipse.jface.wizard.WizardDialog.showStartingPage(WizardDialog.java:1258)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:599)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.eclipse.jface.window.Window.open(Window.java:792)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.ApplicationTemplateWizardPage$2.widgetSelected(ApplicationTemplateWizardPage.java:237)
> 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:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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:152)
> 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:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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}
> and then one more NPE:
> {code}java.lang.NullPointerException
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.refreshDomains(SelectApplicationWizardPageModel.java:49)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.refresh(SelectApplicationWizardPageModel.java:44)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPage$2$1.run(SelectApplicationWizardPage.java:148)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}
> Then I pushed Back and Next and was able to see cartridges and browse my old applications.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19603) NPE in openshift application wizard after several attempts to remember credentials
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19603?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-19603:
----------------------------------------
Assignee: Andre Dietisheim
> NPE in openshift application wizard after several attempts to remember credentials
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-19603
> URL: https://issues.jboss.org/browse/JBIDE-19603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Environment: Linux
> Reporter: Denis Golovin
> Assignee: Andre Dietisheim
>
> I was trying to recover my password with try and fail method and finally succeeded to recover it but next step I got NPE's after pushing Browse button.
> Authorization error was:
> {code}com.openshift.client.InvalidCredentialsOpenShiftException: Your credentials are not authorized to access "https://openshift.redhat.com/broker/rest/user"
> at com.openshift.internal.client.RestService.request(RestService.java:114)
> at com.openshift.internal.client.RestService.request(RestService.java:92)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:143)
> at com.openshift.internal.client.APIResource$GetUserRequest.execute(APIResource.java:400)
> at com.openshift.internal.client.APIResource.getUser(APIResource.java:101)
> at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.doCreateUser(ExpressConnection.java:221)
> at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.createUser(ExpressConnection.java:206)
> at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.connect(ExpressConnection.java:183)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:316)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:459)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.openshift.internal.client.httpclient.UnauthorizedException: HTTP Basic: Access denied.
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:165)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:144)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:103)
> at com.openshift.internal.client.RestService.request(RestService.java:160)
> at com.openshift.internal.client.RestService.request(RestService.java:107)
> ... 11 more
> Caused by: java.io.IOException: Server returned HTTP response code: 401 for URL: https://openshift.redhat.com/broker/rest/user
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1627)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:161)
> ... 15 more{code}
> and then NPE:
> {code}java.lang.NullPointerException
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.loadDomains(SelectApplicationWizardPageModel.java:71)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.loadOpenShiftResources(SelectApplicationWizardPageModel.java:67)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPage.onPageActivated(SelectApplicationWizardPage.java:135)
> at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$1.pageChanged(AbstractOpenShiftWizardPage.java:87)
> at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1505)
> 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.wizard.WizardDialog.firePageChanged(WizardDialog.java:1502)
> at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1308)
> at org.eclipse.jface.wizard.WizardDialog.showStartingPage(WizardDialog.java:1258)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:599)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.eclipse.jface.window.Window.open(Window.java:792)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.ApplicationTemplateWizardPage$2.widgetSelected(ApplicationTemplateWizardPage.java:237)
> 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:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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:152)
> 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:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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}
> and then one more NPE:
> {code}java.lang.NullPointerException
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.refreshDomains(SelectApplicationWizardPageModel.java:49)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.refresh(SelectApplicationWizardPageModel.java:44)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPage$2$1.run(SelectApplicationWizardPage.java:148)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}
> Then I pushed Back and Next and was able to see cartridges and browse my old applications.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19427) Redundant warning for JPA entity
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19427?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-19427:
------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Redundant warning for JPA entity
> --------------------------------
>
> Key: JBIDE-19427
> URL: https://issues.jboss.org/browse/JBIDE-19427
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Alpha2
> Reporter: Arun Gupta
> Assignee: Koen Aers
> Fix For: 4.3.0.Beta1
>
> Attachments: Screen Shot 2015-03-10 at 2.39.46 PM.png
>
>
> Student entity is defined as:
> {code}
> @Entity
> @XmlRootElement
> @NamedQuery(name="findAllStudents", query="select s from Student s")
> public class Student implements Serializable {
> {code}
> Persistence.xml is defined as:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <persistence version="2.1"
> xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd">
> <persistence-unit name="HelloJavaEE7">
> <properties>
> <property name="javax.persistence.schema-generation.database.action"
> value="drop-and-create" />
> <property name="javax.persistence.schema-generation.create-source"
> value="metadata" />
> <property name="javax.persistence.schema-generation.drop-source"
> value="metadata" />
> <property name="hibernate.show_sql" value="true" />
> <property name="hibernate.format_sql" value="true" />
> </properties>
> </persistence-unit>
> </persistence>
> {code}
> Editor shows a red cross on Student class declaration with the error message "Class "org.sample.Student" is managed, but is not listed in the persistence.xml file".
> By default, all entities are included and this error should not occur.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19443) java.lang.NoClassDefFoundError in Reveng editor when using Hibernate 3.6
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19443?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-19443:
------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> java.lang.NoClassDefFoundError in Reveng editor when using Hibernate 3.6
> ------------------------------------------------------------------------
>
> Key: JBIDE-19443
> URL: https://issues.jboss.org/browse/JBIDE-19443
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.3.Beta1
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
>
> java.lang.NoClassDefFoundError: Could not initialize class org.hibernate.cfg.reveng.OverrideRepository
> at org.jboss.tools.hibernate.proxy.ServiceProxy.newOverrideRepository(ServiceProxy.java:198)
> at org.hibernate.eclipse.mapper.editors.ReverseEngineeringEditor.getLazyDatabaseSchema(ReverseEngineeringEditor.java:207)
> at org.hibernate.eclipse.mapper.editors.reveng.TablePropertiesBlock.doAdd(TablePropertiesBlock.java:172)
> at org.hibernate.eclipse.mapper.editors.reveng.TablePropertiesBlock$1.widgetSelected(TablePropertiesBlock.java:128)
> 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:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> 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.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
> 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)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19606) Hibernate XML file is empty after creating
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19606?page=com.atlassian.jira.plugi... ]
Jiri Peterka commented on JBIDE-19606:
--------------------------------------
Bunch of exception is present after creating the file
{code}
!ENTRY org.jboss.tools.hibernate.runtime.common 4 0 2015-04-16 13:55:50.582
!MESSAGE org.hibernate.tool.hbm2x.HibernateConfigurationExporter.setOutput(java.io.StringWriter)
!STACK 0
java.lang.NoSuchMethodException: org.hibernate.tool.hbm2x.HibernateConfigurationExporter.setOutput(java.io.StringWriter)
at java.lang.Class.getMethod(Class.java:1773)
at org.jboss.tools.hibernate.runtime.common.Util.invokeMethod(Util.java:39)
at org.jboss.tools.hibernate.runtime.common.AbstractExporterFacade.setOutput(AbstractExporterFacade.java:194)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.openContentStream(NewConfigurationWizard.java:301)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.access$2(NewConfigurationWizard.java:294)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard$1.getInitialContents(NewConfigurationWizard.java:163)
at org.eclipse.ui.dialogs.WizardNewFileCreationPage.createNewFile(WizardNewFileCreationPage.java:387)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.performFinish(NewConfigurationWizard.java:197)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
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:4477)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
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:152)
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.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:286)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:507)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:558)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:378)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:324)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:86)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1571)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1321)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1346)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1331)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1358)
at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:758)
at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3309)
at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:780)
at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2020)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:5541)
at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:3559)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4707)
at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9241)
at org.eclipse.swt.widgets.Display.eventProc(Display.java:1250)
at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2421)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3423)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
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)
!ENTRY org.jboss.tools.hibernate.runtime.common 4 0 2015-04-16 13:55:50.586
!MESSAGE
!STACK 0
java.lang.reflect.InvocationTargetException
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.jboss.tools.hibernate.runtime.common.Util.invokeMethod(Util.java:41)
at org.jboss.tools.hibernate.runtime.common.AbstractExporterFacade.start(AbstractExporterFacade.java:96)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.openContentStream(NewConfigurationWizard.java:302)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.access$2(NewConfigurationWizard.java:294)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard$1.getInitialContents(NewConfigurationWizard.java:163)
at org.eclipse.ui.dialogs.WizardNewFileCreationPage.createNewFile(WizardNewFileCreationPage.java:387)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.performFinish(NewConfigurationWizard.java:197)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
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:4477)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
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:152)
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.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:286)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:507)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:558)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:378)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:324)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:86)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1571)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1321)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1346)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1331)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1358)
at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:758)
at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3309)
at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:780)
at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2020)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:5541)
at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:3559)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4707)
at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9241)
at org.eclipse.swt.widgets.Display.eventProc(Display.java:1250)
at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2421)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3423)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
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)
Caused by: java.lang.NullPointerException
at org.hibernate.tool.hbm2x.XMLPrettyPrinter.prettyPrintFile(XMLPrettyPrinter.java:95)
at org.hibernate.tool.hbm2x.ArtifactCollector.formatXml(ArtifactCollector.java:69)
at org.hibernate.tool.hbm2x.ArtifactCollector.formatFiles(ArtifactCollector.java:59)
at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:98)
... 86 more
Root exception:
java.lang.NullPointerException
at org.hibernate.tool.hbm2x.XMLPrettyPrinter.prettyPrintFile(XMLPrettyPrinter.java:95)
at org.hibernate.tool.hbm2x.ArtifactCollector.formatXml(ArtifactCollector.java:69)
at org.hibernate.tool.hbm2x.ArtifactCollector.formatFiles(ArtifactCollector.java:59)
at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:98)
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.jboss.tools.hibernate.runtime.common.Util.invokeMethod(Util.java:41)
at org.jboss.tools.hibernate.runtime.common.AbstractExporterFacade.start(AbstractExporterFacade.java:96)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.openContentStream(NewConfigurationWizard.java:302)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.access$2(NewConfigurationWizard.java:294)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard$1.getInitialContents(NewConfigurationWizard.java:163)
at org.eclipse.ui.dialogs.WizardNewFileCreationPage.createNewFile(WizardNewFileCreationPage.java:387)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.performFinish(NewConfigurationWizard.java:197)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
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:4477)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
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:152)
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.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:286)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:507)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:558)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:378)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:324)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:86)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1571)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1321)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1346)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1331)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1358)
at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:758)
at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3309)
at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:780)
at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2020)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:5541)
at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:3559)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4707)
at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9241)
at org.eclipse.swt.widgets.Display.eventProc(Display.java:1250)
at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2421)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3423)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
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)
!ENTRY org.jboss.tools.hibernate.runtime.common 4 0 2015-04-16 13:55:50.794
!MESSAGE org.hibernate.tool.hbm2x.HibernateConfigurationExporter.setOutput(java.io.StringWriter)
!STACK 0
java.lang.NoSuchMethodException: org.hibernate.tool.hbm2x.HibernateConfigurationExporter.setOutput(java.io.StringWriter)
at java.lang.Class.getMethod(Class.java:1773)
at org.jboss.tools.hibernate.runtime.common.Util.invokeMethod(Util.java:39)
at org.jboss.tools.hibernate.runtime.common.AbstractExporterFacade.setOutput(AbstractExporterFacade.java:194)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.openContentStream(NewConfigurationWizard.java:301)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.createHibernateCfgXml(NewConfigurationWizard.java:265)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.access$3(NewConfigurationWizard.java:260)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard$2.run(NewConfigurationWizard.java:202)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
!ENTRY org.jboss.tools.hibernate.runtime.common 4 0 2015-04-16 13:55:50.796
!MESSAGE
!STACK 0
java.lang.reflect.InvocationTargetException
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.jboss.tools.hibernate.runtime.common.Util.invokeMethod(Util.java:41)
at org.jboss.tools.hibernate.runtime.common.AbstractExporterFacade.start(AbstractExporterFacade.java:96)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.openContentStream(NewConfigurationWizard.java:302)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.createHibernateCfgXml(NewConfigurationWizard.java:265)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.access$3(NewConfigurationWizard.java:260)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard$2.run(NewConfigurationWizard.java:202)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
Caused by: java.lang.NullPointerException
at org.hibernate.tool.hbm2x.XMLPrettyPrinter.prettyPrintFile(XMLPrettyPrinter.java:95)
at org.hibernate.tool.hbm2x.ArtifactCollector.formatXml(ArtifactCollector.java:69)
at org.hibernate.tool.hbm2x.ArtifactCollector.formatFiles(ArtifactCollector.java:59)
at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:98)
... 11 more
Root exception:
java.lang.NullPointerException
at org.hibernate.tool.hbm2x.XMLPrettyPrinter.prettyPrintFile(XMLPrettyPrinter.java:95)
at org.hibernate.tool.hbm2x.ArtifactCollector.formatXml(ArtifactCollector.java:69)
at org.hibernate.tool.hbm2x.ArtifactCollector.formatFiles(ArtifactCollector.java:59)
at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:98)
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.jboss.tools.hibernate.runtime.common.Util.invokeMethod(Util.java:41)
at org.jboss.tools.hibernate.runtime.common.AbstractExporterFacade.start(AbstractExporterFacade.java:96)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.openContentStream(NewConfigurationWizard.java:302)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.createHibernateCfgXml(NewConfigurationWizard.java:265)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.access$3(NewConfigurationWizard.java:260)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard$2.run(NewConfigurationWizard.java:202)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
{code}
> Hibernate XML file is empty after creating
> ------------------------------------------
>
> Key: JBIDE-19606
> URL: https://issues.jboss.org/browse/JBIDE-19606
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Alpha2
> Environment: JBDS 9.0.0.Alpha2-nightly
> Reporter: Jiri Peterka
> Priority: Blocker
> Fix For: 4.2.0.Alpha2
>
>
> Hibernate configuration is empty after creating via Hibernate Configuration file wizard.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19606) Hibernate XML file is empty after creating
by Jiri Peterka (JIRA)
Jiri Peterka created JBIDE-19606:
------------------------------------
Summary: Hibernate XML file is empty after creating
Key: JBIDE-19606
URL: https://issues.jboss.org/browse/JBIDE-19606
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 4.3.0.Alpha2
Environment: JBDS 9.0.0.Alpha2-nightly
Reporter: Jiri Peterka
Priority: Blocker
Fix For: 4.2.0.Alpha2
Hibernate configuration is empty after creating via Hibernate Configuration file wizard.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19526) JPA validation doesn't detect generator strategy file removal
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19526?page=com.atlassian.jira.plugi... ]
Koen Aers reassigned JBIDE-19526:
---------------------------------
Assignee: Koen Aers
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> JPA validation doesn't detect generator strategy file removal
> -------------------------------------------------------------
>
> Key: JBIDE-19526
> URL: https://issues.jboss.org/browse/JBIDE-19526
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.3.CR1
> Environment: JBDS 8.1.0.CR1
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Fix For: 4.3.0.Beta1
>
>
> JPA Validator normally checks if generator strategy exist. For example when you give wrong name, it reports error which is expected. But when strategy file removed by project explorer it doesn't report any error and reports no error in project.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19447) Constraint violation resolving org.jboss.tools.browsersim.ui
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19447?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov resolved JBIDE-19447.
--------------------------------------------
Resolution: Cannot Reproduce Bug
everything is fine during latest builds, have no idea what has happened
> Constraint violation resolving org.jboss.tools.browsersim.ui
> ------------------------------------------------------------
>
> Key: JBIDE-19447
> URL: https://issues.jboss.org/browse/JBIDE-19447
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Alpha2
>
>
> Build is OK, and publish is working, but tests are failing:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-browsersim_master/136/console}
> 00:04:56.920 !ENTRY org.jboss.tools.browsersim.eclipse 4 0 2015-03-13 08:51:58.758
> 00:04:56.920 !MESSAGE FrameworkEvent ERROR
> 00:04:56.920 !STACK 0
> 00:04:56.920 org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [265]
> 00:04:56.920 Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.3.0"
> 00:04:56.921 -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true"
> 00:04:56.921 org.jboss.tools.browsersim.ui [266]
> 00:04:56.921 Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.javafx.mock; bundle-version="3.6.0"; resolution:="optional"
> 00:04:56.921 Bundle was not resolved because of a uses contraint violation.
> 00:04:56.921 org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.browsersim.ui [osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true"] because it is exposed to package 'org.eclipse.jetty.util.component' from resources org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="9.2.5.v20141112"] and org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="8.1.14.v20131031"] via two dependency chains.
> 00:04:56.922
> 00:04:56.922 Chain 1:
> 00:04:56.922 org.jboss.tools.browsersim.ui [osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true"]
> 00:04:56.923 require: (&(osgi.wiring.bundle=org.eclipse.jetty.util)(bundle-version>=8.1.14))
> 00:04:56.923 |
> 00:04:56.923 provide: osgi.wiring.bundle: org.eclipse.jetty.util
> 00:04:56.923 org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="9.2.5.v20141112"]
> 00:04:56.923
> 00:04:56.923 Chain 2:
> 00:04:56.923 org.jboss.tools.browsersim.ui [osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true"]
> 00:04:56.924 require: (&(osgi.wiring.bundle=org.eclipse.jetty.websocket)(bundle-version>=8.1.14))
> 00:04:56.924 |
> 00:04:56.924 provide: osgi.wiring.bundle; osgi.wiring.bundle="org.eclipse.jetty.websocket"; bundle-version:Version="8.1.14.v20131031"
> 00:04:56.924 org.eclipse.jetty.websocket [osgi.identity; osgi.identity="org.eclipse.jetty.websocket"; type="osgi.bundle"; version:Version="8.1.14.v20131031"]
> 00:04:56.924 import: (&(osgi.wiring.package=org.eclipse.jetty.io)(&(version>=8.1.0)(!(version>=9.0.0))))
> 00:04:56.924 |
> 00:04:56.925 export: osgi.wiring.package=org.eclipse.jetty.io; uses:=org.eclipse.jetty.util.log
> 00:04:56.925 org.eclipse.jetty.io [osgi.identity; osgi.identity="org.eclipse.jetty.io"; type="osgi.bundle"; version:Version="8.1.14.v20131031"]
> 00:04:56.925 import: (&(osgi.wiring.package=org.eclipse.jetty.util.log)(&(version>=8.1.0)(!(version>=9.0.0))))
> 00:04:56.925 |
> 00:04:56.925 export: osgi.wiring.package: org.eclipse.jetty.util.log; uses:=org.eclipse.jetty.util.component
> 00:04:56.925 export: osgi.wiring.package=org.eclipse.jetty.util.component
> 00:04:56.925 org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="8.1.14.v20131031"]
> 00:04:56.926 at org.eclipse.osgi.container.Module.start(Module.java:434)
> 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> 00:04:56.927 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> 00:04:56.927 at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> 00:04:56.927 at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340){code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Mickael Istria resolved JBDS-3285.
----------------------------------
Resolution: Done
Easymport is now included in JBoss Tools and JBoss Developer Studio.
It's clearly not free from bugs, so if you detect some, please report them in individual Jiras.
> Easy Import of non-eclipse projects
> -----------------------------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
> Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19192) provide option for disable html preview
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19192?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-19192:
-------------------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> provide option for disable html preview
> ---------------------------------------
>
> Key: JBIDE-19192
> URL: https://issues.jboss.org/browse/JBIDE-19192
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.2.Final
> Environment: win8.1 64 eclipse luna 4.4.0 jboss 4.2.2
> Reporter: jim harber
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
> Attachments: Clipboard01.png
>
>
> when i use tween.js to create a html page,i create an array,here is the problem:
> var eles = [];
> //push such as 500 elements into eles;
> ..
> then i need call a function to update every element in eles,when these two line:
> requestAnimationFrame(animate);
> TWEEN.update();
> already in the function,i can't see a change in preview and it makes eclipse shutdown,so i put this two line when i finish the other codes,this time preview become normal.
> every time when i type to for(var i=0;i<eles.length;i) eclipse gets stuck. so i wonder is thers any chance i can shutdown living view,i checked preferences panel i didn't find anything.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18227) JS console.debug() displays message to console with LOG prefix
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18227?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-18227:
--------------------------------
Fix Version/s: 4.3.0.Alpha2
(was: 4.3.0.Beta1)
> JS console.debug() displays message to console with LOG prefix
> --------------------------------------------------------------
>
> Key: JBIDE-18227
> URL: https://issues.jboss.org/browse/JBIDE-18227
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, cordovasim
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.0.CR1-v20140831-0335-B201
> Reporter: Vlado Pakan
> Assignee: Ilya Buziuk
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> JavaScript command console.debug("debug message") invoked within page opened in Browsersim is displaying this string to Eclipse console:
> {noformat}
> !JavaScript LOG: debug message
> {noformat}
> It should display this message maybe also with different color then log message is displayed:
> {noformat}
> !JavaScript DEBUG: debug message
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-12108) BrowserSim is not visible in Quick Access by default when installed individually
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12108?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-12108:
--------------------------------
Sprint: Sprint #2 April 2015 (was: Sprint #1 April 2015)
> BrowserSim is not visible in Quick Access by default when installed individually
> --------------------------------------------------------------------------------
>
> Key: JBIDE-12108
> URL: https://issues.jboss.org/browse/JBIDE-12108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 3.3.0.CR1
> Environment: JBT 3.3.0.CR1b, L64, Ubuntu 12.04
> Reporter: Jiri Peterka
> Assignee: Ilya Buziuk
> Fix For: 4.3.0.Beta1
>
> Attachments: browsersim-enabled.png, customize-perspective.png, enable-browsersim.png, mobile-browser.bmp
>
>
> Unable to access BrowserSIM when installed as single feature from JBT CR1. Additional steps are required. This is confusing for a users. BrowserSIM should be accessible and visible after installation if possible.
> *These additional steps are:*
> # Right click on the Eclipse toolbar→Customize Perspective...:
> !customize-perspective.png!
> # Go to the Command Group Availability tab and select BrowserSim command group:
> !enable-browsersim.png!
> # BrowserSim icon will appear on the toolbar:
> !browsersim-enabled.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-12108) BrowserSim is not visible in Quick Access by default when installed individually
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12108?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-12108:
--------------------------------
Summary: BrowserSim is not visible in Quick Access by default when installed individually (was: BrowserSim is not visible when installed individually)
> BrowserSim is not visible in Quick Access by default when installed individually
> --------------------------------------------------------------------------------
>
> Key: JBIDE-12108
> URL: https://issues.jboss.org/browse/JBIDE-12108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 3.3.0.CR1
> Environment: JBT 3.3.0.CR1b, L64, Ubuntu 12.04
> Reporter: Jiri Peterka
> Assignee: Ilya Buziuk
> Fix For: 4.3.0.Beta1
>
> Attachments: browsersim-enabled.png, customize-perspective.png, enable-browsersim.png, mobile-browser.bmp
>
>
> Unable to access BrowserSIM when installed as single feature from JBT CR1. Additional steps are required. This is confusing for a users. BrowserSIM should be accessible and visible after installation if possible.
> *These additional steps are:*
> # Right click on the Eclipse toolbar→Customize Perspective...:
> !customize-perspective.png!
> # Go to the Command Group Availability tab and select BrowserSim command group:
> !enable-browsersim.png!
> # BrowserSim icon will appear on the toolbar:
> !browsersim-enabled.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-12108) BrowserSim is not visible when installed individually
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12108?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-12108:
-------------------------------------
Moving to 4.3.0.Beta1
I have asked the question on eclipse.org forum about possibility of implementing this functionality - https://www.eclipse.org/forums/index.php/t/1065729/
Will see if it is possible to do.
> BrowserSim is not visible when installed individually
> ------------------------------------------------------
>
> Key: JBIDE-12108
> URL: https://issues.jboss.org/browse/JBIDE-12108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 3.3.0.CR1
> Environment: JBT 3.3.0.CR1b, L64, Ubuntu 12.04
> Reporter: Jiri Peterka
> Assignee: Ilya Buziuk
> Fix For: 4.3.0.Beta1
>
> Attachments: browsersim-enabled.png, customize-perspective.png, enable-browsersim.png, mobile-browser.bmp
>
>
> Unable to access BrowserSIM when installed as single feature from JBT CR1. Additional steps are required. This is confusing for a users. BrowserSIM should be accessible and visible after installation if possible.
> *These additional steps are:*
> # Right click on the Eclipse toolbar→Customize Perspective...:
> !customize-perspective.png!
> # Go to the Command Group Availability tab and select BrowserSim command group:
> !enable-browsersim.png!
> # BrowserSim icon will appear on the toolbar:
> !browsersim-enabled.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-12108) BrowserSim is not visible when installed individually
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12108?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-12108:
--------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> BrowserSim is not visible when installed individually
> ------------------------------------------------------
>
> Key: JBIDE-12108
> URL: https://issues.jboss.org/browse/JBIDE-12108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 3.3.0.CR1
> Environment: JBT 3.3.0.CR1b, L64, Ubuntu 12.04
> Reporter: Jiri Peterka
> Assignee: Ilya Buziuk
> Fix For: 4.3.0.Beta1
>
> Attachments: browsersim-enabled.png, customize-perspective.png, enable-browsersim.png, mobile-browser.bmp
>
>
> Unable to access BrowserSIM when installed as single feature from JBT CR1. Additional steps are required. This is confusing for a users. BrowserSIM should be accessible and visible after installation if possible.
> *These additional steps are:*
> # Right click on the Eclipse toolbar→Customize Perspective...:
> !customize-perspective.png!
> # Go to the Command Group Availability tab and select BrowserSim command group:
> !enable-browsersim.png!
> # BrowserSim icon will appear on the toolbar:
> !browsersim-enabled.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18372) Remote EAP server with mgmt profile - Publishing to server shows 0 % until done
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18372?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-18372.
---------------------------------
This is fixed, but I can't really verify it completely ATM, because there is another issue with remote deployment: JBIDE-19350
But I verified it before and even now I can see the progress, so closing.
> Remote EAP server with mgmt profile - Publishing to server shows 0 % until done
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18372
> URL: https://issues.jboss.org/browse/JBIDE-18372
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> When I publish a very big project to a remote server and it's taking minutes, the status bar still keeps saying 0 % is complete.
> I got this issue with a remote EAP 6.3 with management profile. Not sure about file operations profile.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19350) big war deployment to remote server (management) gets stuck
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19350?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-19350:
----------------------------------
Fix Version/s: 4.3.0.Alpha2
> big war deployment to remote server (management) gets stuck
> -----------------------------------------------------------
>
> Key: JBIDE-19350
> URL: https://issues.jboss.org/browse/JBIDE-19350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
> Attachments: remote-publishing-stuck.png
>
>
> I tried deploying an ear with a nested utility project to a remote EAP 6.3 server with the management profile and it got stuck during publishing (10 %).
> I used the project from JBIDE-19043 - see "Steps to Reproduce".
> !remote-publishing-stuck.png!
> I wanted to get a more general use case before reporting this, but I'm still stuck at canceling of the publish task, so I decided to write this JIRA before killing off Eclipse - that is btw a serious problem as well - that you can't cancel the task.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19350) big war deployment to remote server (management) gets stuck
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19350?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19350:
---------------------------------------
[~rob.stryker], I know I should have raised this earlier, but I think we will need this fixed. Today I tried to deploy a big dynamic web project to a remote server (no runtime, management, ssh connection both remote and localhost) and it get's stuck at 31 %.
So it's actually not needed to have an EAR project. It's very simple.
1. Create remote server
2. Create dynamic web project
3. Add a big file inside project/WebContent - like the JBDS installer jar
4. Start the server and try to deploy
5. Deployment shows 20 %, then 31 % and then nothing more - it is stuck
Furthermore, when you're stuck, there is no way to cancel the publishing - if I click the stop button in the progress view, it will stuck on that.
Note that if I only want to deploy a small dynamic web project, it works fine. But inclusion of a big file somehow breaks it.
> big war deployment to remote server (management) gets stuck
> -----------------------------------------------------------
>
> Key: JBIDE-19350
> URL: https://issues.jboss.org/browse/JBIDE-19350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Attachments: remote-publishing-stuck.png
>
>
> I tried deploying an ear with a nested utility project to a remote EAP 6.3 server with the management profile and it got stuck during publishing (10 %).
> I used the project from JBIDE-19043 - see "Steps to Reproduce".
> !remote-publishing-stuck.png!
> I wanted to get a more general use case before reporting this, but I'm still stuck at canceling of the publish task, so I decided to write this JIRA before killing off Eclipse - that is btw a serious problem as well - that you can't cancel the task.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19350) big war deployment to remote server (management) gets stuck
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19350?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-19350:
----------------------------------
Summary: big war deployment to remote server (management) gets stuck (was: EAR project deployment to remote server (management) gets stuck)
> big war deployment to remote server (management) gets stuck
> -----------------------------------------------------------
>
> Key: JBIDE-19350
> URL: https://issues.jboss.org/browse/JBIDE-19350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Attachments: remote-publishing-stuck.png
>
>
> I tried deploying an ear with a nested utility project to a remote EAP 6.3 server with the management profile and it got stuck during publishing (10 %).
> I used the project from JBIDE-19043 - see "Steps to Reproduce".
> !remote-publishing-stuck.png!
> I wanted to get a more general use case before reporting this, but I'm still stuck at canceling of the publish task, so I decided to write this JIRA before killing off Eclipse - that is btw a serious problem as well - that you can't cancel the task.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19605:
-----------------------------------
Summary: Avoid need for multiple javax.servlet (was: Avoid need for multiple jetty)
> Avoid need for multiple javax.servlet
> -------------------------------------
>
> Key: JBIDE-19605
> URL: https://issues.jboss.org/browse/JBIDE-19605
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
>
> We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1.
> {code}
> On 04/15/2015 11:56 PM, Nick Boldt wrote:
> > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
> > 3.1.0 in JBDS.
> > More importantly... SHOULD we be including both? Or can we just include
> > 3.1.0 and drop 3.0.0?
> I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both).
> So I've tried the ultimate test:
> $ cd jbdevstudio-9.0.0.Alpha2/studio
> $ rm plugins/javax.servlet_3.0.0*
> $ ./jbdevstudio
> And saw
> !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967]
> Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)"
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19605:
----------------------------------------
[~ibuziuk] Thanks!
> Avoid need for multiple javax.servlet
> -------------------------------------
>
> Key: JBIDE-19605
> URL: https://issues.jboss.org/browse/JBIDE-19605
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
>
> We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1.
> {code}
> On 04/15/2015 11:56 PM, Nick Boldt wrote:
> > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
> > 3.1.0 in JBDS.
> > More importantly... SHOULD we be including both? Or can we just include
> > 3.1.0 and drop 3.0.0?
> I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both).
> So I've tried the ultimate test:
> $ cd jbdevstudio-9.0.0.Alpha2/studio
> $ rm plugins/javax.servlet_3.0.0*
> $ ./jbdevstudio
> And saw
> !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967]
> Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)"
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19605) Avoid need for multiple jetty
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-19605:
-------------------------------------
AFAIK this is not about jetty bundles but about javax.servlet ones
> Avoid need for multiple jetty
> -----------------------------
>
> Key: JBIDE-19605
> URL: https://issues.jboss.org/browse/JBIDE-19605
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
>
> We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1.
> {code}
> On 04/15/2015 11:56 PM, Nick Boldt wrote:
> > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
> > 3.1.0 in JBDS.
> > More importantly... SHOULD we be including both? Or can we just include
> > 3.1.0 and drop 3.0.0?
> I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both).
> So I've tried the ultimate test:
> $ cd jbdevstudio-9.0.0.Alpha2/studio
> $ rm plugins/javax.servlet_3.0.0*
> $ ./jbdevstudio
> And saw
> !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967]
> Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)"
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19605) Avoid need for multiple jetty
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-19605:
--------------------------------------
Summary: Avoid need for multiple jetty
Key: JBIDE-19605
URL: https://issues.jboss.org/browse/JBIDE-19605
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, webservices
Affects Versions: 4.3.0.Alpha2
Reporter: Mickael Istria
We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1.
{code}
On 04/15/2015 11:56 PM, Nick Boldt wrote:
> Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
> 3.1.0 in JBDS.
> More importantly... SHOULD we be including both? Or can we just include
> 3.1.0 and drop 3.0.0?
I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both).
So I've tried the ultimate test:
$ cd jbdevstudio-9.0.0.Alpha2/studio
$ rm plugins/javax.servlet_3.0.0*
$ ./jbdevstudio
And saw
!ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967]
Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)"
at org.eclipse.osgi.container.Module.start(Module.java:434)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-17822) Launch shortcut enablement expression caused exception
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17822?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-17822:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Launch shortcut enablement expression caused exception
> ------------------------------------------------------
>
> Key: JBIDE-17822
> URL: https://issues.jboss.org/browse/JBIDE-17822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Reporter: Radoslav Rábara
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.3.0.Beta1
>
> Attachments: error1, error2, error3, error4, error5
>
>
> Sometimes when expanding JAX-RS Explorer, a bunch of errors appears in Error Log.
> There are 5 similar errors:
> {code}
> Launch shortcut 'org.testng.eclipse.shortcut' enablement expression caused exception. Shortcut was removed.
> org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesPattern to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement
> {code}
> {code}
> Launch shortcut 'org.testng.eclipse.shortcut.testngSuite' enablement expression caused exception. Shortcut was removed.
> org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesPattern to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement
> {code}
> {code}
> Launch shortcut 'org.jboss.tools.maven.actions.LifeCycleCleanVerify' enablement expression caused exception. Shortcut was removed.
> org.eclipse.core.runtime.CoreException: No property tester contributes a property org.jboss.tools.maven.ui.isCleanVerifyMenuEnabled to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement
> {code}
> {code}
> Launch shortcut 'org.eclipse.ant.ui.antShortcutWithDialog' enablement expression caused exception. Shortcut was removed.
> org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesContentType to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement
> {code}
> {code}
> Launch shortcut 'org.eclipse.ant.ui.antShortcut' enablement expression caused exception. Shortcut was removed.
> org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesContentType to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18516) JAX-RS Validator should report problem when @DefaultValue is used alone
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18516?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-18516:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> JAX-RS Validator should report problem when @DefaultValue is used alone
> -----------------------------------------------------------------------
>
> Key: JBIDE-18516
> URL: https://issues.jboss.org/browse/JBIDE-18516
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.2.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.3.0.Beta1
>
>
> If a method parameter is annotated with {{@DefaultValue}} but has _no_ {{@QueryParam}} (or similar) annotation, then the application will most certainly fail with an error message such as:
> {code}
> failed to execute: javax.ws.rs.NotSupportedException: Could not find message body reader for type: int of content type: */*
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18101) API updates
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18101?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-18101:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> API updates
> -----------
>
> Key: JBIDE-18101
> URL: https://issues.jboss.org/browse/JBIDE-18101
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.3.0.Beta1
>
>
> Unify the JaxrsElement builders to provide the same methods:
> - buildTransient()
> - buildInMetamodel(JaxrsMetamodel)
> Also, simplify the JaxrsElement#update() method (code could be simpler, with less if/else blocks)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18348) Add support for WildFly 9
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18348?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18348:
--------------------------------
Labels: new_and_noteworthy (was: )
> Add support for WildFly 9
> -------------------------
>
> Key: JBIDE-18348
> URL: https://issues.jboss.org/browse/JBIDE-18348
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
>
> Now that WildFly 9.0.0.Alpha1 is out, we need to make sure it works properly with JBT/JBDS.
> I played with it a little, tried to start/stop, deploy a project and so far I haven't seen any issue.
> Other than the one expected that is - when you add the server, you get a warning that the runtime version doesn't match - it detected 9, but 8 is expected. We need to deal with this somehow.
> Runtime detection doesn't work. It find the server (although with a strange Type of "WILDFLY-FULL"), but doesn't actually add it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18582) 4 errors while executing offline script
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18582?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-18582.
---------------------------------
Resolution: Done
offline script now runs every day on jenkins :
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-offline-e... => 0 errors
> 4 errors while executing offline script
> ---------------------------------------
>
> Key: JBIDE-18582
> URL: https://issues.jboss.org/browse/JBIDE-18582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.2.0.CR2
> Reporter: Rastislav Wagner
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha2
>
>
> {code}
> rawagner@rawagner:~/tmp/off$ groovy "/home/rawagner/files/RedHat/JBoss/JBDS/workspace/integration-tests-fork/.metadata/.plugins/org.jboss.tools.project.examples/offline/go_offline_2.0.0.CR2_v20141003_2212_B95.groovy" http://download.jboss.org/jbosstools/examples/project-examples-category-j... http://download.jboss.org/jbosstools/examples/project-examples-jbds80.Bet... http://download.jboss.org/jbosstools/examples/project-examples-shared-4.2... -q -e
> Quiet mode : true
> Descriptors : [http://download.jboss.org/jbosstools/examples/project-examples-category-j..., http://download.jboss.org/jbosstools/examples/project-examples-jbds80.Bet..., http://download.jboss.org/jbosstools/examples/project-examples-shared-4.2...]
> creating offline/.jbosstools/cache
> parsing http://download.jboss.org/jbosstools/examples/project-examples-category-j...
> parsing http://download.jboss.org/jbosstools/examples/project-examples-jbds80.Bet...
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-helloworld-jms.zip into /home/rawagner/tmp/off/offline/workDir/jboss-helloworld-jms.zip [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/wfk/jboss-kitchensink-html5-mobile.zip into /home/rawagner/tmp/off/offline/workDir/jboss-kitchensink-html5-mobile.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-helloworld.zip into /home/rawagner/tmp/off/offline/workDir/jboss-helloworld.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-numberguess.zip into /home/rawagner/tmp/off/offline/workDir/jboss-numberguess.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-helloworld-mdb.zip into /home/rawagner/tmp/off/offline/workDir/jboss-helloworld-mdb.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/wfk/jboss-kitchensink-rf.zip into /home/rawagner/tmp/off/offline/workDir/jboss-kitchensink-rf.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-kitchensink.zip into /home/rawagner/tmp/off/offline/workDir/jboss-kitchensink.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/wfk/jboss-kitchensink-backbone.zip into /home/rawagner/tmp/off/offline/workDir/jboss-kitchensink-backbone.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/wfk/jboss-deltaspike-helloworld-jms.zip into /home/rawagner/tmp/off/offline/workDir/jboss-deltaspike-helloworld-jms.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-helloworld-rs.zip into /home/rawagner/tmp/off/offline/workDir/jboss-helloworld-rs.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-greeter.zip into /home/rawagner/tmp/off/offline/workDir/jboss-greeter.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/wfk/jboss-kitchensink-angularjs.zip into /home/rawagner/tmp/off/offline/workDir/jboss-kitchensink-angularjs.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-jax-rs-client.zip into /home/rawagner/tmp/off/offline/workDir/jboss-jax-rs-client.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/contacts-mobile-basic/0.0.1/contacts-mobile.zip into /home/rawagner/tmp/off/offline/workDir/contacts-mobile.zip
> parsing http://download.jboss.org/jbosstools/examples/project-examples-shared-4.2...
> Building org.jboss.quickstarts.eap:jboss-helloworld-mdb:6.2.0.GA openshift
> [debug] execute contextualize
> Building org.jboss.quickstarts.eap:jboss-jax-rs-client:6.2.0.GA
> Building org.jboss.quickstarts.eap:jboss-helloworld:6.2.0.GA
> Building org.jboss.quickstarts.wfk:jboss-deltaspike-helloworld-jms:2.4.0.Final openshift
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-html5-mobile:2.4.0.Final default,openshift,minify,arq-jbossas-managed
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-html5-mobile:2.4.0.Final arq-jbossas-remote
> Building org.jboss.quickstarts.eap:jboss-numberguess:6.2.0.GA
> Building org.jboss.quickstarts.eap:jboss-kitchensink:6.2.0.GA default,arq-jbossas-managed,openshift
> Building org.jboss.quickstarts.eap:jboss-kitchensink:6.2.0.GA arq-jbossas-remote
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-backbone:2.4.0.Final default,openshift,minify,arq-jbossas-managed,graph
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.1:resolve-plugins (resolve-plugins) on project jboss-kitchensink-backbone: Nested: Could not transfer artifact org.fusesource.mvnplugins:maven-graph-plugin:jar:1.0 from/to mvnplugins.fusesource.org (http://mvnplugins.fusesource.org/repo/release): Connection timed out
> [ERROR] org.fusesource.mvnplugins:maven-graph-plugin:maven-plugin:1.0
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] mvnplugins.fusesource.org (http://mvnplugins.fusesource.org/repo/release, releases=true, snapshots=true),
> [ERROR] redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/, releases=true, snapshots=false),
> [ERROR] jboss-public-repository (https://repository.jboss.org/nexus/content/groups/public-jboss/, releases=true, snapshots=false),
> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false)
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> Result: 1
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-backbone:2.4.0.Final arq-jbossas-remote
> Building org.jboss.quickstarts.eap:jboss-greeter:6.2.0.GA
> Building org.jboss.quickstarts.eap:jboss-helloworld-rs:6.2.0.GA openshift
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-rf:2.4.0.Final default,arq-jbossas-managed,openshift,debug
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-rf:2.4.0.Final arq-jbossas-remote
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-angularjs:2.4.0.Final default,arq-jbossas-managed,openshift
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-angularjs:2.4.0.Final arq-jbossas-remote
> Building org.jboss.quickstarts.eap:jboss-helloworld-jms:6.2.0.GA
> Building org.jboss.tools.example.html5:contacts-mobile-basic-services:0.0.1-SNAPSHOT default,openshift,minify,arq-jbossas-managed
> [ERROR] Failed to execute goal ro.isdc.wro4j:wro4j-maven-plugin:1.4.4:run (default) on project contacts-mobile-basic-services: Exception occured while processing: Exception while loading properties file from /home/rawagner/tmp/off/offline/workDir/contacts-mobile.zip/contacts-mobile-basic-services/src/main/webapp/WEB-INF/wro.properties: /home/rawagner/tmp/off/offline/workDir/contacts-mobile.zip/contacts-mobile-basic-services/src/main/webapp/WEB-INF/wro.properties (No such file or directory) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> Result: 1
> Building org.jboss.tools.example.html5:contacts-mobile-basic-services:0.0.1-SNAPSHOT arq-jbossas-remote
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.2:generate (default-cli) on project standalone-pom: The desired archetype does not exist (org.jboss.tools.archetypes:jboss-forge-html5:1.0.0-SNAPSHOT) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> Result: 1
> offline/workDir/jboss-forge-html5/myapp.jboss-forge-html5/pom.xml can't be found. Skipping maven build
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-ear-archetype:1.0.0-SNAPSHOT
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-ear-archetype:1.0.0-SNAPSHOT jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-ear-blank-archetype:1.0.0-SNAPSHOT
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-ear-blank-archetype:1.0.0-SNAPSHOT jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT default,openshift,minify,arq-jbossas-managed
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT default,openshift,minify,arq-jbossas-managed,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-blank-archetype:1.0.0-SNAPSHOT default,openshift,minify,arq-jbossas-managed,jboss-product-repository
> [ERROR] Failed to execute goal ro.isdc.wro4j:wro4j-maven-plugin:1.4.4:run (default) on project my-jboss-html5-mobile-blank-archetype: Exception occured while processing: Exception while loading properties file from /home/rawagner/tmp/off/offline/workDir/jboss-html5-mobile-blank-archetype/my-jboss-html5-mobile-blank-archetype/src/main/webapp/WEB-INF/wro.properties: /home/rawagner/tmp/off/offline/workDir/jboss-html5-mobile-blank-archetype/my-jboss-html5-mobile-blank-archetype/src/main/webapp/WEB-INF/wro.properties (No such file or directory) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> Result: 1
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-blank-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT default,openshift,minify,arq-jbossas-managed,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-blank-archetype:1.0.0-SNAPSHOT default,openshift,minify,arq-jbossas-managed,jboss-product-repository
> [ERROR] Failed to execute goal ro.isdc.wro4j:wro4j-maven-plugin:1.4.4:run (default) on project my-jboss-html5-mobile-blank-archetype: Exception occured while processing: Exception while loading properties file from /home/rawagner/tmp/off/offline/workDir/jboss-html5-mobile-blank-archetype/my-jboss-html5-mobile-blank-archetype/src/main/webapp/WEB-INF/wro.properties: /home/rawagner/tmp/off/offline/workDir/jboss-html5-mobile-blank-archetype/my-jboss-html5-mobile-blank-archetype/src/main/webapp/WEB-INF/wro.properties (No such file or directory) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> Result: 1
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-blank-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift,debug
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink-enterprise:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift,debug
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink-enterprise:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift,debug,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-simpleapp:1.0.0-SNAPSHOT jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift,debug,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-simpleapp:1.0.0-SNAPSHOT jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-spring-mvc-archetype:1.0.0-SNAPSHOT openshift,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-spring-mvc-archetype:1.0.0-SNAPSHOT openshift,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-errai-kitchensink-archetype:1.0.0-SNAPSHOT default,openshift
> [ERROR] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> [ERROR] SLF4J: Defaulting to no-operation (NOP) logger implementation
> [ERROR] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> [ERROR] Oct 10, 2014 11:08:24 AM org.hibernate.annotations.common.Version <clinit>
> [ERROR] INFO: HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
> [ERROR] Oct 10, 2014 11:08:24 AM org.hibernate.Version logVersion
> [ERROR] INFO: HHH000412: Hibernate Core {4.1.1}
> [ERROR] Oct 10, 2014 11:08:24 AM org.hibernate.cfg.Environment <clinit>
> [ERROR] INFO: HHH000206: hibernate.properties not found
> [ERROR] Oct 10, 2014 11:08:24 AM org.hibernate.cfg.Environment buildBytecodeProvider
> [ERROR] INFO: HHH000021: Bytecode provider name : javassist
> [ERROR] Oct 10, 2014 11:08:24 AM org.hibernate.ejb.Ejb3Configuration configure
> [ERROR] INFO: HHH000204: Processing PersistenceUnitInfo [
> [ERROR] name: ErraiClientPersistenceUnit
> [ERROR] ...]
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator initiateService
> [ERROR] WARN: HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.Dialect <init>
> [ERROR] INFO: HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.H2Dialect <init>
> [ERROR] WARN: HHH000431: Unable to determine H2 database version, certain features may not work
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.jdbc.internal.LobCreatorBuilder useContextualLobCreation
> [ERROR] INFO: HHH000422: Disabling contextual LOB creation as connection was null
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.transaction.internal.TransactionFactoryInitiator initiateService
> [ERROR] INFO: HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory <init>
> [ERROR] INFO: HHH000397: Using ASTQueryTranslatorFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.ejb.Ejb3Configuration configure
> [ERROR] INFO: HHH000204: Processing PersistenceUnitInfo [
> [ERROR] name: ErraiClientPersistenceUnit
> [ERROR] ...]
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator initiateService
> [ERROR] WARN: HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.Dialect <init>
> [ERROR] INFO: HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.H2Dialect <init>
> [ERROR] WARN: HHH000431: Unable to determine H2 database version, certain features may not work
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.jdbc.internal.LobCreatorBuilder useContextualLobCreation
> [ERROR] INFO: HHH000422: Disabling contextual LOB creation as connection was null
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.transaction.internal.TransactionFactoryInitiator initiateService
> [ERROR] INFO: HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory <init>
> [ERROR] INFO: HHH000397: Using ASTQueryTranslatorFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.ejb.Ejb3Configuration configure
> [ERROR] INFO: HHH000204: Processing PersistenceUnitInfo [
> [ERROR] name: ErraiClientPersistenceUnit
> [ERROR] ...]
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator initiateService
> [ERROR] WARN: HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.Dialect <init>
> [ERROR] INFO: HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.H2Dialect <init>
> [ERROR] WARN: HHH000431: Unable to determine H2 database version, certain features may not work
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.jdbc.internal.LobCreatorBuilder useContextualLobCreation
> [ERROR] INFO: HHH000422: Disabling contextual LOB creation as connection was null
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.transaction.internal.TransactionFactoryInitiator initiateService
> [ERROR] INFO: HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory <init>
> [ERROR] INFO: HHH000397: Using ASTQueryTranslatorFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.ejb.Ejb3Configuration configure
> [ERROR] INFO: HHH000204: Processing PersistenceUnitInfo [
> [ERROR] name: ErraiClientPersistenceUnit
> [ERROR] ...]
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator initiateService
> [ERROR] WARN: HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.Dialect <init>
> [ERROR] INFO: HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.H2Dialect <init>
> [ERROR] WARN: HHH000431: Unable to determine H2 database version, certain features may not work
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.jdbc.internal.LobCreatorBuilder useContextualLobCreation
> [ERROR] INFO: HHH000422: Disabling contextual LOB creation as connection was null
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.transaction.internal.TransactionFactoryInitiator initiateService
> [ERROR] INFO: HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory <init>
> [ERROR] INFO: HHH000397: Using ASTQueryTranslatorFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.ejb.Ejb3Configuration configure
> [ERROR] INFO: HHH000204: Processing PersistenceUnitInfo [
> [ERROR] name: ErraiClientPersistenceUnit
> [ERROR] ...]
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator initiateService
> [ERROR] WARN: HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.Dialect <init>
> [ERROR] INFO: HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.H2Dialect <init>
> [ERROR] WARN: HHH000431: Unable to determine H2 database version, certain features may not work
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.jdbc.internal.LobCreatorBuilder useContextualLobCreation
> [ERROR] INFO: HHH000422: Disabling contextual LOB creation as connection was null
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.transaction.internal.TransactionFactoryInitiator initiateService
> [ERROR] INFO: HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory <init>
> [ERROR] INFO: HHH000397: Using ASTQueryTranslatorFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.ejb.Ejb3Configuration configure
> [ERROR] INFO: HHH000204: Processing PersistenceUnitInfo [
> [ERROR] name: ErraiClientPersistenceUnit
> [ERROR] ...]
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator initiateService
> [ERROR] WARN: HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.Dialect <init>
> [ERROR] INFO: HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.H2Dialect <init>
> [ERROR] WARN: HHH000431: Unable to determine H2 database version, certain features may not work
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.jdbc.internal.LobCreatorBuilder useContextualLobCreation
> [ERROR] INFO: HHH000422: Disabling contextual LOB creation as connection was null
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.transaction.internal.TransactionFactoryInitiator initiateService
> [ERROR] INFO: HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory <init>
> [ERROR] INFO: HHH000397: Using ASTQueryTranslatorFactory
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype-enterprise:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype-enterprise:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype-enterprise:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype-enterprise:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-ear-archetype:1.0.0-SNAPSHOT
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-ear-blank-archetype:1.0.0-SNAPSHOT
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT default,openshift,minify,arq-jbossas-managed
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype-enterprise:1.0.0-SNAPSHOT default,openshift,minify,arq-jbossas-managed
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype-enterprise:1.0.0-SNAPSHOT arq-jbossas-remote
> Cleaning up installed artifacts created from archetypes
> Script executed in 30 min, 55 sec with 4 error(s)
> Project offline/workDir/jboss-kitchensink-backbone.zip failed to build
> Project offline/workDir/contacts-mobile.zip/contacts-mobile-basic-services failed to build
> Failed to generate project myapp.jboss-forge-html5 from archetype org.jboss.tools.archetypes:jboss-forge-html5:1.0.0-SNAPSHOT
> Project offline/workDir/jboss-html5-mobile-blank-archetype/my-jboss-html5-mobile-blank-archetype failed to build
> {code}
> Project offline/workDir/jboss-kitchensink-backbone.zip failed to build - reported in JBIDE-18581
> Project offline/workDir/contacts-mobile.zip/contacts-mobile-basic-services failed to build - reported in JBIDE-18579
> Im not sure what to do about the rest:
> Project offline/workDir/jboss-html5-mobile-blank-archetype/my-jboss-html5-mobile-blank-archetype failed to build - wro4j files are missing since its blank archetype so minify profile doesnt work
> Failed to generate project myapp.jboss-forge-html5 from archetype org.jboss.tools.archetypes:jboss-forge-html5:1.0.0-SNAPSHOT - pom.xml can't be found
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[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 commented on JBDS-3208:
----------------------------------
Yes, unless you want early access stuff too, in which case you can use:
* http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... and
* https://devstudio.jboss.com/9.0/snapshots/builds/jbosstools-discovery.ear...
> 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)
11 years
[JBoss JIRA] (JBIDE-19108) Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19108?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-19108.
---------------------------------
Resolution: Rejected
Setting the default host is inappropriate given the workflow. Users who press 'back' and select a new server type should also be sure to set their host, which is on the same page where they select server type. They don't need to workaround as described above by opening the editor. It's right in the wizard, on the same page as server type.
Sorry, but this is a won't-fix
> Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19108
> URL: https://issues.jboss.org/browse/JBIDE-19108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.2.Final
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
> Attachments: JBIDE-19108_1.png, JBIDE-19108_2.png, JBIDE-19108_3.png, server_already_running.png
>
>
> If I am creating new server in Servers view via New Server wizard and I select in tree at first OpenShift Server Adapter and then e.g. Wildfly 8.x server, then created server cannot be started. There is a warning there there is server running on openshift.redhat.com:8080. User has to delete such server from servers view and create a new one without selecting OpenShift Server Adapter in server type selection.
> !server_already_running.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19604) Save Password in New Openshift Application Wizard is annoying
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19604?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-19604:
----------------------------------
Description: Selected "Save Password" option in wizard triggers secure storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three or more times). After reopening wizard first Security Storage Login pops up that I have to Cancel it several times (see attached video). (was: Selected "Save Password" option in wizard triggers secure storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three or more times). After reopening wizard first Security Storage Login pops up that I have to Cancel it several times.)
> Save Password in New Openshift Application Wizard is annoying
> -------------------------------------------------------------
>
> Key: JBIDE-19604
> URL: https://issues.jboss.org/browse/JBIDE-19604
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Environment: Linux, x86_64, Open JDK 7
> Reporter: Denis Golovin
> Attachments: openshif-save-password.mp4
>
>
> Selected "Save Password" option in wizard triggers secure storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three or more times). After reopening wizard first Security Storage Login pops up that I have to Cancel it several times (see attached video).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19604) Save Password in New Openshift Application Wizard is annoying
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19604?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-19604:
----------------------------------
Description: Selected "Save Password" option in wizard triggers secure storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three or more times). After reopening wizard first Security Storage Login pops up that I have to Cancel it several times. (was: Selected "Save Password" option in wizard triggers secues storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three times). After reopening wizard first Security Storage Login pops up that I have to Cancel twice.)
> Save Password in New Openshift Application Wizard is annoying
> -------------------------------------------------------------
>
> Key: JBIDE-19604
> URL: https://issues.jboss.org/browse/JBIDE-19604
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Environment: Linux, x86_64, Open JDK 7
> Reporter: Denis Golovin
> Attachments: openshif-save-password.mp4
>
>
> Selected "Save Password" option in wizard triggers secure storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three or more times). After reopening wizard first Security Storage Login pops up that I have to Cancel it several times.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19604) Save Password in New Openshift Application Wizard is annoying
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19604?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-19604:
----------------------------------
Attachment: openshif-save-password.mp4
> Save Password in New Openshift Application Wizard is annoying
> -------------------------------------------------------------
>
> Key: JBIDE-19604
> URL: https://issues.jboss.org/browse/JBIDE-19604
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Environment: Linux, x86_64, Open JDK 7
> Reporter: Denis Golovin
> Attachments: openshif-save-password.mp4
>
>
> Selected "Save Password" option in wizard triggers secues storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three times). After reopening wizard first Security Storage Login pops up that I have to Cancel twice.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19604) Save Password in New Openshift Application Wizard is annoying
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-19604:
-------------------------------------
Summary: Save Password in New Openshift Application Wizard is annoying
Key: JBIDE-19604
URL: https://issues.jboss.org/browse/JBIDE-19604
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Alpha2
Environment: Linux, x86_64, Open JDK 7
Reporter: Denis Golovin
Selected "Save Password" option in wizard triggers secues storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three times). After reopening wizard first Security Storage Login pops up that I have to Cancel twice.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19603) NPE in openshift application wizard after several attempts to remember credentials
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-19603:
-------------------------------------
Summary: NPE in openshift application wizard after several attempts to remember credentials
Key: JBIDE-19603
URL: https://issues.jboss.org/browse/JBIDE-19603
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Alpha2
Environment: Linux
Reporter: Denis Golovin
I was trying to recover my password with try and fail method and finally succeeded to recover it but next step I got NPE's after pushing Browse button.
Authorization error was:
{code}com.openshift.client.InvalidCredentialsOpenShiftException: Your credentials are not authorized to access "https://openshift.redhat.com/broker/rest/user"
at com.openshift.internal.client.RestService.request(RestService.java:114)
at com.openshift.internal.client.RestService.request(RestService.java:92)
at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:143)
at com.openshift.internal.client.APIResource$GetUserRequest.execute(APIResource.java:400)
at com.openshift.internal.client.APIResource.getUser(APIResource.java:101)
at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.doCreateUser(ExpressConnection.java:221)
at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.createUser(ExpressConnection.java:206)
at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.connect(ExpressConnection.java:183)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:316)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:459)
at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.openshift.internal.client.httpclient.UnauthorizedException: HTTP Basic: Access denied.
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:165)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:144)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:103)
at com.openshift.internal.client.RestService.request(RestService.java:160)
at com.openshift.internal.client.RestService.request(RestService.java:107)
... 11 more
Caused by: java.io.IOException: Server returned HTTP response code: 401 for URL: https://openshift.redhat.com/broker/rest/user
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1627)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:161)
... 15 more{code}
and then NPE:
{code}java.lang.NullPointerException
at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.loadDomains(SelectApplicationWizardPageModel.java:71)
at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.loadOpenShiftResources(SelectApplicationWizardPageModel.java:67)
at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPage.onPageActivated(SelectApplicationWizardPage.java:135)
at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$1.pageChanged(AbstractOpenShiftWizardPage.java:87)
at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1505)
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.wizard.WizardDialog.firePageChanged(WizardDialog.java:1502)
at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1308)
at org.eclipse.jface.wizard.WizardDialog.showStartingPage(WizardDialog.java:1258)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:599)
at org.eclipse.jface.window.Window.create(Window.java:430)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
at org.eclipse.jface.window.Window.open(Window.java:792)
at org.jboss.tools.openshift.express.internal.ui.wizard.application.ApplicationTemplateWizardPage$2.widgetSelected(ApplicationTemplateWizardPage.java:237)
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:4477)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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:152)
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:4477)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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}
and then one more NPE:
{code}java.lang.NullPointerException
at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.refreshDomains(SelectApplicationWizardPageModel.java:49)
at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.refresh(SelectApplicationWizardPageModel.java:44)
at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPage$2$1.run(SelectApplicationWizardPage.java:148)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}
Then I pushed Back and Next and was able to see cartridges and browse my old applications.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19602) "Warning: NLS unused message" in org.jboss.tools.common.jdt.debug
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19602?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-19602:
--------------------------------------
Assignee: Rob Stryker
> "Warning: NLS unused message" in org.jboss.tools.common.jdt.debug
> -----------------------------------------------------------------
>
> Key: JBIDE-19602
> URL: https://issues.jboss.org/browse/JBIDE-19602
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Rob Stryker
>
> {code}Warning: NLS unused message: updatePeriodNotEnteredMsg in: org.jboss.tools.common.jdt.debug.messages
> Warning: NLS unused message: illegalUpdatePeriodMsg in: org.jboss.tools.common.jdt.debug.messages
> Warning: NLS unused message: updatePeriodOutOfRangeMsg in: org.jboss.tools.common.jdt.debug.messages
> Warning: NLS unused message: loadAgentFailedMsg in: org.jboss.tools.common.jdt.debug.messages
> Warning: NLS unused message: agentJarNotFoundMsg in: org.jboss.tools.common.jdt.debug.messages
> Warning: NLS unused message: agentJarFoundMsg in: org.jboss.tools.common.jdt.debug.messages
> Warning: NLS unused message: corePluginNoFoundMsg in: org.jboss.tools.common.jdt.debug.messages
> Warning: NLS unused message: charsetNotSupportedMsg in: org.jboss.tools.common.jdt.debug.messages
> Warning: NLS unused message: readInputStreamFailedMsg in: org.jboss.tools.common.jdt.debug.messages
> Warning: NLS unused message: updateTimerCanceledMsg in: org.jboss.tools.common.jdt.debug.messages
> Warning: NLS unused message: getMonitoredJvmFailedMsg in: org.jboss.tools.common.jdt.debug.messages
> Warning: NLS unused message: getLocalConnectorAddressFailedMsg in: org.jboss.tools.common.jdt.debug.messages
> Warning: NLS unused message: connectTargetJvmFailedMsg in: org.jboss.tools.common.jdt.debug.messages
> Warning: NLS unused message: fileNotFoundMsg in: org.jboss.tools.common.jdt.debug.messages
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19602) "Warning: NLS unused message" in org.jboss.tools.common.jdt.debug
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-19602:
-------------------------------------
Summary: "Warning: NLS unused message" in org.jboss.tools.common.jdt.debug
Key: JBIDE-19602
URL: https://issues.jboss.org/browse/JBIDE-19602
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 4.3.0.Alpha2
Reporter: Denis Golovin
{code}Warning: NLS unused message: updatePeriodNotEnteredMsg in: org.jboss.tools.common.jdt.debug.messages
Warning: NLS unused message: illegalUpdatePeriodMsg in: org.jboss.tools.common.jdt.debug.messages
Warning: NLS unused message: updatePeriodOutOfRangeMsg in: org.jboss.tools.common.jdt.debug.messages
Warning: NLS unused message: loadAgentFailedMsg in: org.jboss.tools.common.jdt.debug.messages
Warning: NLS unused message: agentJarNotFoundMsg in: org.jboss.tools.common.jdt.debug.messages
Warning: NLS unused message: agentJarFoundMsg in: org.jboss.tools.common.jdt.debug.messages
Warning: NLS unused message: corePluginNoFoundMsg in: org.jboss.tools.common.jdt.debug.messages
Warning: NLS unused message: charsetNotSupportedMsg in: org.jboss.tools.common.jdt.debug.messages
Warning: NLS unused message: readInputStreamFailedMsg in: org.jboss.tools.common.jdt.debug.messages
Warning: NLS unused message: updateTimerCanceledMsg in: org.jboss.tools.common.jdt.debug.messages
Warning: NLS unused message: getMonitoredJvmFailedMsg in: org.jboss.tools.common.jdt.debug.messages
Warning: NLS unused message: getLocalConnectorAddressFailedMsg in: org.jboss.tools.common.jdt.debug.messages
Warning: NLS unused message: connectTargetJvmFailedMsg in: org.jboss.tools.common.jdt.debug.messages
Warning: NLS unused message: fileNotFoundMsg in: org.jboss.tools.common.jdt.debug.messages
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3351) Copyright notice refers to 2014, not 2015
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3351?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3351:
-----------------------------
CDW devel_ack: + (was: ?)
> Copyright notice refers to 2014, not 2015
> -----------------------------------------
>
> Key: JBDS-3351
> URL: https://issues.jboss.org/browse/JBDS-3351
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 9.0.0.Alpha1
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Trivial
> Fix For: 9.0.0.Alpha2
>
>
> The copyright notice for 9.0.0.Alpha1 reads:
> ====================================
> Version: 9.0.0.Alpha1
> Build id: Alpha1-v20150216-1042-B11
> Build date: 20150216-1042
> Copyright (c) 2004-2014 Red Hat, Inc., contributors and others. All rights reserved.
> ====================================
> ------> Shouldn't this refer to 2004-2015?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3351) Copyright notice refers to 2014, not 2015
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3351?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-3351.
------------------------------
Resolution: Done
> Copyright notice refers to 2014, not 2015
> -----------------------------------------
>
> Key: JBDS-3351
> URL: https://issues.jboss.org/browse/JBDS-3351
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 9.0.0.Alpha1
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Trivial
> Fix For: 9.0.0.Alpha2
>
>
> The copyright notice for 9.0.0.Alpha1 reads:
> ====================================
> Version: 9.0.0.Alpha1
> Build id: Alpha1-v20150216-1042-B11
> Build date: 20150216-1042
> Copyright (c) 2004-2014 Red Hat, Inc., contributors and others. All rights reserved.
> ====================================
> ------> Shouldn't this refer to 2004-2015?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3351) Copyright notice refers to 2014, not 2015
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3351?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3351:
-----------------------------
CDW release: ?
Status: New (was: New)
Target Release: 9.0.0.GA
> Copyright notice refers to 2014, not 2015
> -----------------------------------------
>
> Key: JBDS-3351
> URL: https://issues.jboss.org/browse/JBDS-3351
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 9.0.0.Alpha1
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Trivial
> Fix For: 9.0.0.Alpha2
>
>
> The copyright notice for 9.0.0.Alpha1 reads:
> ====================================
> Version: 9.0.0.Alpha1
> Build id: Alpha1-v20150216-1042-B11
> Build date: 20150216-1042
> Copyright (c) 2004-2014 Red Hat, Inc., contributors and others. All rights reserved.
> ====================================
> ------> Shouldn't this refer to 2004-2015?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3351) Copyright notice refers to 2014, not 2015
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3351?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3351:
-----------------------------
CDW release: + (was: ?)
> Copyright notice refers to 2014, not 2015
> -----------------------------------------
>
> Key: JBDS-3351
> URL: https://issues.jboss.org/browse/JBDS-3351
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 9.0.0.Alpha1
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Trivial
> Fix For: 9.0.0.Alpha2
>
>
> The copyright notice for 9.0.0.Alpha1 reads:
> ====================================
> Version: 9.0.0.Alpha1
> Build id: Alpha1-v20150216-1042-B11
> Build date: 20150216-1042
> Copyright (c) 2004-2014 Red Hat, Inc., contributors and others. All rights reserved.
> ====================================
> ------> Shouldn't this refer to 2004-2015?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3351) Copyright notice refers to 2014, not 2015
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3351?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3351:
--------------------------------
> Copyright notice refers to 2014, not 2015
> -----------------------------------------
>
> Key: JBDS-3351
> URL: https://issues.jboss.org/browse/JBDS-3351
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 9.0.0.Alpha1
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Trivial
> Fix For: 9.0.0.Alpha2
>
>
> The copyright notice for 9.0.0.Alpha1 reads:
> ====================================
> Version: 9.0.0.Alpha1
> Build id: Alpha1-v20150216-1042-B11
> Build date: 20150216-1042
> Copyright (c) 2004-2014 Red Hat, Inc., contributors and others. All rights reserved.
> ====================================
> ------> Shouldn't this refer to 2004-2015?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3351) Copyright notice refers to 2014, not 2015
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3351?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3351:
-----------------------------
CDW qa_ack: + (was: ?)
> Copyright notice refers to 2014, not 2015
> -----------------------------------------
>
> Key: JBDS-3351
> URL: https://issues.jboss.org/browse/JBDS-3351
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 9.0.0.Alpha1
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Trivial
> Fix For: 9.0.0.Alpha2
>
>
> The copyright notice for 9.0.0.Alpha1 reads:
> ====================================
> Version: 9.0.0.Alpha1
> Build id: Alpha1-v20150216-1042-B11
> Build date: 20150216-1042
> Copyright (c) 2004-2014 Red Hat, Inc., contributors and others. All rights reserved.
> ====================================
> ------> Shouldn't this refer to 2004-2015?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3351) Copyright notice refers to 2014, not 2015
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3351?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3351 at 4/15/15 5:36 PM:
-----------------------------------------------------------
Updated files in JBDS:
{code}
modified: features/com.jboss.devstudio.core.feature.source/feature.properties
modified: features/com.jboss.devstudio.core.feature/feature.properties
modified: installer/src/config/resources/EULA/JBoss-EULA.html
modified: installer/src/test/com/jboss/devstudio/core/installer/IUListPanelTest.java
modified: plugins/com.jboss.devstudio.core.usage.branding/about.properties
modified: plugins/com.jboss.devstudio.core/about.html
modified: plugins/com.jboss.devstudio.core/about.properties
modified: plugins/com.jboss.devstudio.core/plugin.properties
modified: site/com.jboss.devstudio.core.product
{code}
https://github.com/jbdevstudio/jbdevstudio-product/commit/bdf9459bd8722ab...
Building:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >= 2960
was (Author: nickboldt):
Updated files in JBDS:
{code}
modified: features/com.jboss.devstudio.core.feature.source/feature.properties
modified: features/com.jboss.devstudio.core.feature/feature.properties
modified: installer/src/config/resources/EULA/JBoss-EULA.html
modified: installer/src/test/com/jboss/devstudio/core/installer/IUListPanelTest.java
modified: plugins/com.jboss.devstudio.core.usage.branding/about.properties
modified: plugins/com.jboss.devstudio.core/about.html
modified: plugins/com.jboss.devstudio.core/about.properties
modified: plugins/com.jboss.devstudio.core/plugin.properties
modified: site/com.jboss.devstudio.core.product
{code}
https://github.com/jbdevstudio/jbdevstudio-product/commit/bdf9459bd8722ab...
> Copyright notice refers to 2014, not 2015
> -----------------------------------------
>
> Key: JBDS-3351
> URL: https://issues.jboss.org/browse/JBDS-3351
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 9.0.0.Alpha1
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Trivial
> Fix For: 9.0.0.Alpha2
>
>
> The copyright notice for 9.0.0.Alpha1 reads:
> ====================================
> Version: 9.0.0.Alpha1
> Build id: Alpha1-v20150216-1042-B11
> Build date: 20150216-1042
> Copyright (c) 2004-2014 Red Hat, Inc., contributors and others. All rights reserved.
> ====================================
> ------> Shouldn't this refer to 2004-2015?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3351) Copyright notice refers to 2014, not 2015
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3351?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3351:
-----------------------------
CDW docs_ack: ?
CDW devel_ack: ?
CDW pm_ack: +
CDW qa_ack: ?
> Copyright notice refers to 2014, not 2015
> -----------------------------------------
>
> Key: JBDS-3351
> URL: https://issues.jboss.org/browse/JBDS-3351
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 9.0.0.Alpha1
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Trivial
> Fix For: 9.0.0.Alpha2
>
>
> The copyright notice for 9.0.0.Alpha1 reads:
> ====================================
> Version: 9.0.0.Alpha1
> Build id: Alpha1-v20150216-1042-B11
> Build date: 20150216-1042
> Copyright (c) 2004-2014 Red Hat, Inc., contributors and others. All rights reserved.
> ====================================
> ------> Shouldn't this refer to 2004-2015?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3351) Copyright notice refers to 2014, not 2015
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3351?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3351:
----------------------------------
Updated files in JBDS:
{code}
modified: features/com.jboss.devstudio.core.feature.source/feature.properties
modified: features/com.jboss.devstudio.core.feature/feature.properties
modified: installer/src/config/resources/EULA/JBoss-EULA.html
modified: installer/src/test/com/jboss/devstudio/core/installer/IUListPanelTest.java
modified: plugins/com.jboss.devstudio.core.usage.branding/about.properties
modified: plugins/com.jboss.devstudio.core/about.html
modified: plugins/com.jboss.devstudio.core/about.properties
modified: plugins/com.jboss.devstudio.core/plugin.properties
modified: site/com.jboss.devstudio.core.product
{code}
https://github.com/jbdevstudio/jbdevstudio-product/commit/bdf9459bd8722ab...
> Copyright notice refers to 2014, not 2015
> -----------------------------------------
>
> Key: JBDS-3351
> URL: https://issues.jboss.org/browse/JBDS-3351
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 9.0.0.Alpha1
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Trivial
> Fix For: 9.0.0.Alpha2
>
>
> The copyright notice for 9.0.0.Alpha1 reads:
> ====================================
> Version: 9.0.0.Alpha1
> Build id: Alpha1-v20150216-1042-B11
> Build date: 20150216-1042
> Copyright (c) 2004-2014 Red Hat, Inc., contributors and others. All rights reserved.
> ====================================
> ------> Shouldn't this refer to 2004-2015?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-19025 at 4/15/15 5:18 PM:
-------------------------------------------------------------
We now have 2 update sites for Central and 2 for Early Access:
* Central Update Site (contains only things from JBT)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
** Output: http://download.jboss.org/jbosstools/mars/snapshots/updates/central/master/
* Central TP (third party stuff)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta...
** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/
* Early Access Update Site (contains only things from JBT)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
** Output: http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess/m...
* Early Access TP (third party stuff)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta...
** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/
This results in discovery sites for JBT Central, JBT EA, JBDS Central, and JBDS EA, built here [1]:
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ea...
So now when things change in JBT, they're rebuilt into an *update site* instead of affecting a *target platform*, which will make our release process more efficient.
[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-discovery...
was (Author: nickboldt):
We now have 2 update sites for Central and 2 for Early Access:
* Central Update Site (contains only things from JBT)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
** Output: http://download.jboss.org/jbosstools/mars/snapshots/updates/central/master/
* Central TP (third party stuff)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta...
** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/
* Early Access Update Site (contains only things from JBT)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
** Output: http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess/m...
* Early Access TP (third party stuff)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta...
** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/
This results in discovery sites for JBT Central, JBT EA, JBDS Central, and JBDS EA:
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ea...
So now when things change in JBT, they're rebuilt into an *update site* instead of affecting a *target platform*, which will make our release process more efficient.
> Separate JBT and JBDS Central and EA sites
> ------------------------------------------
>
> Key: JBIDE-19025
> URL: https://issues.jboss.org/browse/JBIDE-19025
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: discovery
> Affects Versions: 4.2.2.Final
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.3.0.Beta1
>
>
> Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them.
> This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need.
> So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS.
> Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-19025 at 4/15/15 5:17 PM:
-------------------------------------------------------------
We now have 2 update sites for Central and 2 for Early Access:
* Central Update Site (contains only things from JBT)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
** Output: http://download.jboss.org/jbosstools/mars/snapshots/updates/central/master/
* Central TP (third party stuff)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta...
** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/
* Early Access Update Site (contains only things from JBT)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
** Output: http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess/m...
* Early Access TP (third party stuff)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta...
** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/
This results in discovery sites for JBT Central, JBT EA, JBDS Central, and JBDS EA:
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ea...
So now when things change in JBT, they're rebuilt into an *update site* instead of affecting a *target platform*, which will make our release process more efficient.
was (Author: nickboldt):
We now have 2 update sites for Central and 2 for Early Access:
* Central Update Site (contains only things from JBT)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
** Output:
* Central TP (third party stuff)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta...
** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/
* Early Access Update Site (contains only things from JBT)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
** Output:
* Early Access TP (third party stuff)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta...
** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/
This results in discovery sites for JBT Central, JBT EA, JBDS Central, and JBDS EA:
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ea...
So now when things change in JBT, they're rebuilt into an *update site* instead of affecting a *target platform*, which will make our release process more efficient.
> Separate JBT and JBDS Central and EA sites
> ------------------------------------------
>
> Key: JBIDE-19025
> URL: https://issues.jboss.org/browse/JBIDE-19025
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: discovery
> Affects Versions: 4.2.2.Final
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.3.0.Beta1
>
>
> Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them.
> This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need.
> So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS.
> Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19025:
------------------------------------
We now have 2 update sites for Central and 2 for Early Access:
* Central Update Site (contains only things from JBT)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
** Output:
* Central TP (third party stuff)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta...
** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/
* Early Access Update Site (contains only things from JBT)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
** Output:
* Early Access TP (third party stuff)
** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta...
** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/
This results in discovery sites for JBT Central, JBT EA, JBDS Central, and JBDS EA:
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ea...
So now when things change in JBT, they're rebuilt into an *update site* instead of affecting a *target platform*, which will make our release process more efficient.
> Separate JBT and JBDS Central and EA sites
> ------------------------------------------
>
> Key: JBIDE-19025
> URL: https://issues.jboss.org/browse/JBIDE-19025
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: discovery
> Affects Versions: 4.2.2.Final
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.3.0.Beta1
>
>
> Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them.
> This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need.
> So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS.
> Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3208:
--------------------------------------
Cool. So should install-grinder jobs be changed to use http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... and https://devstudio.jboss.com/9.0/snapshots/builds/jbosstools-discovery.cen... ?
> 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)
11 years
[JBoss JIRA] (JBIDE-19473) Central can't load Discovery catalog
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19473?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-19473.
------------------------------
I've fixed the jobs to use the correct new publishing locations.
Details here: https://issues.jboss.org/browse/JBDS-3208?focusedCommentId=13059479&page=...
Closing. Reopen if symptoms reappear. :D
> Central can't load Discovery catalog
> ------------------------------------
>
> Key: JBIDE-19473
> URL: https://issues.jboss.org/browse/JBIDE-19473
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: discovery
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.3.0.Alpha2
>
>
> Both locally and with install-grinder, after installing nighly build from master, Central compains about "no connectors" found.
> The URL of the catalog seems right ( http://download.jboss.org/jbosstools/discovery/nightly/core/master/jbosst... ), referenced plugins are existing and seem to have right content.
> Log says
> {quote}
> !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-03-19 10:22:00.223
> !MESSAGE Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'angularjs-eclipse-feature' declared in org.jboss.tools.central.discovery.earlyaccess_4.3.0.Alpha2_v20150318_0819_B3421.jar_8982963591780016496.jar
> {quote}
> I looked at jbosstoold-discovery history to see whether there was a suspicious change since last success (March 13th for install-grinder) and couldn't see anything related.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[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 commented on JBDS-3208:
----------------------------------
I've fixed the jobs [1], [2] to use the correct new publishing locations, INCLUDING fixing jbosstools-cleanup.sh [3], [4] so it works for devstudio.redhat.com /builds/ folders too [3], [4].
[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-discovery...
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-discovery...
[3] https://github.com/jbosstools/jbosstools-build-ci/commit/bf4e07ffd4a1291a...
[4] https://github.com/jbosstools/jbosstools-build-ci/commit/e14086feeed1abb7...
[5] https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce...
[6] https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ea...
Also updated ide-config.properties [7] to pull from the new correct paths [8], [9]:
[7] https://github.com/jbosstools/jbosstools-download.jboss.org/commit/10b7cd...
[8] http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
[9] http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
And I've prepared new paths on devstudio.redhat.com, such as [10], [11], so we'll be ready for Alpha2 publishing to the new path conventions:
[10] https://devstudio.redhat.com/9.0/snapshots/updates/
[11] https://devstudio.redhat.com/9.0/staging/updates/
> 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)
11 years
[JBoss JIRA] (JBIDE-19601) Explorer: Resources cannot be listed when using latest OpenShift origin v3 code
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19601?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19601:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure you're using the latest openshift origin code from github (https://github.com/openshift/origin.git)
# EXEC: create a new connection (with the credentials that you have set to the server) and hit "Finish"
# ASSERT: the connection dialog closes
Result:
You get an error dialog popping up telling you that the connection was refused
!connection-refused.png!
In the Eclipse log one can see the following stack trace:
{code}
java.lang.RuntimeException: java.lang.RuntimeException: Version 'v1beta3' not supported for kind 'Status'
at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:111)
at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:95)
at com.openshift.internal.restclient.DefaultClient.handleHttpClientException(DefaultClient.java:354)
at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:116)
at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:97)
at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:92)
at org.jboss.tools.openshift.core.connection.Connection.get(Connection.java:265)
at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:67)
at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:124)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.RuntimeException: Version 'v1beta3' not supported for kind 'Status'
at com.openshift.internal.restclient.model.properties.ResourcePropertiesRegistry.get(ResourcePropertiesRegistry.java:135)
at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:107)
... 9 more
{code}
was:
# ASSERT: make sure you're using the latest openshift origin code from github (https://github.com/openshift/origin.git)
# EXEC: create a new connection (with the credentials that you have set to the server) and hit "Finish"
# ASSERT: the connection dialog closes
Result:
You get an error dialog popping up telling you that the connection was refused
!connection-refused.png!
> Explorer: Resources cannot be listed when using latest OpenShift origin v3 code
> -------------------------------------------------------------------------------
>
> Key: JBIDE-19601
> URL: https://issues.jboss.org/browse/JBIDE-19601
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.3.0.Alpha2
>
> Attachments: connection-refused.png
>
>
> When using the latest origin code from github one can connect but once the connection wizard is closed an error dialog pops up telling you that the connection was refused
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19597) add google tag manager to website
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19597?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19597:
---------------------------------------------
pushed change to master and production so it can be verified by jboss.org team.
> add google tag manager to website
> ---------------------------------
>
> Key: JBIDE-19597
> URL: https://issues.jboss.org/browse/JBIDE-19597
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
>
> Asked by jboss.org to add the following:
> {code}
> Option 1: You have an existing GA (Google Analytics) account you want to keep using. You should upgrade your GA account to use UA (Universal Analytics).
> <script>dataLayer = [{'channel' : ‘<insert project name here>’, ‘additional_tracking_code’ : ‘<insert optional additional GA tracking code here>'}];</script>
> <!-- Google Tag Manager -->
> <noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-NJWS5L"
> height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
> <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
> new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
> j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
> '//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
> })(window,document,'script','dataLayer','GTM-NJWS5L');</script>
> <!-- End Google Tag Manager —>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3285:
-------------------------------------------
core.
> Easy Import of non-eclipse projects
> -----------------------------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
> Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3404:
-------------------------------------------
I blame tern because it is the exact same error and it lists angularjs/tern in the list.
> Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
> --------------------------------------------------------
>
> Key: JBDS-3404
> URL: https://issues.jboss.org/browse/JBDS-3404
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
> Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png
>
>
> When you do Check for update, only thym update is offered:
> !Screenshot 2015-04-13 14.03.50.png!
> Output when you do Install/Check All
> {code}
> Your original request has been modified.
> "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3)
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBTIS-427) correct individual certification id for modeshape and teiid
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-427:
--------------------------------
Summary: correct individual certification id for modeshape and teiid
Key: JBTIS-427
URL: https://issues.jboss.org/browse/JBTIS-427
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 4.2.1.Final
Reporter: Paul Leacu
Assignee: Paul Leacu
Priority: Minor
Fix For: 4.2.1.Final
The major categories are fine - just the individual category ids for modeshape and teiid
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3404:
-------------------------------------
This issue needs some more info to replicate:
1. List of installed root features form Help->Installation Details
2. List of all available p2 repositories from Hepp->Preferences->Install/Update->Available Software Sites
3. Screenshot for First Step of Install dialog
> Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
> --------------------------------------------------------
>
> Key: JBDS-3404
> URL: https://issues.jboss.org/browse/JBDS-3404
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
> Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png
>
>
> When you do Check for update, only thym update is offered:
> !Screenshot 2015-04-13 14.03.50.png!
> Output when you do Install/Check All
> {code}
> Your original request has been modified.
> "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3)
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ]
Victor Rubezhny commented on JBDS-3404:
---------------------------------------
thym optionally depends on org.jboss.tools.jst.jsdt:
https://github.com/jbosstools/jbosstools-aerogear/blob/master/cordova/plu...
> Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
> --------------------------------------------------------
>
> Key: JBDS-3404
> URL: https://issues.jboss.org/browse/JBDS-3404
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
> Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png
>
>
> When you do Check for update, only thym update is offered:
> !Screenshot 2015-04-13 14.03.50.png!
> Output when you do Install/Check All
> {code}
> Your original request has been modified.
> "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3)
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3404:
-------------------------------------
Cannot replicate using steps to reproduce under Linux:
1. Installed 9.0.0.Alpha1-v20150216-1042-B11
2. Added update site
3. Checked for update and get suggestion to update to
JBoss Developer Studio (Branded Product) 9.0.0.Alpha2-v20150415-1632-B2957
4. Opened Install dialog and selected nightly site from ^ (2)
"Select All", "Next" sequence works
Deselect "Group Items by category" , "Select All", "Next" works as well
What am I doing wrong? :)
> Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
> --------------------------------------------------------
>
> Key: JBDS-3404
> URL: https://issues.jboss.org/browse/JBDS-3404
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
> Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png
>
>
> When you do Check for update, only thym update is offered:
> !Screenshot 2015-04-13 14.03.50.png!
> Output when you do Install/Check All
> {code}
> Your original request has been modified.
> "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3)
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19600) HTML5 Palette: Java crash while attempt to create WebKit browser on Windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19600?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-19600:
----------------------------------------
We didn't face this issue before. It used to work when we tested it for Luna releases. But anyway it seems that it would be much safer for us to switch to the default browser for all palette wizards and not to try to load any specific browser to avoid such crashes.
> HTML5 Palette: Java crash while attempt to create WebKit browser on Windows
> ---------------------------------------------------------------------------
>
> Key: JBIDE-19600
> URL: https://issues.jboss.org/browse/JBIDE-19600
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha2
> Environment: Windows 8, eclipse-SDK-4.5M6-win32 Mars (32bit)
> Reporter: Daniel Azarov
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
> Fix For: 4.3.0.Alpha2
>
>
> if one of the following wizards run first:
> NewRangeSliderWizardPage
> NewTableWizardPage (html)
> NewTableWizardPage (jquery)
> NewTabsWizardPage
> NewHeadingWizardPage
> NewPanelWizardPage
> NewMeterWizardPage
> NewSpinnerWizardPage
> Java Crashes:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00c0e58c, pid=8152, tid=4044
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) Client VM (24.79-b02 mixed mode windows-x86 )
> # Problematic frame:
> # C 0x00c0e58c
> #
> # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
> #
> # An error report file with more information is saved as:
> # C:\Users\Daniil\Java\eclipse-SDK-4.5M6 Mars\hs_err_pid8152.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19600) HTML5 Palette: Java crash while attempt to create WebKit browser on Windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19600?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19600:
-----------------------------------
Fix Version/s: 4.3.0.Alpha2
> HTML5 Palette: Java crash while attempt to create WebKit browser on Windows
> ---------------------------------------------------------------------------
>
> Key: JBIDE-19600
> URL: https://issues.jboss.org/browse/JBIDE-19600
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha2
> Environment: Windows 8, eclipse-SDK-4.5M6-win32 Mars (32bit)
> Reporter: Daniel Azarov
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
> Fix For: 4.3.0.Alpha2
>
>
> if one of the following wizards run first:
> NewRangeSliderWizardPage
> NewTableWizardPage (html)
> NewTableWizardPage (jquery)
> NewTabsWizardPage
> NewHeadingWizardPage
> NewPanelWizardPage
> NewMeterWizardPage
> NewSpinnerWizardPage
> Java Crashes:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00c0e58c, pid=8152, tid=4044
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) Client VM (24.79-b02 mixed mode windows-x86 )
> # Problematic frame:
> # C 0x00c0e58c
> #
> # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
> #
> # An error report file with more information is saved as:
> # C:\Users\Daniil\Java\eclipse-SDK-4.5M6 Mars\hs_err_pid8152.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19600) HTML5 Palette: Java crash while attempt to create WebKit browser on Windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19600?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-19600:
--------------------------------------
Assignee: Viacheslav Kabanovich
> HTML5 Palette: Java crash while attempt to create WebKit browser on Windows
> ---------------------------------------------------------------------------
>
> Key: JBIDE-19600
> URL: https://issues.jboss.org/browse/JBIDE-19600
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha2
> Environment: Windows 8, eclipse-SDK-4.5M6-win32 Mars (32bit)
> Reporter: Daniel Azarov
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
>
> if one of the following wizards run first:
> NewRangeSliderWizardPage
> NewTableWizardPage (html)
> NewTableWizardPage (jquery)
> NewTabsWizardPage
> NewHeadingWizardPage
> NewPanelWizardPage
> NewMeterWizardPage
> NewSpinnerWizardPage
> Java Crashes:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00c0e58c, pid=8152, tid=4044
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) Client VM (24.79-b02 mixed mode windows-x86 )
> # Problematic frame:
> # C 0x00c0e58c
> #
> # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
> #
> # An error report file with more information is saved as:
> # C:\Users\Daniil\Java\eclipse-SDK-4.5M6 Mars\hs_err_pid8152.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19600) HTML5 Palette: Java crash while attempt to create WebKit browser on Windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19600?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19600:
-----------------------------------
Summary: HTML5 Palette: Java crash while attempt to create WebKit browser on Windows (was: HTML5 Palette: Java crash while attempt to create WebKit browser )
> HTML5 Palette: Java crash while attempt to create WebKit browser on Windows
> ---------------------------------------------------------------------------
>
> Key: JBIDE-19600
> URL: https://issues.jboss.org/browse/JBIDE-19600
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha2
> Environment: Windows 8, eclipse-SDK-4.5M6-win32 Mars (32bit)
> Reporter: Daniel Azarov
> Priority: Blocker
>
> if one of the following wizards run first:
> NewRangeSliderWizardPage
> NewTableWizardPage (html)
> NewTableWizardPage (jquery)
> NewTabsWizardPage
> NewHeadingWizardPage
> NewPanelWizardPage
> NewMeterWizardPage
> NewSpinnerWizardPage
> Java Crashes:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00c0e58c, pid=8152, tid=4044
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) Client VM (24.79-b02 mixed mode windows-x86 )
> # Problematic frame:
> # C 0x00c0e58c
> #
> # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
> #
> # An error report file with more information is saved as:
> # C:\Users\Daniil\Java\eclipse-SDK-4.5M6 Mars\hs_err_pid8152.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19600) HTML5 Palette: Java crash while attempt to create WebKit browser
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19600?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19600:
-----------------------------------
Affects Version/s: 4.3.0.Alpha2
> HTML5 Palette: Java crash while attempt to create WebKit browser
> -----------------------------------------------------------------
>
> Key: JBIDE-19600
> URL: https://issues.jboss.org/browse/JBIDE-19600
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha2
> Environment: Windows 8, eclipse-SDK-4.5M6-win32 Mars (32bit)
> Reporter: Daniel Azarov
> Priority: Blocker
>
> if one of the following wizards run first:
> NewRangeSliderWizardPage
> NewTableWizardPage (html)
> NewTableWizardPage (jquery)
> NewTabsWizardPage
> NewHeadingWizardPage
> NewPanelWizardPage
> NewMeterWizardPage
> NewSpinnerWizardPage
> Java Crashes:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00c0e58c, pid=8152, tid=4044
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) Client VM (24.79-b02 mixed mode windows-x86 )
> # Problematic frame:
> # C 0x00c0e58c
> #
> # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
> #
> # An error report file with more information is saved as:
> # C:\Users\Daniil\Java\eclipse-SDK-4.5M6 Mars\hs_err_pid8152.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19600) HTML5 Palette: Java crash while attempt to create WebKit browser
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19600?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19600:
-----------------------------------
Priority: Blocker (was: Major)
> HTML5 Palette: Java crash while attempt to create WebKit browser
> -----------------------------------------------------------------
>
> Key: JBIDE-19600
> URL: https://issues.jboss.org/browse/JBIDE-19600
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Environment: Windows 8, eclipse-SDK-4.5M6-win32 Mars (32bit)
> Reporter: Daniel Azarov
> Priority: Blocker
>
> if one of the following wizards run first:
> NewRangeSliderWizardPage
> NewTableWizardPage (html)
> NewTableWizardPage (jquery)
> NewTabsWizardPage
> NewHeadingWizardPage
> NewPanelWizardPage
> NewMeterWizardPage
> NewSpinnerWizardPage
> Java Crashes:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00c0e58c, pid=8152, tid=4044
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) Client VM (24.79-b02 mixed mode windows-x86 )
> # Problematic frame:
> # C 0x00c0e58c
> #
> # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
> #
> # An error report file with more information is saved as:
> # C:\Users\Daniil\Java\eclipse-SDK-4.5M6 Mars\hs_err_pid8152.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19600) HTML5 Palette: Java crash while attempt to create WebKit browser
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-19600:
-------------------------------------
Summary: HTML5 Palette: Java crash while attempt to create WebKit browser
Key: JBIDE-19600
URL: https://issues.jboss.org/browse/JBIDE-19600
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml/html source editing
Environment: Windows 8, eclipse-SDK-4.5M6-win32 Mars (32bit)
Reporter: Daniel Azarov
if one of the following wizards run first:
NewRangeSliderWizardPage
NewTableWizardPage (html)
NewTableWizardPage (jquery)
NewTabsWizardPage
NewHeadingWizardPage
NewPanelWizardPage
NewMeterWizardPage
NewSpinnerWizardPage
Java Crashes:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00c0e58c, pid=8152, tid=4044
#
# JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
# Java VM: Java HotSpot(TM) Client VM (24.79-b02 mixed mode windows-x86 )
# Problematic frame:
# C 0x00c0e58c
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Daniil\Java\eclipse-SDK-4.5M6 Mars\hs_err_pid8152.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19600) HTML5 Palette: Java crash while attempt to create WebKit browser
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19600?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19600:
----------------------------------
Description:
if one of the following wizards run first:
NewRangeSliderWizardPage
NewTableWizardPage (html)
NewTableWizardPage (jquery)
NewTabsWizardPage
NewHeadingWizardPage
NewPanelWizardPage
NewMeterWizardPage
NewSpinnerWizardPage
Java Crashes:
{code}
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00c0e58c, pid=8152, tid=4044
#
# JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
# Java VM: Java HotSpot(TM) Client VM (24.79-b02 mixed mode windows-x86 )
# Problematic frame:
# C 0x00c0e58c
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Daniil\Java\eclipse-SDK-4.5M6 Mars\hs_err_pid8152.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
{code}
was:
if one of the following wizards run first:
NewRangeSliderWizardPage
NewTableWizardPage (html)
NewTableWizardPage (jquery)
NewTabsWizardPage
NewHeadingWizardPage
NewPanelWizardPage
NewMeterWizardPage
NewSpinnerWizardPage
Java Crashes:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00c0e58c, pid=8152, tid=4044
#
# JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
# Java VM: Java HotSpot(TM) Client VM (24.79-b02 mixed mode windows-x86 )
# Problematic frame:
# C 0x00c0e58c
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Daniil\Java\eclipse-SDK-4.5M6 Mars\hs_err_pid8152.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
> HTML5 Palette: Java crash while attempt to create WebKit browser
> -----------------------------------------------------------------
>
> Key: JBIDE-19600
> URL: https://issues.jboss.org/browse/JBIDE-19600
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Environment: Windows 8, eclipse-SDK-4.5M6-win32 Mars (32bit)
> Reporter: Daniel Azarov
>
> if one of the following wizards run first:
> NewRangeSliderWizardPage
> NewTableWizardPage (html)
> NewTableWizardPage (jquery)
> NewTabsWizardPage
> NewHeadingWizardPage
> NewPanelWizardPage
> NewMeterWizardPage
> NewSpinnerWizardPage
> Java Crashes:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00c0e58c, pid=8152, tid=4044
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) Client VM (24.79-b02 mixed mode windows-x86 )
> # Problematic frame:
> # C 0x00c0e58c
> #
> # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
> #
> # An error report file with more information is saved as:
> # C:\Users\Daniil\Java\eclipse-SDK-4.5M6 Mars\hs_err_pid8152.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ]
Denis Golovin edited comment on JBDS-3404 at 4/15/15 2:29 PM:
--------------------------------------------------------------
Why blame tern? It is not possible to install any update to any feature included into JBoss Developer Studio (Branded product) without updating it itself. I don't see branded product in list above. It happens, I guess, because it is not categorized in JBDS p2 repository.
was (Author: dgolovin):
Why blame tern? It is not possible install any update to any feature included into JBoss Developer Studio (Branded product) without updating it itself. I don't see branded product in list above. It happens, I guess, because it is not categorized in JBDS p2 repository.
> Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
> --------------------------------------------------------
>
> Key: JBDS-3404
> URL: https://issues.jboss.org/browse/JBDS-3404
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
> Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png
>
>
> When you do Check for update, only thym update is offered:
> !Screenshot 2015-04-13 14.03.50.png!
> Output when you do Install/Check All
> {code}
> Your original request has been modified.
> "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3)
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3404:
-------------------------------------
Why blame tern? It is not possiible install any update to any feature included into JBoss Developer Studio (Branded product) without updating it itself. I don't see branded product in list above. It happens, I guess, because it is not categorized in JBDS p2 repository.
> Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
> --------------------------------------------------------
>
> Key: JBDS-3404
> URL: https://issues.jboss.org/browse/JBDS-3404
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
> Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png
>
>
> When you do Check for update, only thym update is offered:
> !Screenshot 2015-04-13 14.03.50.png!
> Output when you do Install/Check All
> {code}
> Your original request has been modified.
> "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3)
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ]
Denis Golovin edited comment on JBDS-3404 at 4/15/15 2:29 PM:
--------------------------------------------------------------
Why blame tern? It is not possible install any update to any feature included into JBoss Developer Studio (Branded product) without updating it itself. I don't see branded product in list above. It happens, I guess, because it is not categorized in JBDS p2 repository.
was (Author: dgolovin):
Why blame tern? It is not possiible install any update to any feature included into JBoss Developer Studio (Branded product) without updating it itself. I don't see branded product in list above. It happens, I guess, because it is not categorized in JBDS p2 repository.
> Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
> --------------------------------------------------------
>
> Key: JBDS-3404
> URL: https://issues.jboss.org/browse/JBDS-3404
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
> Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png
>
>
> When you do Check for update, only thym update is offered:
> !Screenshot 2015-04-13 14.03.50.png!
> Output when you do Install/Check All
> {code}
> Your original request has been modified.
> "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3)
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-15884:
--------------------------------
Sprint: Sprint #2 April 2015
> Allow the runBrowserSim command to accept a URL as a parameter
> --------------------------------------------------------------
>
> Key: JBIDE-15884
> URL: https://issues.jboss.org/browse/JBIDE-15884
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.0.Final
> Reporter: Vineet Reynolds
> Assignee: Ilya Buziuk
> Priority: Minor
> Fix For: 4.3.x
>
>
> Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected.
> When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
