April 2015 - jbosstools-issues - Jboss List Archives

[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)

9 years

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)

9 years

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)

9 years

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)

9 years

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)

9 years

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)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19700) Support @BatchProperty qualifiers for injected beans

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19700?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19700: -------------------------------------- Assignee: Daniel Azarov (was: Viacheslav Kabanovich) Validation (see the step #3 in the description above) is done as part of https://github.com/jbosstools/jbosstools-javaee/pull/325 [~dazarov] please create OpenOn for this injection point. > Support @BatchProperty qualifiers for injected beans > ---------------------------------------------------- > > Key: JBIDE-19700 > URL: https://issues.jboss.org/browse/JBIDE-19700 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch, cdi-extensions > Affects Versions: 4.3.0.Alpha2 > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > > You can find an example of such beans 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/RecordsReader.java > 3. There should not be warning messages about no eligible beans for *separatorRegex* and *fileName* properties. > 4. OpenOns for these properties should open import-file.xml and select the corresponding properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

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: ----------------------------------- Description: 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} was: 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} 4. I guess this is a built-in CDI bean ([~scabanovich] please double check it). If so, the Ctrl+Click on this injection should open javax.batch.runtime.context.JobContext interface. > 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)

9 years

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: ------------------------------------ The IS target platform POM references the JBoss parent POM - no references in IS to the jbosstools-build parent POM. > 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)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19571) Add FSW to downloadable runtimes

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19571?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19571: ------------------------------------- [~mmalina] JBT will use a custom 'installer' which, rather than simply 'extracting' will run java -jar (the-file). This will run the installer. One possible area of improvement which isn't there yet is that if the user selects a different installation folder during the installer, I could parse the installation log to get this value and then allow runtime detection to continue properly. As of now, it will run the installer, and, if the user selects the same folder in the installer as he did in the jbt wizard, it will also locate the runtime / server after installation. If the user selects a different folder, though, then it won't. Another possible area of improvement would be that we could ask that installers in the future allow for a sysprop that would set the default install location, and we could run java -jar {file} -Ddefault.install.dir={value_from_wizard} But yeah... as of now... it could use some work. > Add FSW to downloadable runtimes > -------------------------------- > > Key: JBIDE-19571 > URL: https://issues.jboss.org/browse/JBIDE-19571 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > FSW 6.0 is not available in download runtimes -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2015