[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 updated JBIDE-19743:
------------------------------
Sprint: Sprint #3 May 2015
> 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
[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 reassigned JBIDE-19743:
---------------------------------
Assignee: Koen Aers
> 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
[JBoss JIRA] (JBIDE-19687) Web Service wizard buttons act strangely if an error occurs creating CXF service
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19687?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick resolved JBIDE-19687.
---------------------------------------
Release Notes Docs Status: Not Required
Fix Version/s: 4.3.0.Final
(was: 4.3.0.Beta1)
Resolution: Won't Fix
We have a workaround for this and the issue is in the code upstream. I am hoping it will be fixed in the Mars release if they can do that.
> Web Service wizard buttons act strangely if an error occurs creating CXF service
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19687
> URL: https://issues.jboss.org/browse/JBIDE-19687
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.3.0.Alpha2
> Environment: Fedora 20 x64, openjdk 1.7.0_75
> Reporter: Jan Richter
> Assignee: Brian Fitzpatrick
> Labels: upstream, workaround
> Fix For: 4.3.0.Final
>
> Attachments: errorMessage
>
>
> Trying to create a bottom up Apache CXF web service. If after the "Apache CXF Wbe Service Java2WS Configuration" step an error occurs, the "back" and "next" buttons stop behaving in the expected fashion.
> So far I've found these cases:
> - The back button will loop through the last 3 pages of the wizard, while pressing "next" on any of these pages will return you to the first page.
> - You can return with the back button, but pressing next will open an error dialog with the same message as the original error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19687) Web Service wizard buttons act strangely if an error occurs creating CXF service
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19687?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick updated JBIDE-19687:
--------------------------------------
Fix Version/s: 4.3.0.Beta1
(was: LATER)
> Web Service wizard buttons act strangely if an error occurs creating CXF service
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19687
> URL: https://issues.jboss.org/browse/JBIDE-19687
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.3.0.Alpha2
> Environment: Fedora 20 x64, openjdk 1.7.0_75
> Reporter: Jan Richter
> Assignee: Brian Fitzpatrick
> Labels: upstream, workaround
> Fix For: 4.3.0.Beta1
>
> Attachments: errorMessage
>
>
> Trying to create a bottom up Apache CXF web service. If after the "Apache CXF Wbe Service Java2WS Configuration" step an error occurs, the "back" and "next" buttons stop behaving in the expected fashion.
> So far I've found these cases:
> - The back button will loop through the last 3 pages of the wizard, while pressing "next" on any of these pages will return you to the first page.
> - You can return with the back button, but pressing next will open an error dialog with the same message as the original error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19687) Web Service wizard buttons act strangely if an error occurs creating CXF service
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19687?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick updated JBIDE-19687:
--------------------------------------
Fix Version/s: LATER
> Web Service wizard buttons act strangely if an error occurs creating CXF service
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19687
> URL: https://issues.jboss.org/browse/JBIDE-19687
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.3.0.Alpha2
> Environment: Fedora 20 x64, openjdk 1.7.0_75
> Reporter: Jan Richter
> Assignee: Brian Fitzpatrick
> Labels: upstream, workaround
> Fix For: LATER
>
> Attachments: errorMessage
>
>
> Trying to create a bottom up Apache CXF web service. If after the "Apache CXF Wbe Service Java2WS Configuration" step an error occurs, the "back" and "next" buttons stop behaving in the expected fashion.
> So far I've found these cases:
> - The back button will loop through the last 3 pages of the wizard, while pressing "next" on any of these pages will return you to the first page.
> - You can return with the back button, but pressing next will open an error dialog with the same message as the original error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19734) JAX-RS Validator NPEs with wildcard type arguments
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19734?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick reassigned JBIDE-19734:
-----------------------------------------
Assignee: Xavier Coulon
> JAX-RS Validator NPEs with wildcard type arguments
> --------------------------------------------------
>
> Key: JBIDE-19734
> URL: https://issues.jboss.org/browse/JBIDE-19734
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Environment: Eclipse Mars, JDK 1.7 32-bit
> Reporter: Kory Markevich
> Assignee: Xavier Coulon
>
> JBoss JAX-RS Tools feature version: 1.8.0.Beta1-v20150417-0152-B698
> The JAX-RS validator throws an NPE when using generic types with wildcards. Specifically, the call to typeArgumentBinding.getJavaElement() in SourceType.from(VariableDeclaration) can return null, which the SourceType constructor then tries to use, resulting in the following stack trace. Depending on the code, the validator could trigger this exception as frequently as every pause in typing, resulting in a modal error box popping up constantly. The sample code provided only triggers it on save though.
> java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.core.jdt.SourceType.<init>(SourceType.java:157)
> at org.jboss.tools.ws.jaxrs.core.jdt.SourceType.from(SourceType.java:49)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignature(JdtUtils.java:1109)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResource$Builder.build(JaxrsResource.java:169)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResource.update(JaxrsResource.java:273)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElement(JaxrsMetamodel.java:647)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processResourceChange(JaxrsMetamodel.java:608)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processAffectedResources(JaxrsMetamodel.java:574)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:77)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19734) JAX-RS Validator NPEs with wildcard type arguments
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19734?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-19734:
-------------------------------------------
[~xcoulon] Can you take a look at this one?
> JAX-RS Validator NPEs with wildcard type arguments
> --------------------------------------------------
>
> Key: JBIDE-19734
> URL: https://issues.jboss.org/browse/JBIDE-19734
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Environment: Eclipse Mars, JDK 1.7 32-bit
> Reporter: Kory Markevich
> Assignee: Xavier Coulon
>
> JBoss JAX-RS Tools feature version: 1.8.0.Beta1-v20150417-0152-B698
> The JAX-RS validator throws an NPE when using generic types with wildcards. Specifically, the call to typeArgumentBinding.getJavaElement() in SourceType.from(VariableDeclaration) can return null, which the SourceType constructor then tries to use, resulting in the following stack trace. Depending on the code, the validator could trigger this exception as frequently as every pause in typing, resulting in a modal error box popping up constantly. The sample code provided only triggers it on save though.
> java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.core.jdt.SourceType.<init>(SourceType.java:157)
> at org.jboss.tools.ws.jaxrs.core.jdt.SourceType.from(SourceType.java:49)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignature(JdtUtils.java:1109)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResource$Builder.build(JaxrsResource.java:169)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResource.update(JaxrsResource.java:273)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElement(JaxrsMetamodel.java:647)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processResourceChange(JaxrsMetamodel.java:608)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processAffectedResources(JaxrsMetamodel.java:574)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:77)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19756) jbosstools-src.zip has incomplete/misleading version info in folder names/structure
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19756:
---------------------------------------------
Yes, having jbosstools-4.3.0.Beta1 inside the source folder is fine.
im baffled why there need to be any rebuilds.
Is this not build and controlled with something that is versioned in its pom appropriately and Beta, Final etc. is part of it when being built ?
All our plugins has Final in them without requiring any custom munging.
> jbosstools-src.zip has incomplete/misleading version info in folder names/structure
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-19756
> URL: https://issues.jboss.org/browse/JBIDE-19756
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
> Attachments: jbide19756.png
>
>
> Downloading latest jbosstools-src.zip from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... I see multiple files in root named:
> <componentname>_<buildqualifier>_<sha1>
> example:
> jbosstools-javaee_Beta1-v20150501-0413-B767_149f9a46d5c676fd7119515e8b6aa796859955ad
> A few issues with this:
> a) it would have been nice unzipping would not create multiple root level folders. Maybe have a jbosstools-source folder as root ?
> b) the buildqualifier is there but the version string for the component is not. Either put the full version string for that component (not overall jbosstools version) or just leave it as <component>-<sha> and have the root folder state the full version of jbosstools. since non-indulged user would not know this one had to do with 4.3.0.Beta1 or 4.2.3.Beta1 (for example).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months