April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3431) Update JBDS support matrix to include only major version of EAP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3431?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3431: ---------------------------------- I've added JBDS 9 to the tables [1], as a clone of what we did for 8.1. However, JBDS 9 adds support for WFLY 8.2 and 9.0, plus will eventually support EAP 7 when it is released. If you see anything wrong there, let me know. [1] https://developer.jboss.org/wiki/MatrixOfSupportedPlatformsRuntimesAndTec... > Update JBDS support matrix to include only major version of EAP > --------------------------------------------------------------- > > Key: JBDS-3431 > URL: https://issues.jboss.org/browse/JBDS-3431 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 8.1.0.GA > Reporter: Mustafa Musaji > Assignee: Misha Ali > > Update this page https://access.redhat.com/articles/427493 > So that we only include the major versions of EAP supported > I.e. 4.x, 5.x and 6.x -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19746) Support javax.batch.runtime.context.StepContext injections

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19746?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-19746: ------------------------------------------ Description: 1. Import https://github.com/jboss-developer/jboss-sandbox-quickstarts/ as an exisitng maven project 2. Create a Batch artifact type. 3. Insert injection {code:java} @Inject private StepContext jobContext; {code} There should not be a warning message about no eligible beans for it. > Support javax.batch.runtime.context.StepContext injections > ---------------------------------------------------------- > > Key: JBIDE-19746 > URL: https://issues.jboss.org/browse/JBIDE-19746 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch > Affects Versions: 4.3.0.Alpha2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > > 1. Import https://github.com/jboss-developer/jboss-sandbox-quickstarts/ as an exisitng maven project > 2. Create a Batch artifact type. > 3. Insert injection > {code:java} > @Inject > private StepContext jobContext; > {code} > There should not be a warning message about no eligible beans for it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19744) jbosstools-build has both 4.2.x and 4.2.X and with different content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19744?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19744: ------------------------------------ JBoss parent pom != JBoss Tools parent pom, so you're fine there. And since you're using our target platform by version (not indirectly via our parent pom) you're already using the 4.42.0.Final released version rather than the -SNAPSHOT one. TL;DR, you're fine. [~maxandersen] [~mickael_istria], please approve this PR: https://github.com/jbosstools/jbosstools-build/pull/183 so we can delete the .X (upper case) branch. > jbosstools-build has both 4.2.x and 4.2.X and with different content > -------------------------------------------------------------------- > > Key: JBIDE-19744 > URL: https://issues.jboss.org/browse/JBIDE-19744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Final > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.2.3.Final > > > Both https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.X and https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.x exist. > The difference is shown here: https://github.com/jbosstools/jbosstools-build/compare/jbosstools-4.2.x..... > indicating that 4.2.x builds are *not* using the released version of TP to build against - only snapshot (which should not be there if TP was released) > We should get the 4.2.X deleted, but before we do - what do we do about the missing commit on 4.2.x ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19747) IllegalArgumentException when creating new batch job xml file

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-19747: -------------------------------------- Summary: IllegalArgumentException when creating new batch job xml file Key: JBIDE-19747 URL: https://issues.jboss.org/browse/JBIDE-19747 Project: Tools (JBoss Tools) Issue Type: Bug Components: batch Affects Versions: 4.3.0.Beta1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.3.0.Beta1 1. File->New->Batch->Job XML File 2. Click on any project (root folder): {code} java.lang.IllegalArgumentException: Path must include project and resource name: /BatchTestProject at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2069) at org.eclipse.core.internal.resources.Container.getFolder(Container.java:201) at org.jboss.tools.batch.ui.internal.wizard.NewJobXMLCreationWizard$WizardNewBeansXMLFileCreationPage.validatePage(NewJobXMLCreationWizard.java:367) at org.eclipse.ui.dialogs.WizardNewFileCreationPage.handleEvent(WizardNewFileCreationPage.java:687) at org.eclipse.ui.internal.ide.misc.ResourceAndContainerGroup.handleEvent(ResourceAndContainerGroup.java:369) 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:1327) at org.eclipse.swt.widgets.Text.setText(Text.java:2560) at org.eclipse.swt.widgets.Text.setText(Text.java:2486) at org.eclipse.ui.internal.ide.misc.ContainerSelectionGroup.containerSelectionChanged(ContainerSelectionGroup.java:190) at org.eclipse.ui.internal.ide.misc.ContainerSelectionGroup$1.selectionChanged(ContainerSelectionGroup.java:277) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163) 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.viewers.Viewer.fireSelectionChanged(Viewer.java:160) at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197) at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228) at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257) at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242) at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408) 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} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19746) Support javax.batch.runtime.context.StepContext injections

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-19746: --------------------------------------------- Summary: Support javax.batch.runtime.context.StepContext injections Key: JBIDE-19746 URL: https://issues.jboss.org/browse/JBIDE-19746 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: batch Affects Versions: 4.3.0.Alpha2 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.3.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19744) jbosstools-build has both 4.2.x and 4.2.X and with different content

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19744?page=com.atlassian.jira.plugi... ] Paul Leacu commented on JBIDE-19744: ------------------------------------ I reference the 4.42.0.Final JBT core TP deps here: https://github.com/jbosstools/jbosstools-integration-stack/blob/jbosstool... ref: https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... and I reference the JBoss parent POM here: https://github.com/jbosstools/jbosstools-integration-stack/blob/jbosstool... Is that okay? > jbosstools-build has both 4.2.x and 4.2.X and with different content > -------------------------------------------------------------------- > > Key: JBIDE-19744 > URL: https://issues.jboss.org/browse/JBIDE-19744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Final > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.2.3.Final > > > Both https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.X and https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.x exist. > The difference is shown here: https://github.com/jbosstools/jbosstools-build/compare/jbosstools-4.2.x..... > indicating that 4.2.x builds are *not* using the released version of TP to build against - only snapshot (which should not be there if TP was released) > We should get the 4.2.X deleted, but before we do - what do we do about the missing commit on 4.2.x ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19742) Change color of B in batch Icon

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19742?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19742: ---------------------------------- Attachment: NewBatchIcon.png > Change color of B in batch Icon > ------------------------------- > > Key: JBIDE-19742 > URL: https://issues.jboss.org/browse/JBIDE-19742 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Alpha2 > Reporter: Fred Bricon > Assignee: Daniel Azarov > Priority: Minor > Fix For: 4.3.0.Beta1 > > Attachments: NewBatchIcon.png > > > My brains keeps processing the red B of !https://raw.githubusercontent.com/jbosstools/jbosstools-javaee/03d08a6ffea565dca1207dc37d8ff1d213f4ab28/batch/plugins/org.jboss.tools.batch.ui/images/batch_icon16.png! as an error marker every time I see it. > Could we please use another color? Blue or dark Green, nothing too bright. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19717) Visual (diagram) editor for JSR-352 batch job files.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19717?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19717: ----------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.x) > Visual (diagram) editor for JSR-352 batch job files. > ---------------------------------------------------- > > Key: JBIDE-19717 > URL: https://issues.jboss.org/browse/JBIDE-19717 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch > Affects Versions: 4.3.0.Alpha1 > Reporter: Tomáš Milata > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > > A *visual* editor which allows users to *graphically draw* structure of a JSR-352 batch job xml file. > Existing Sapphire model makes it easy to create a new Sapphire diagram editor that works together with the existing tree editor. > While the existing tree editor is efficient for editing properties of *single element*, the diagram editor should serve as a useful *visualization* tool that helps with orientation in complex flow *strucures*. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19744) jbosstools-build has both 4.2.x and 4.2.X and with different content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19744?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19744: ------------------------------------ Ah, so you mean you reference this: https://github.com/jbosstools/jbosstools-build/blob/jbosstools-4.2.x/pare... not this: https://github.com/jbosstools/jbosstools-build/blob/jbosstools-4.2.x/pare... (They're the same thing. jbosstools-build is the project in which the parent pom lives.) > jbosstools-build has both 4.2.x and 4.2.X and with different content > -------------------------------------------------------------------- > > Key: JBIDE-19744 > URL: https://issues.jboss.org/browse/JBIDE-19744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Final > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.2.3.Final > > > Both https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.X and https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.x exist. > The difference is shown here: https://github.com/jbosstools/jbosstools-build/compare/jbosstools-4.2.x..... > indicating that 4.2.x builds are *not* using the released version of TP to build against - only snapshot (which should not be there if TP was released) > We should get the 4.2.X deleted, but before we do - what do we do about the missing commit on 4.2.x ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19701) Support javax.batch.runtime.context.JobContext injections

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19701?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19701: ----------------------------------- Sprint: Sprint #2 April 2015 (was: Sprint #3 May 2015) > Support javax.batch.runtime.context.JobContext injections > --------------------------------------------------------- > > Key: JBIDE-19701 > URL: https://issues.jboss.org/browse/JBIDE-19701 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch, cdi-extensions > Affects Versions: 4.3.0.Alpha2 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > > You can find an example of such injections here: > https://github.com/jboss-developer/jboss-sandbox-quickstarts/blob/master/... > 1. Import https://github.com/jboss-developer/jboss-sandbox-quickstarts/ as an exisitng maven project > 2. Open /batch-processing/src/main/java/org/jboss/as/quickstarts/batch/job/listener/JobListener.java > 3. There should not be a warning message about no eligible beans for: > {code:java} > @Inject > private JobContext jobContext; > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2015