[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19757:
-------------------------------
Summary: Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery (was: Consider using main JBT site for server discovery)
> Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-19757
> URL: https://issues.jboss.org/browse/JBIDE-19757
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, server
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
>
> With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml.
> Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... )
> In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery.
> However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing
> {code}
> !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088
> !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null".
> {code}
> because we are lines specifying bundle but no version in the site.xml.
> [~nickboldt] What are those site.xml useful for? Could we get rid of them?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19757) Consider using main JBT site for server discovery
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-19757:
----------------------------------
Assignee: Nick Boldt
> Consider using main JBT site for server discovery
> -------------------------------------------------
>
> Key: JBIDE-19757
> URL: https://issues.jboss.org/browse/JBIDE-19757
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, server
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
>
> With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml.
> Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... )
> In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery.
> However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing
> {code}
> !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088
> !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null".
> {code}
> because we are lines specifying bundle but no version in the site.xml.
> [~nickboldt] What are those site.xml useful for? Could we get rid of them?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19729) Version Auditing
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19729?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19729:
-------------------------------
Fix Version/s: 4.3.0.Final
> Version Auditing
> ----------------
>
> Key: JBIDE-19729
> URL: https://issues.jboss.org/browse/JBIDE-19729
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Fix For: 4.3.0.Final
>
>
> Epic to track issues related to auditing and quality control.
> This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19729) Version Auditing
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19729?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-19729:
----------------------------------
Assignee: Nick Boldt
> Version Auditing
> ----------------
>
> Key: JBIDE-19729
> URL: https://issues.jboss.org/browse/JBIDE-19729
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Final
>
>
> Epic to track issues related to auditing and quality control.
> This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19743) Execution of criteria query shows <null> result
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19743?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-19743.
-------------------------------
Resolution: Done
> Execution of criteria query shows <null> result
> -----------------------------------------------
>
> Key: JBIDE-19743
> URL: https://issues.jboss.org/browse/JBIDE-19743
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Beta1
> Environment: JBDS 9.0.0.Beta1 - nightly 20150430, L64
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> There is null result after executing Criteria query:
> {code}
> !ENTRY org.jboss.tools.hibernate.runtime.common 4 0 2015-04-30 15:16:16.562
> !MESSAGE org.hibernate.impl.CriteriaImpl.setMaxResults()
> !STACK 0
> java.lang.NoSuchMethodException: org.hibernate.impl.CriteriaImpl.setMaxResults()
> 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.AbstractCriteriaFacade.list(AbstractCriteriaFacade.java:39)
> 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 bsh.Reflect.invokeMethod(Unknown Source)
> at bsh.Reflect.invokeObjectMethod(Unknown Source)
> at bsh.BSHPrimarySuffix.doName(Unknown Source)
> at bsh.BSHPrimarySuffix.doSuffix(Unknown Source)
> at bsh.BSHPrimaryExpression.eval(Unknown Source)
> at bsh.BSHPrimaryExpression.eval(Unknown Source)
> at bsh.Interpreter.eval(Unknown Source)
> at bsh.Interpreter.eval(Unknown Source)
> at bsh.Interpreter.eval(Unknown Source)
> at org.hibernate.eclipse.console.common.JavaPage.setSession(JavaPage.java:73)
> at org.hibernate.eclipse.console.common.HibernateExtension$3.execute(HibernateExtension.java:127)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.eclipse.console.common.HibernateExtension.execute(HibernateExtension.java:189)
> at org.hibernate.eclipse.console.common.HibernateExtension.executeCriteriaQuery(HibernateExtension.java:123)
> at org.hibernate.console.ConsoleConfiguration.executeBSHQuery(ConsoleConfiguration.java:313)
> at org.hibernate.eclipse.criteriaeditor.CriteriaEditor.executeQuery(CriteriaEditor.java:142)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:82)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
> 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$6.handleEvent(ActionContributionItem.java:462)
> 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.Widget.sendEvent(Widget.java:1346)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1331)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1116)
> at org.jboss.reddeer.core.handler.WidgetHandler$4.run(WidgetHandler.java:332)
> at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:193)
> at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:1)
> at org.jboss.reddeer.core.util.Display$ErrorHandlingRunnable.run(Display.java:159)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3790)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months