February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-18859) Basic Batch XML Editor (Tree form + source editor tabs)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18859?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-18859. ------------------------------------ Resolution: Done > Basic Batch XML Editor (Tree form + source editor tabs) > ------------------------------------------------------- > > Key: JBIDE-18859 > URL: https://issues.jboss.org/browse/JBIDE-18859 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: editor.ogv, editor.png > > > This is supposed to be a multi page editor with two tabs: > - Tree form editor > - XML source editor (a simple extension of Eclipse XML Editor) > !editor.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18859) Basic Batch XML Editor (Tree form + source editor tabs)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18859?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18859: ---------------------------------------- [~ljelinko] Batch tree form editor is broken now because of an upstream issue in Mars M5 - JBIDE-19270 I'm resolving this issue and let's track remaining problems in JBIDE-19270 > Basic Batch XML Editor (Tree form + source editor tabs) > ------------------------------------------------------- > > Key: JBIDE-18859 > URL: https://issues.jboss.org/browse/JBIDE-18859 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: editor.ogv, editor.png > > > This is supposed to be a multi page editor with two tabs: > - Tree form editor > - XML source editor (a simple extension of Eclipse XML Editor) > !editor.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19112) Create Luna SR2 target platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19112?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19112: ---------------------------------------- Pull request to move to Luna SR2 RC4 (hopefully promoted next weel as Luna SR2): https://github.com/jbosstools/jbosstools-target-platforms/pull/134. p2diff shows not added/removed IUs. Only Mylyn and TM pushed newer builds. All other projects (including Platform and Webtools) have provided same bundles that they did for the RC3. So no big change here. To try it {code} $ cd jbosstools-target-platforms $ git fetch jbosstools pull/134/head $ cd jbosstools/multiple $ mvn install $ cd jbosstools-component-to-test $ mvn clean verify -Pmutliple.target -Dtpc.version=4.42.0.Beta1-SNAPSHOT {code} > Create Luna SR2 target platform > -------------------------------- > > Key: JBIDE-19112 > URL: https://issues.jboss.org/browse/JBIDE-19112 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.2.3.Beta1 > > > Need a target platform from 4.42.x branch based on Luna SR2. > Schedule of RC1 - RC4 milestones is here (GA bits available as of 02/20): > http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#SR2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18915?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-18915. ------------------------------------ Resolution: Done [~ljelinko], could you please create a separate issue for that? We will see what we can do for Alpha2. > 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: analyzer.png, batchlet.png, batch_editor.png, batch_editor_icon.png, batch_icon16.png, batch_node_icon.png, checkpoint-algorithm.png, chunk.png, collector.png, decision.png, end.png, exclude.png, fail.png, flow.png, include.png, listener.png, listeners.png, mapper.png, next.png, no-rollback-exception-classes.png, partition.png, plan.png, processor.png, properties.png, property.png, reader.png, reducer.png, retryable-exception-classes.png, skippable-exception-classes.png, split.png, step.png, stop.png, writer.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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19112) Create Luna SR2 target platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19112?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19112: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/120, https://github.com/jbosstools/jbosstools-target-platforms/pull/130, https://github.com/jbosstools/jbosstools-target-platforms/pull/134 (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/120, https://github.com/jbosstools/jbosstools-target-platforms/pull/130) > Create Luna SR2 target platform > -------------------------------- > > Key: JBIDE-19112 > URL: https://issues.jboss.org/browse/JBIDE-19112 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.2.3.Beta1 > > > Need a target platform from 4.42.x branch based on Luna SR2. > Schedule of RC1 - RC4 milestones is here (GA bits available as of 02/20): > http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#SR2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14642) How to automate process of bumping version for changed modules/submodules for every release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14642?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-14642: ------------------------------------ [~dgolovin] Is this issue resolved by Mickael's new mojo in JBIDE-19056 ? > How to automate process of bumping version for changed modules/submodules for every release > ------------------------------------------------------------------------------------------- > > Key: JBIDE-14642 > URL: https://issues.jboss.org/browse/JBIDE-14642 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > Assignee: Max Rydahl Andersen > Labels: versioning > Fix For: 4.3.x > > > The versions of plugins are constantly discovered to not be uptodated when they should and things like Usage and others where it is critical are not getting bumped. > We need two things: > A) detect when versions are not bumped properly - we got parts of this in various places, but they are not run nor documented regularly (having a green build verifying versions are not conflicting would be a Good Thing) > B) document/automate a process which every affected lead can follow to make this happen and if not See #A -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14642) How to automate process of bumping version for changed modules/submodules for every release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14642?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14642: ------------------------------- Fix Version/s: 4.3.x (was: 4.2.x) > How to automate process of bumping version for changed modules/submodules for every release > ------------------------------------------------------------------------------------------- > > Key: JBIDE-14642 > URL: https://issues.jboss.org/browse/JBIDE-14642 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > Assignee: Max Rydahl Andersen > Labels: versioning > Fix For: 4.3.x > > > The versions of plugins are constantly discovered to not be uptodated when they should and things like Usage and others where it is critical are not getting bumped. > We need two things: > A) detect when versions are not bumped properly - we got parts of this in various places, but they are not run nor documented regularly (having a green build verifying versions are not conflicting would be a Good Thing) > B) document/automate a process which every affected lead can follow to make this happen and if not See #A -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15339) Create version/change auditor/reporting tool

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15339?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15339: ------------------------------- Fix Version/s: 4.3.x (was: 4.2.x) > Create version/change auditor/reporting tool > -------------------------------------------- > > Key: JBIDE-15339 > URL: https://issues.jboss.org/browse/JBIDE-15339 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, updatesite > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: versioning > Fix For: 4.3.x > > > Plugin/Feature Version Auditor > Goal: be able to more easily see if a feature or plugin needs to be upversioned > Goal: be able to more easily see if a commit in github has been built into the jars in an update site > Goal: be able to more easily see what has changed between two builds (with links to relevant Jenkins, JIRA, Github, upstream URLs, TP URLs) > Output: generate a report of: > plugins, features in JBT or JBDS by version, md5 #, JIRA #s related to latest commits, jenkins build IDs > Include URL links to content/metadata: Github, Jenkins, JIRA, dl.jb.org (upstream sites which feed the aggregates, target platforms, composites, etc.) > May also include some parallel work to provide improvements to QA's versionwatch tool (https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch ) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19324) Arquillian core frezzes Eclipse startup

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19324?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19324: ---------------------------------------- Please, make sure we don't have this issue in 4.2.x. > Arquillian core frezzes Eclipse startup > --------------------------------------- > > Key: JBIDE-19324 > URL: https://issues.jboss.org/browse/JBIDE-19324 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.3.0.Alpha1 > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > Attachments: dump.txt, restart.ogv > > > When I have arquillian.xml with at least one container defined and I open it with Arquillian editor and restart Eclipse, the Eclipse wont start and it freezes on loading arquillian core plugin (see screencast). > I am also attaching thread dump (thanks to [~rhopp]) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19321) Unable to close Restore Cordova Plugin Dialog

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19321?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19321: ---------------------------------------- Any exceptions? > Unable to close Restore Cordova Plugin Dialog > --------------------------------------------- > > Key: JBIDE-19321 > URL: https://issues.jboss.org/browse/JBIDE-19321 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha1 > Environment: MS Windows 7 64 bit JBDS 9.0.0.Alpha1-v20150216-1042-B11 > Reporter: Vlado Pakan > Priority: Critical > > # Import project https://github.com/aerogear/aerogear-push-quickstarts/tree/master/client/... as Hyrid Mobile Project > # Click on Finish button of dialog with title "Restore Cordova Plug-In" > ERROR: Dialog is not closed even when clicking many times > Button Cancel works -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 February 2015