December 2014 - jbosstools-issues

[JBoss JIRA] (JBTIS-371) Update JBTIS composites for Luna Beta2

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-371?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-371: ---------------------------------- https://github.com/jbosstools/jbosstools-integration-stack/pull/262 > Update JBTIS composites for Luna Beta2 > -------------------------------------- > > Key: JBTIS-371 > URL: https://issues.jboss.org/browse/JBTIS-371 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 4.2.0.Beta1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.2.0.Beta2 > > > Catch all for updates to the IS composites for Beta2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3215) 3rd party certification for JBDS 8.0.1.GA

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3215?page=com.atlassian.jira.plugin.... ] Len DiMaggio closed JBDS-3215. ------------------------------ > 3rd party certification for JBDS 8.0.1.GA > ----------------------------------------- > > Key: JBDS-3215 > URL: https://issues.jboss.org/browse/JBDS-3215 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform > Affects Versions: 8.0.0.GA > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 8.0.1.GA > > > For JBDS 8.0.1.GA, track changes since JBDS-2869 (8.0.0.GA release). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3215) 3rd party certification for JBDS 8.0.1.GA

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3215?page=com.atlassian.jira.plugin.... ] Len DiMaggio resolved JBDS-3215. -------------------------------- Release Notes Text: Dependent/child JIRAs are closed - closing for 8.0.1 Resolution: Done > 3rd party certification for JBDS 8.0.1.GA > ----------------------------------------- > > Key: JBDS-3215 > URL: https://issues.jboss.org/browse/JBDS-3215 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform > Affects Versions: 8.0.0.GA > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 8.0.1.GA > > > For JBDS 8.0.1.GA, track changes since JBDS-2869 (8.0.0.GA release). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18921) release webtools site for Eclipse 4.3 Mars to so WTP 3.7 discovery upstream can find it

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18921?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18921: --------------------------------------------- Btw. Why not just follow same pattern as last year. Add the http://download.jboss.org/jbosstools/updates/webtools/mars to wtp and composite in the nightly site ? Then we don't break any of our current and past conventions/release cadence. > release webtools site for Eclipse 4.3 Mars to so WTP 3.7 discovery upstream can find it > --------------------------------------------------------------------------------------- > > Key: JBIDE-18921 > URL: https://issues.jboss.org/browse/JBIDE-18921 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, updatesite, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > Need a semi-working placeholder (even if it's a weak first alpha or copy of JBT 4.2.0's site) so that WTP can resolve a valid site for server adapters. > Content that needs to be copied is here: > http://download.jboss.org/jbosstools/static/updates/JBossTools-4.2.0.Fina... (or something newer?) > Destination folder (new folder hierarchy as of JBDS-3208 reorg): > http://download.jboss.org/jbosstools/mars/stable/updates/webtools/ > Upstream issue: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=454810 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18921) release webtools site for Eclipse 4.3 Mars to so WTP 3.7 discovery upstream can find it

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18921?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18921: --------------------------------------------- You do not need to clone anything. You can simply unzip the plugin and put the info. And I've said this all 4 years. Put empty site until we actually have something tested and released for Luna. And how about fixing the bug that prevent us to just point to our main updatesite so we don't even have to publish different url ? That would be when we actually release first alpha. A) yes, or Just add the site empty. B) no one said wait for ga. I said wait to we actually have something tested and we want to make available. C) this would be better than putting alpha1 non tested content there. D) having stable contain not even milestone/develpoment release breaks just as much convention. > release webtools site for Eclipse 4.3 Mars to so WTP 3.7 discovery upstream can find it > --------------------------------------------------------------------------------------- > > Key: JBIDE-18921 > URL: https://issues.jboss.org/browse/JBIDE-18921 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, updatesite, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > Need a semi-working placeholder (even if it's a weak first alpha or copy of JBT 4.2.0's site) so that WTP can resolve a valid site for server adapters. > Content that needs to be copied is here: > http://download.jboss.org/jbosstools/static/updates/JBossTools-4.2.0.Fina... (or something newer?) > Destination folder (new folder hierarchy as of JBDS-3208 reorg): > http://download.jboss.org/jbosstools/mars/stable/updates/webtools/ > Upstream issue: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=454810 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18921) release webtools site for Eclipse 4.3 Mars to so WTP 3.7 discovery upstream can find it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18921?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18921: ------------------------------------ Actually we do, because it's embedded in org.eclipse.webtools code. Ok, sure, I could clone it, fork it, patch it, and then play with it, but why? Why not just push the one-line change upstream, let them built it into Mars M4, and THEN I can play with the contents of http://download.jboss.org/jbosstools/mars/stable/updates/webtools/ As to the fact that we're putting "completely untested" code into the stable URL, this is what we've done now for, oh, what, 4 years [1]? [1] http://download.jboss.org/jbosstools/updates/webtools/ (note the sites for indigo, juno, kepler, & luna) Possible other solutions: a) ask WTP to change the URL closer to Mars GA (and have them forget like last year) b) have a stable URL with no contents until we go GA, which means NO ONE using WTP 3.7 will see our server adapters until ~ October 2015 c) put the old 4.2.0.Final bits in there; replace them later as we release each 4.3.x milestone d) remove the word "stable" from the URL, which breaks with the conventions set forth in JBDS-3208, reverting to the old convention in [1] > release webtools site for Eclipse 4.3 Mars to so WTP 3.7 discovery upstream can find it > --------------------------------------------------------------------------------------- > > Key: JBIDE-18921 > URL: https://issues.jboss.org/browse/JBIDE-18921 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, updatesite, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > Need a semi-working placeholder (even if it's a weak first alpha or copy of JBT 4.2.0's site) so that WTP can resolve a valid site for server adapters. > Content that needs to be copied is here: > http://download.jboss.org/jbosstools/static/updates/JBossTools-4.2.0.Fina... (or something newer?) > Destination folder (new folder hierarchy as of JBDS-3208 reorg): > http://download.jboss.org/jbosstools/mars/stable/updates/webtools/ > Upstream issue: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=454810 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18915) Create Icons for Batch tools

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18915?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-18915: --------------------------------------- [~scabanovich], please use attached png images. *batch_editor_icon.png* for xml file and editor and *batch_node_icon.png* for all nodes. This is just for beginning. I suggest to have different image files for all nodes, so they could be easily replaced in the future without any code changes. > Create Icons for Batch tools > ---------------------------- > > Key: JBIDE-18915 > URL: https://issues.jboss.org/browse/JBIDE-18915 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Viacheslav Kabanovich > Assignee: Daniel Azarov > Fix For: 4.3.0.Alpha1 > > Attachments: batch_editor_icon.png, batch_icon16.png, batch_node_icon.png > > > batch_icon16.png - file batch.xml (initial image is attached, it can be replaced or used) > analyzer.png - receives intermediary results from each partition sent via partition collector and serves as a collection point for this data; it may be used to implement custom exit status handling for the step > batchlet.png - 'batchlet' element specifies a task-oriented batch step > checkpoint-algorithm.png - an optional custom checkpoint algorithm that may be used to provide a checkpoint decision based > on factors other than only number of items, or amount of time > chunk.png - kind of step that processes multiple items and is periodically checkpointed by the batch runtime according to a configured checkpoint policy > collector.png - partition collector is used by step partitions for sharing data that is used to decide the overall outcome of the step > decision.png - decision provides a customized way of determining sequencing among steps, flows, and splits (batch status is set to FAILED) > end.png - end element is used to terminate the job at the current step (batch status is set to COMPLETED) > exclude.png - element 'exclude' specifies a class name of an exception or exception superclass to not be taken into account > fail.png - fail element is used to terminate the job at the conclusion of the current step or flow > flow.png - flow defines a sequence of execution elements that execute together as a unit > include.png - element 'include' specifies the class name of an exception or exception superclass that should be taken into account > job.png - root node of file batch.xml, it may be the same as batch_icon16.png > listeners.png - folder for listeners > listener.png - job listener > mapper.png - partition mapper provides a programmatic means for calculating the number of partitions and threads for a partitioned step > next.png - transition element that defines condition and target for transition to next step. > partition.png - 'partition' element specifies that a step is a partitioned step > plan.png - plan defines the number of partitions and the maximum number of threads on which to execute the partitions of the partitioned step > processor.png - 'processor' element specifies the item processor for a chunk step > properties.png - folder for properties > property.png - common 'name'='value' object. > reader.png - 'reader' element specifies the item reader for a chunk step > reducer.png - partition reducer provides a kind of unit of work demarcation around the processing of the partitions > no-rollback-exception-classes.png - list of exceptions that override the default behavior of rollback for retryable exceptions > retryable-exception-classes.png - set of exceptions that chunk processing will retry > skippable-exception-classes.png - set of exceptions that chunk processing will skip > split.png - split defines a set of flows that execute concurrently > step.png - 'step' element identifies a job step, job may contain any number of steps > stop.png - stop element is used to terminate the job after the current step or flow (batch status is set to STOPPED), optionally defines step at which job can be restarted > writer.png - 'writer' element specifies the item writer for a chunk step -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18915) Create Icons for Batch tools

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18915?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-18915: ---------------------------------- Attachment: batch_node_icon.png batch_editor_icon.png > Create Icons for Batch tools > ---------------------------- > > Key: JBIDE-18915 > URL: https://issues.jboss.org/browse/JBIDE-18915 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Viacheslav Kabanovich > Assignee: Daniel Azarov > Fix For: 4.3.0.Alpha1 > > Attachments: batch_editor_icon.png, batch_icon16.png, batch_node_icon.png > > > batch_icon16.png - file batch.xml (initial image is attached, it can be replaced or used) > analyzer.png - receives intermediary results from each partition sent via partition collector and serves as a collection point for this data; it may be used to implement custom exit status handling for the step > batchlet.png - 'batchlet' element specifies a task-oriented batch step > checkpoint-algorithm.png - an optional custom checkpoint algorithm that may be used to provide a checkpoint decision based > on factors other than only number of items, or amount of time > chunk.png - kind of step that processes multiple items and is periodically checkpointed by the batch runtime according to a configured checkpoint policy > collector.png - partition collector is used by step partitions for sharing data that is used to decide the overall outcome of the step > decision.png - decision provides a customized way of determining sequencing among steps, flows, and splits (batch status is set to FAILED) > end.png - end element is used to terminate the job at the current step (batch status is set to COMPLETED) > exclude.png - element 'exclude' specifies a class name of an exception or exception superclass to not be taken into account > fail.png - fail element is used to terminate the job at the conclusion of the current step or flow > flow.png - flow defines a sequence of execution elements that execute together as a unit > include.png - element 'include' specifies the class name of an exception or exception superclass that should be taken into account > job.png - root node of file batch.xml, it may be the same as batch_icon16.png > listeners.png - folder for listeners > listener.png - job listener > mapper.png - partition mapper provides a programmatic means for calculating the number of partitions and threads for a partitioned step > next.png - transition element that defines condition and target for transition to next step. > partition.png - 'partition' element specifies that a step is a partitioned step > plan.png - plan defines the number of partitions and the maximum number of threads on which to execute the partitions of the partitioned step > processor.png - 'processor' element specifies the item processor for a chunk step > properties.png - folder for properties > property.png - common 'name'='value' object. > reader.png - 'reader' element specifies the item reader for a chunk step > reducer.png - partition reducer provides a kind of unit of work demarcation around the processing of the partitions > no-rollback-exception-classes.png - list of exceptions that override the default behavior of rollback for retryable exceptions > retryable-exception-classes.png - set of exceptions that chunk processing will retry > skippable-exception-classes.png - set of exceptions that chunk processing will skip > split.png - split defines a set of flows that execute concurrently > step.png - 'step' element identifies a job step, job may contain any number of steps > stop.png - stop element is used to terminate the job after the current step or flow (batch status is set to STOPPED), optionally defines step at which job can be restarted > writer.png - 'writer' element specifies the item writer for a chunk step -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18925) Choose a default target server runtime as the latest available

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18925?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18925: ----------------------------------- Component/s: central project-examples > Choose a default target server runtime as the latest available > -------------------------------------------------------------- > > Key: JBIDE-18925 > URL: https://issues.jboss.org/browse/JBIDE-18925 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, project-examples > Reporter: Marek Novotny > > This suggestion for enhancement distilled from JBDS-3240 comments. > The creating of new project from Maven archetype (Start from Scratch in JBoss Central) is the starting point. > Could a runtime in the Target runtime field be set by default (the latest is the best) from available runtimes ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18921) release webtools site for Eclipse 4.3 Mars to so WTP 3.7 discovery upstream can find it

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18921?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18921: --------------------------------------------- We dont need wtp to embed things to do experiments. Just add your own locally. > release webtools site for Eclipse 4.3 Mars to so WTP 3.7 discovery upstream can find it > --------------------------------------------------------------------------------------- > > Key: JBIDE-18921 > URL: https://issues.jboss.org/browse/JBIDE-18921 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, updatesite, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > Need a semi-working placeholder (even if it's a weak first alpha or copy of JBT 4.2.0's site) so that WTP can resolve a valid site for server adapters. > Content that needs to be copied is here: > http://download.jboss.org/jbosstools/static/updates/JBossTools-4.2.0.Fina... (or something newer?) > Destination folder (new folder hierarchy as of JBDS-3208 reorg): > http://download.jboss.org/jbosstools/mars/stable/updates/webtools/ > Upstream issue: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=454810 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

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 December 2014