April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-66) Mirror Eclipse BPMN2 Modeler v0.2.5 on jboss tools requirements

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-66?page=com.atlassian.jira.plugin.s... ] Nick Boldt commented on JBTIS-66: --------------------------------- Reason for this respun version of 0.2.5 is best summed up by these comments from [~bbrodt]: {quote} Well folks, up until now I was under the assumption that I was building the bpmn2 editor with the latest version of graphiti 0.10.0-M6 - I did not realize that the MANIFEST.MF bundle-version="[0.8.2,0.10.0] does NOT include M6 (whodathunkit?) So this bpmn2 editor migration to the version of graphiti that will ship with kepler is going to take longer than I thought. This API change affects about 20 or so classes and there ain't no going back. This means I'll have to maintain 3 different code bases for helios, indigo/juno, and kepler. The best, short-term solution is that we continue to use graphiti 0.9.2 for both juno and kepler builds until kepler releases in June. That will give me time to work on a new branch for graphiti 0.10.x. ---- I'm going to change the bpmn2 editor manifest files to require [0.8.2,0.11.0] but the project pom will still have this repo definition for kepler builds: <repository> <id>eclipse-graphiti-kepler</id> <url>http://download.eclipse.org/graphiti/updates/milestones/S-0.10.0M6-201303...</url> <layout>p2</layout> <snapshots> <enabled>true</enabled> </snapshots> <releases> <enabled>true</enabled> </releases> </repository> and update this as graphiti & kepler get to their release dates. {quote} > Mirror Eclipse BPMN2 Modeler v0.2.5 on jboss tools requirements > --------------------------------------------------------------- > > Key: JBTIS-66 > URL: https://issues.jboss.org/browse/JBTIS-66 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: releng, switchyard, target-platform > Affects Versions: 4.0.0 > Reporter: Robert (Bob) Brodt > Assignee: Robert (Bob) Brodt > Fix For: 4.0.0 > > > Here is the site URL: http://download.eclipse.org/bpmn2-modeler/site/0.2.5/ > This is required for SwitchYard 0.8. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-66) Mirror Eclipse BPMN2 Modeler v0.2.5 on jboss tools requirements

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-66?page=com.atlassian.jira.plugin.s... ] Nick Boldt edited comment on JBTIS-66 at 4/27/13 8:06 AM: ---------------------------------------------------------- {color:red}*Previous mirror (depends on Graphiti 0.9; won't resolve Graphiti 0.10 due to bad upper bound):*{color} http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/2... {color:green}*New mirror (should fix upper bound restriction on dependency on Graphiti 0.10):*{color} http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/2... Questions: a) Why does each maintenance release live in a different URL? Why not just add the new content via composite site metadata to http://download.eclipse.org/bpmn2-modeler/site/ instead of http://download.eclipse.org/bpmn2-modeler/site/0.2.5/ b) Do you plan to drop a new maintenance release every 3 weeks? The last update was 0.2.4 on 2013-04-09 @ 22:17. c) What's in 0.2.5 that SwitchYard *NEEDS* which wasn't in 0.2.4? d) Is there a new release planned for http://download.eclipse.org/bpmn2-modeler/bpmn2/site/ ? The BPMN2 Project Feature 0.7.0.201106271450 hasn't changed in almost 2 years, yet the Modeler/Editor drops a new release every 3 weeks. Thanks! was (Author: nickboldt): Previous mirror (depends on Graphiti 0.9; won't resolve Graphiti 0.10 due to bad upper bound): http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/2... New mirror (should fix upper bound restriction on dependency on Graphiti 0.10): http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/2... Questions: a) Why does each maintenance release live in a different URL? Why not just add the new content via composite site metadata to http://download.eclipse.org/bpmn2-modeler/site/ instead of http://download.eclipse.org/bpmn2-modeler/site/0.2.5/ b) Do you plan to drop a new maintenance release every 3 weeks? The last update was 0.2.4 on 2013-04-09 @ 22:17. c) What's in 0.2.5 that SwitchYard *NEEDS* which wasn't in 0.2.4? d) Is there a new release planned for http://download.eclipse.org/bpmn2-modeler/bpmn2/site/ ? The BPMN2 Project Feature 0.7.0.201106271450 hasn't changed in almost 2 years, yet the Modeler/Editor drops a new release every 3 weeks. Thanks! > Mirror Eclipse BPMN2 Modeler v0.2.5 on jboss tools requirements > --------------------------------------------------------------- > > Key: JBTIS-66 > URL: https://issues.jboss.org/browse/JBTIS-66 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: releng, switchyard, target-platform > Affects Versions: 4.0.0 > Reporter: Robert (Bob) Brodt > Assignee: Robert (Bob) Brodt > Fix For: 4.0.0 > > > Here is the site URL: http://download.eclipse.org/bpmn2-modeler/site/0.2.5/ > This is required for SwitchYard 0.8. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-66) Mirror Eclipse BPMN2 Modeler v0.2.5 on jboss tools requirements

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-66?page=com.atlassian.jira.plugin.s... ] Nick Boldt edited comment on JBTIS-66 at 4/27/13 8:06 AM: ---------------------------------------------------------- Previous mirror (depends on Graphiti 0.9; won't resolve Graphiti 0.10 due to bad upper bound): http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/2... New mirror (should fix upper bound restriction on dependency on Graphiti 0.10): http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/2... Questions: a) Why does each maintenance release live in a different URL? Why not just add the new content via composite site metadata to http://download.eclipse.org/bpmn2-modeler/site/ instead of http://download.eclipse.org/bpmn2-modeler/site/0.2.5/ b) Do you plan to drop a new maintenance release every 3 weeks? The last update was 0.2.4 on 2013-04-09 @ 22:17. c) What's in 0.2.5 that SwitchYard *NEEDS* which wasn't in 0.2.4? d) Is there a new release planned for http://download.eclipse.org/bpmn2-modeler/bpmn2/site/ ? The BPMN2 Project Feature 0.7.0.201106271450 hasn't changed in almost 2 years, yet the Modeler/Editor drops a new release every 3 weeks. Thanks! was (Author: nickboldt): Mirrored here: http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/2... Questions: a) Why does each maintenance release live in a different URL? Why not just add the new content via composite site metadata to http://download.eclipse.org/bpmn2-modeler/site/ instead of http://download.eclipse.org/bpmn2-modeler/site/0.2.5/ b) Do you plan to drop a new maintenance release every 3 weeks? The last update was 0.2.4 on 2013-04-09 @ 22:17. c) What's in 0.2.5 that SwitchYard *NEEDS* which wasn't in 0.2.4? d) Is there a new release planned for http://download.eclipse.org/bpmn2-modeler/bpmn2/site/ ? The BPMN2 Project Feature 0.7.0.201106271450 hasn't changed in almost 2 years, yet the Modeler/Editor drops a new release every 3 weeks. Thanks! > Mirror Eclipse BPMN2 Modeler v0.2.5 on jboss tools requirements > --------------------------------------------------------------- > > Key: JBTIS-66 > URL: https://issues.jboss.org/browse/JBTIS-66 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: releng, switchyard, target-platform > Affects Versions: 4.0.0 > Reporter: Robert (Bob) Brodt > Assignee: Robert (Bob) Brodt > Fix For: 4.0.0 > > > Here is the site URL: http://download.eclipse.org/bpmn2-modeler/site/0.2.5/ > This is required for SwitchYard 0.8. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13877) Test the RichFaces Kitchensink archetype upgrade

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13877?page=com.atlassian.jira.plugi... ] Brian Leathem commented on JBIDE-13877: --------------------------------------- [~fbricon] we've promoted these archetypes out of staging. Can you verify they work with JBIDE so we can update JBoss central? > Test the RichFaces Kitchensink archetype upgrade > ------------------------------------------------ > > Key: JBIDE-13877 > URL: https://issues.jboss.org/browse/JBIDE-13877 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: central > Reporter: Brian Leathem > Assignee: Fred Bricon > > RichFaces kitchensink archetype 4.3.1.Final-2 is currently in a JBoss staging repository. RichFaces QA of the archetype is complete. > The archetype will be promoted out of staging when JBoss tools QA is complete. > Staging repository: > https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14327) org.jboss.tools.project.examples does not compile

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14327?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-14327. ------------------------------------ Assignee: Alexey Kazakov Resolution: Done I reverted https://github.com/jbosstools/jbosstools-base/pull/93 > org.jboss.tools.project.examples does not compile > ------------------------------------------------- > > Key: JBIDE-14327 > URL: https://issues.jboss.org/browse/JBIDE-14327 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, common/jst/core, project-examples, server > Affects Versions: 4.1.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.1.0.Beta1 > > > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.17.0:compile (default-compile) on project org.jboss.tools.project.examples: Compilation failure: Compilation failure: > [ERROR] /home/igels/Projects/jbt-4.0/requests/jbosstools-central/examples/plugins/org.jboss.tools.project.examples/src/org/jboss/tools/project/examples/model/ProjectExampleUtil.java:[836,0] > [ERROR] return ECFTransport.getInstance(); > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] Type mismatch: cannot convert from org.jboss.tools.common.core.ecf.ECFTransport to org.jboss.tools.runtime.core.util.ECFTransport > [ERROR] 1 problem (1 error) > [ERROR] -> [Help 1] > [ERROR] > {code} > It seems that this PR https://github.com/jbosstools/jbosstools-base/pull/93 pushed to master broke the build. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14328) ConfigureProblemSeverity Quick fix is broken for ELValidator problem markers

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-14328: ------------------------------------- Summary: ConfigureProblemSeverity Quick fix is broken for ELValidator problem markers Key: JBIDE-14328 URL: https://issues.jboss.org/browse/JBIDE-14328 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.1.0.Beta1 Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 4.1.0.Beta1 We should add ConfigureProblemSeverityResolutionGenerator for org.jboss.tools.jst.web.kb.elproblem marker type And we definitely need more tests for that -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14326) Escape HTML in user input in wizards

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14326?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-14326: ---------------------------------------- Slava, please add steps to reproduce the issue. > Escape HTML in user input in wizards > ------------------------------------ > > Key: JBIDE-14326 > URL: https://issues.jboss.org/browse/JBIDE-14326 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13654) org.eclipse.core.internal.resources.ResourceException performing Quick Fix from Teiid Designer tooling

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13654?page=com.atlassian.jira.plugi... ] Daniel Azarov edited comment on JBIDE-13654 at 4/26/13 6:03 PM: ---------------------------------------------------------------- Barry, please try my pull request that limits ConfigureProblemSeverityResolutionGenerator to work with only org.jboss.tools.common.validation.JBTValidationProblem. I think it could help. was (Author: dazarov): Burry, please try my pull request that limits ConfigureProblemSeverityResolutionGenerator to work with only org.jboss.tools.common.validation.JBTValidationProblem. I think it could help. > org.eclipse.core.internal.resources.ResourceException performing Quick Fix from Teiid Designer tooling > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13654 > URL: https://issues.jboss.org/browse/JBIDE-13654 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Reporter: Barry LaFond > Assignee: Daniel Azarov > Fix For: 4.1.0.Beta1 > > > Developing a Quick Fix (org.eclipse.ui.ide.markerResolution extension point) for upcoming Teiid Designer 8.1 release. > After performing Quick fix successfully, the following exception is thrown from org.jboss.tools.common.ui.Marker class as the wizard is tearing down (deactivating). > org.eclipse.core.internal.resources.ResourceException: Marker id 89 not found. > at org.eclipse.core.internal.resources.Marker.checkInfo(Marker.java:57) > at org.eclipse.core.internal.resources.Marker.getType(Marker.java:195) > at org.jboss.tools.common.ui.marker.ConfigureProblemSeverityResolutionGenerator.getProblemType(ConfigureProblemSeverityResolutionGenerator.java:140) > at org.jboss.tools.common.ui.marker.ConfigureProblemSeverityResolutionGenerator.hasResolutions(ConfigureProblemSeverityResolutionGenerator.java:124) > at org.eclipse.ui.internal.ide.registry.MarkerHelpRegistry.hasResolution(MarkerHelpRegistry.java:191) > at org.eclipse.ui.internal.ide.registry.MarkerHelpRegistry.hasResolutions(MarkerHelpRegistry.java:160) > at org.eclipse.ui.internal.views.markers.QuickFixPropertyTester.test(QuickFixPropertyTester.java:39) > at org.eclipse.core.internal.expressions.Property.test(Property.java:58) > at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:99) > at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) > at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:150) > at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) > at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:29) > at org.eclipse.ui.internal.services.EvaluationReference.evaluate(EvaluationReference.java:93) > at org.eclipse.ui.internal.services.EvaluationReference.evaluate(EvaluationReference.java:130) > at org.eclipse.ui.internal.services.EvaluationReference.changed(EvaluationReference.java:124) > at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:110) > at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:318) > at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:332) > at org.eclipse.e4.core.internal.contexts.EclipseContext.activate(EclipseContext.java:630) > at org.eclipse.e4.ui.internal.workbench.swt.ShellActivationListener$3.run(ShellActivationListener.java:153) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.swt.ShellActivationListener.deactivate(ShellActivationListener.java:145) > at org.eclipse.e4.ui.internal.workbench.swt.ShellActivationListener.access$0(ShellActivationListener.java:131) > at org.eclipse.e4.ui.internal.workbench.swt.ShellActivationListener$4.widgetDisposed(ShellActivationListener.java:197) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1300) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1281) > at org.eclipse.swt.widgets.Widget.release(Widget.java:1098) > at org.eclipse.swt.widgets.Control.release(Control.java:3529) > at org.eclipse.swt.widgets.Widget.dispose(Widget.java:476) > at org.eclipse.swt.widgets.Shell.dispose(Shell.java:2307) > at org.eclipse.jface.window.Window.close(Window.java:335) > at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:979) > at org.eclipse.jface.wizard.WizardDialog.hardClose(WizardDialog.java:892) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:835) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) > at org.eclipse.jface.window.Window.open(Window.java:801) > at org.eclipse.ui.internal.views.markers.QuickFixHandler.execute(QuickFixHandler.java:165) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:76) > 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:616) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:229) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:210) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:131) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:171) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:814) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:707) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:691) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:630) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) > 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:616) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) > at org.eclipse.equinox.launcher.Main.run(Main.java:1438) > at org.eclipse.equinox.launcher.Main.main(Main.java:1414) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14281) Forge New and Noteworthy for 4.1.0.Alpha2

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14281?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-14281: --------------------------------------- There is no issue for Forge 2 (experimental) support, but we probably should mention that in N&N. > Forge New and Noteworthy for 4.1.0.Alpha2 > ----------------------------------------- > > Key: JBIDE-14281 > URL: https://issues.jboss.org/browse/JBIDE-14281 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Critical > Fix For: 4.1.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14274) Webservices and Rest New and Noteworthy for 4.1.0.Alpha2

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14274?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-14274. ----------------------------------- Resolution: Rejected > Webservices and Rest New and Noteworthy for 4.1.0.Alpha2 > -------------------------------------------------------- > > Key: JBIDE-14274 > URL: https://issues.jboss.org/browse/JBIDE-14274 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Webservices > Reporter: Max Rydahl Andersen > Assignee: Brian Fitzpatrick > Priority: Critical > Fix For: 4.1.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Webservices and Rest is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Webservices and Rest by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2013