[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19697:
---------------------------------------
That's what I thought at first too. But I don't have such config inside ~/eclipse:
{code}
$ ls ~/.eclipse
org.eclipse.equinox.security org.eclipse.oomph.p2 org.eclipse.oomph.setup org.eclipse.recommenders
$ find ~/.eclipse -name 'org.jboss.tools.runtime.*.prefs'|wc
0 0 0
{code}
> org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19697
> URL: https://issues.jboss.org/browse/JBIDE-19697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Snjezana Peco
>
> When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
> Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
> {code}
> This is inside the file:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
> eclipse.preferences.version=1
> runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
> {code}
> It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
> I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
> Can somebody explain what's going on?
> Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-19697:
-------------------------------------------
Assignee: Snjezana Peco
> org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19697
> URL: https://issues.jboss.org/browse/JBIDE-19697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Snjezana Peco
>
> When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
> Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
> {code}
> This is inside the file:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
> eclipse.preferences.version=1
> runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
> {code}
> It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
> I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
> Can somebody explain what's going on?
> Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19697:
---------------------------------------------
I would expect the settings would be stored in your ~/.eclipse setting if anything. surprising if its in your local preferences.
[~snjeza] and [~rob.stryker] whats the logic we got currently for storing the runtime location preferences ?
> org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19697
> URL: https://issues.jboss.org/browse/JBIDE-19697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Snjezana Peco
>
> When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
> Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
> {code}
> This is inside the file:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
> eclipse.preferences.version=1
> runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
> {code}
> It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
> I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
> Can somebody explain what's going on?
> Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19697:
----------------------------------------
Component/s: (was: build)
> org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19697
> URL: https://issues.jboss.org/browse/JBIDE-19697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
>
> When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
> Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
> {code}
> This is inside the file:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
> eclipse.preferences.version=1
> runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
> {code}
> It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
> I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
> Can somebody explain what's going on?
> Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19697:
---------------------------------------
I wasn't sure what component to use - it's not really about build, but there is no p2 component. And I would assume that this is not specific to JBDS only, so I created the JIRA under JBIDE.
> org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19697
> URL: https://issues.jboss.org/browse/JBIDE-19697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, runtime-detection
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
>
> When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
> Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
> {code}
> This is inside the file:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
> eclipse.preferences.version=1
> runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
> {code}
> It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
> I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
> Can somebody explain what's going on?
> Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Martin Malina (JIRA)
Martin Malina created JBIDE-19697:
-------------------------------------
Summary: org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
Key: JBIDE-19697
URL: https://issues.jboss.org/browse/JBIDE-19697
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, runtime-detection
Affects Versions: 4.3.0.Alpha2
Reporter: Martin Malina
When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
{code}
$ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
{code}
This is inside the file:
{code}
$ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
eclipse.preferences.version=1
runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
{code}
It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
Can somebody explain what's going on?
Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-19507:
-----------------------------------------
Created JBIDE-19696
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, PropertyRename.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> Example:
> During the search for references for class "SearchableException" like:
> {code}
> package batch;
> public class SearchableException extends Exception{
> private static final long serialVersionUID = 1L;
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableExceptionReferences.png!
> *Rename Participant*
> 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named
> Example:
> During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring:
> !BatchArtifactRename.png!
> 2. Should be able to add changes in Batch Property Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Properties which name comes from Java Field Name, not from annotation @BatchProperty
> Example:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class RenamablePropertyBatchlet implements Batchlet {
>
> @Inject @BatchProperty String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> During rename of field "otherName" changes for job.xml references should be added in Refactoring:
> !PropertyRename.png!
> 3. Should be able to add changes in Exception Class Rename for references in job.xml files.
> Example:
> During rename of class "SearchableException" changes for job.xml references should be added in Refactoring:
> !ExceptionRename.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-19507.
-----------------------------------
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, PropertyRename.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> Example:
> During the search for references for class "SearchableException" like:
> {code}
> package batch;
> public class SearchableException extends Exception{
> private static final long serialVersionUID = 1L;
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableExceptionReferences.png!
> *Rename Participant*
> 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named
> Example:
> During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring:
> !BatchArtifactRename.png!
> 2. Should be able to add changes in Batch Property Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Properties which name comes from Java Field Name, not from annotation @BatchProperty
> Example:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class RenamablePropertyBatchlet implements Batchlet {
>
> @Inject @BatchProperty String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> During rename of field "otherName" changes for job.xml references should be added in Refactoring:
> !PropertyRename.png!
> 3. Should be able to add changes in Exception Class Rename for references in job.xml files.
> Example:
> During rename of class "SearchableException" changes for job.xml references should be added in Refactoring:
> !ExceptionRename.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19696) Rename of an exception class does not work properly
by Lucia Jelinkova (JIRA)
Lucia Jelinkova created JBIDE-19696:
---------------------------------------
Summary: Rename of an exception class does not work properly
Key: JBIDE-19696
URL: https://issues.jboss.org/browse/JBIDE-19696
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: batch
Affects Versions: 4.3.0.Alpha2
Reporter: Lucia Jelinkova
Priority: Critical
When I try to rename an exception class RenamableException to RenamableException2, I get batch.RenamableException2enamableException in job XML file instead.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-19507:
-----------------------------------------
All works fine in JBDS 9.0.0.alpha2 except for renaming exception class. I'll create separate issue for that.
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, PropertyRename.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> Example:
> During the search for references for class "SearchableException" like:
> {code}
> package batch;
> public class SearchableException extends Exception{
> private static final long serialVersionUID = 1L;
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableExceptionReferences.png!
> *Rename Participant*
> 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named
> Example:
> During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring:
> !BatchArtifactRename.png!
> 2. Should be able to add changes in Batch Property Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Properties which name comes from Java Field Name, not from annotation @BatchProperty
> Example:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class RenamablePropertyBatchlet implements Batchlet {
>
> @Inject @BatchProperty String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> During rename of field "otherName" changes for job.xml references should be added in Refactoring:
> !PropertyRename.png!
> 3. Should be able to add changes in Exception Class Rename for references in job.xml files.
> Example:
> During rename of class "SearchableException" changes for job.xml references should be added in Refactoring:
> !ExceptionRename.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years