[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_editor.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.png, 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, 2 months
[JBoss JIRA] (JBIDE-19057) externalize MultipleVersionIssue#ignore into pom properties for easier extensibility
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19057?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19057:
-------------------------------
Description:
Currently, there are two IUs which are excluded from tracking as a MultipleVersionIssue:
{code:title=MultipleVersionIssue.java}
String[] ignore = {"javax.wsdl","org.apache.commons.logging"};
{code}
However, we need to add more, such as *org.eclipse.jdt.annotation*, so might as well externalize this into a pom property for easier use.
was:
Currently, there are two IUs which are excluded from tracking as a MultipleVersionIssue:
{code:title=MultipleVersionIssue.java}
String[] ignore = {"javax.wsdl","org.apache.commons.logging"};
{code}
However, we need to add more, so might as well externalize this into a pom property for easier use.
> externalize MultipleVersionIssue#ignore into pom properties for easier extensibility
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19057
> URL: https://issues.jboss.org/browse/JBIDE-19057
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa
> Affects Versions: 4.2.2.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Currently, there are two IUs which are excluded from tracking as a MultipleVersionIssue:
> {code:title=MultipleVersionIssue.java}
> String[] ignore = {"javax.wsdl","org.apache.commons.logging"};
> {code}
> However, we need to add more, such as *org.eclipse.jdt.annotation*, so might as well externalize this into a pom property for easier use.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19058) refactor output.html and product.html into report_detailed.html and report_summary.html
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19058:
----------------------------------
Summary: refactor output.html and product.html into report_detailed.html and report_summary.html
Key: JBIDE-19058
URL: https://issues.jboss.org/browse/JBIDE-19058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, qa
Reporter: Nick Boldt
Today, vwatch produces two files:
* a detailed, tabular report called "output.hml"
* a summary report called "report.html"
In Jenkins, I then rename these to results*.html and report*.html, which is a bit confusing because the files are not listed next to each other in the http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... folder.
So, I propose we generate the files with these names:
* report_detailed.html
* report_summary.html
Then in Jenkins we can simply rename them to include a timestamp/buildID prefix, and continue to differentiate the "all" report from the org.jboss-only "filtered" report:
* B1766_2015-01-07_17-28-06_report_detailed_all.html
* B1766_2015-01-07_17-28-06_report_detailed_filtered.html
* B1766_2015-01-07_17-28-06_report_summary_all.html
* B1766_2015-01-07_17-28-06_report_summary_filtered.html
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19057) externalize MultipleVersionIssue#ignore into pom properties for easier extensibility
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19057:
----------------------------------
Summary: externalize MultipleVersionIssue#ignore into pom properties for easier extensibility
Key: JBIDE-19057
URL: https://issues.jboss.org/browse/JBIDE-19057
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, qa
Affects Versions: 4.2.2.Final
Reporter: Nick Boldt
Currently, there are two IUs which are excluded from tracking as a MultipleVersionIssue:
{code:title=MultipleVersionIssue.java}
String[] ignore = {"javax.wsdl","org.apache.commons.logging"};
{code}
However, we need to add more, so might as well externalize this into a pom property for easier use.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19040) Software update: Item hidden under table header
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19040?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-19040:
-------------------------------------
resizing the window will also show the hidden element
> Software update: Item hidden under table header
> -----------------------------------------------
>
> Key: JBIDE-19040
> URL: https://issues.jboss.org/browse/JBIDE-19040
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.2.Final
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.3.x
>
> Attachments: update-hidden.png, update-shown.png
>
>
> This is probably an upstream issue and I'm not sure if/how much we can do here. But I'd like to have this reported anyway.
> When JBDS notifies me of updates and I want to install the updates, the "Available Updates" window seems empty:
> !update-hidden.png!
> What's happening is that there is only one item and it's hidden at the very top behind the table header. With my mouse, I can scroll to see it:
> !update-shown.png!
> What's worse, the hidden item can only be made visible by scrolling a mouse, not using touchpad. So unless I have a mouse connected, I'm out of luck.
> This happens in other places as well, notably in the software update sites page in Preferences.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19040) Software update: Item hidden under table header
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19040?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19040:
---------------------------------------
This is Oracle JDK 1.8.
OK, I did not expect this would be any different on 10.9, but you're right, 10.10 is not officially supported. So let me try this on 10.9 and report back here if it's happening there as well.
> Software update: Item hidden under table header
> -----------------------------------------------
>
> Key: JBIDE-19040
> URL: https://issues.jboss.org/browse/JBIDE-19040
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.2.Final
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.3.x
>
> Attachments: update-hidden.png, update-shown.png
>
>
> This is probably an upstream issue and I'm not sure if/how much we can do here. But I'd like to have this reported anyway.
> When JBDS notifies me of updates and I want to install the updates, the "Available Updates" window seems empty:
> !update-hidden.png!
> What's happening is that there is only one item and it's hidden at the very top behind the table header. With my mouse, I can scroll to see it:
> !update-shown.png!
> What's worse, the hidden item can only be made visible by scrolling a mouse, not using touchpad. So unless I have a mouse connected, I'm out of luck.
> This happens in other places as well, notably in the software update sites page in Preferences.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months