[JBoss JIRA] (JBIDE-19158) Batch Validation
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19158?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-19158:
------------------------------------------
Description:
Validation rules for job xml
1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#\{jobProperties['%name%']\} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
4. Sequence of execution elements defined by @next and @to should not loop.
5. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class.
was:
Validation rules for job xml
1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#\{jobProperties['%name%']\} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
4. Sequence of execution elements defined by @next and @to should not loop.
> Batch Validation
> ----------------
>
> Key: JBIDE-19158
> URL: https://issues.jboss.org/browse/JBIDE-19158
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha1
>
>
> Validation rules for job xml
> 1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
> 2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#\{jobProperties['%name%']\} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
> 3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
> 4. Sequence of execution elements defined by @next and @to should not loop.
> 5. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19158) Batch Validation
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19158?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-19158:
------------------------------------------
Description:
Validation rules for job xml
1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#{jobProperties['%name%']} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
4. Sequence of execution elements defined by @next and @to should not loop.
was:
Validation rules for job xml
1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution #{jobProperties['%name%']} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
4. Sequence of execution elements defined by @next and @to should not loop.
> Batch Validation
> ----------------
>
> Key: JBIDE-19158
> URL: https://issues.jboss.org/browse/JBIDE-19158
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha1
>
>
> Validation rules for job xml
> 1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
> 2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#{jobProperties['%name%']} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
> 3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
> 4. Sequence of execution elements defined by @next and @to should not loop.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19158) Batch Validation
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19158?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-19158:
------------------------------------------
Description:
Validation rules for job xml
1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#\{jobProperties['%name%']\} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
4. Sequence of execution elements defined by @next and @to should not loop.
was:
Validation rules for job xml
1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#{jobProperties['%name%']} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
4. Sequence of execution elements defined by @next and @to should not loop.
> Batch Validation
> ----------------
>
> Key: JBIDE-19158
> URL: https://issues.jboss.org/browse/JBIDE-19158
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha1
>
>
> Validation rules for job xml
> 1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
> 2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#\{jobProperties['%name%']\} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
> 3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
> 4. Sequence of execution elements defined by @next and @to should not loop.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19158) Batch Validation
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19158?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-19158:
------------------------------------------
Description:
Validation rules for job xml
1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution #{jobProperties['%name%']} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
4. Sequence of execution elements defined by @next and @to should not loop.
was:
Validation rules for job xml
1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
2. Attribute 'properties/property/@name' should refer by batch property name a field in Java type for the batch artifact. Batch runtime ignores properties that do not match Java fields, so that validation should only set warning markers.
3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the same level as the current flow element.
4. Sequence of flow elements defined by @next and @to should not loop.
> Batch Validation
> ----------------
>
> Key: JBIDE-19158
> URL: https://issues.jboss.org/browse/JBIDE-19158
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha1
>
>
> Validation rules for job xml
> 1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element.
> 2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution #{jobProperties['%name%']} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name.
> 3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another.
> 4. Sequence of execution elements defined by @next and @to should not loop.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19194) FeedHenry requires minimal-json, but it was removed from TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19194?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19194:
-------------------------------
Description:
When moving Tern from the 4.42.x and 4.50.x target platforms into JST, we also moved minimal-json assuming nothing else required it.
But turns out that Feedhenry (Aerogear) also needs minimal-json.
So... we need to add that plugin back into the TPs, and make sure that the version we include works with both Aerogear/FeedHenry (0.9.2, same code base in both 4.2.3 and 4.3.0, currently) and JST/Tern (0.9.1 in JBT 4.2, 0.9.2 in JBT 4.3).
[~maxandersen] [~gercan] [~dgolovin] [~akazakov]
In JBT 4.2.0-2 we include Tern 0.6 and minimal-json 0.9.1.
In JBT 4.2.3 we include Tern 0.7 and minimal-json 0.9.1.
In JBT 4.3.0 we _currently_ include Tern 0.8 and minimal-json 0.9.2.
Which version should we include in the target platforms for JBT 4.2.3 (4.42.0.Beta1) and JBT 4.3.0 (4.50.0.Alpha1) ?
was:
When moving Tern from the 4.42.x and 4.50.x target platforms into JST, we also moved minimal-json assuming nothing else required it.
But turns out that Feedhenry (Aerogear) also needs minimal-json.
So... we need to add that plugin back into the TPs. :(
> FeedHenry requires minimal-json, but it was removed from TP
> -----------------------------------------------------------
>
> Key: JBIDE-19194
> URL: https://issues.jboss.org/browse/JBIDE-19194
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> When moving Tern from the 4.42.x and 4.50.x target platforms into JST, we also moved minimal-json assuming nothing else required it.
> But turns out that Feedhenry (Aerogear) also needs minimal-json.
> So... we need to add that plugin back into the TPs, and make sure that the version we include works with both Aerogear/FeedHenry (0.9.2, same code base in both 4.2.3 and 4.3.0, currently) and JST/Tern (0.9.1 in JBT 4.2, 0.9.2 in JBT 4.3).
> [~maxandersen] [~gercan] [~dgolovin] [~akazakov]
> In JBT 4.2.0-2 we include Tern 0.6 and minimal-json 0.9.1.
> In JBT 4.2.3 we include Tern 0.7 and minimal-json 0.9.1.
> In JBT 4.3.0 we _currently_ include Tern 0.8 and minimal-json 0.9.2.
> Which version should we include in the target platforms for JBT 4.2.3 (4.42.0.Beta1) and JBT 4.3.0 (4.50.0.Alpha1) ?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19195) For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [BrowserSim]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19195?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19195:
-----------------------------------
Component/s: browsersim
cordovasim
(was: visual-page-editor-core)
> For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [BrowserSim]
> ----------------------------------------------------------------------
>
> Key: JBIDE-19195
> URL: https://issues.jboss.org/browse/JBIDE-19195
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: browsersim, cordovasim
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.3.Beta1
>
>
> For JBIDE 4.2.3.Beta1 [VPE]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3.
> Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.3.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version:
> {code}
> mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT
> {code}
> 2. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19195) For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [BrowserSim]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19195?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19195:
-----------------------------------
Description:
For JBIDE 4.2.3.Beta1 [BrowserSim]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3.
Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.3.Beta1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version:
{code}
mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
was:
For JBIDE 4.2.3.Beta1 [VPE]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3.
Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.3.Beta1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version:
{code}
mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [BrowserSim]
> ----------------------------------------------------------------------
>
> Key: JBIDE-19195
> URL: https://issues.jboss.org/browse/JBIDE-19195
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: browsersim, cordovasim
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.3.Beta1
>
>
> For JBIDE 4.2.3.Beta1 [BrowserSim]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3.
> Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.3.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version:
> {code}
> mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT
> {code}
> 2. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19195) For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [BrowserSim]
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-19195:
--------------------------------------
Summary: For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [BrowserSim]
Key: JBIDE-19195
URL: https://issues.jboss.org/browse/JBIDE-19195
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: visual-page-editor-core
Reporter: Alexey Kazakov
Assignee: Konstantin Marmalyukov
Priority: Blocker
Fix For: 4.2.3.Beta1
For JBIDE 4.2.3.Beta1 [VPE]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3.
Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.3.Beta1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version:
{code}
mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19194) FeedHenry requires minimal-json, but it was removed from TP
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19194:
----------------------------------
Summary: FeedHenry requires minimal-json, but it was removed from TP
Key: JBIDE-19194
URL: https://issues.jboss.org/browse/JBIDE-19194
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
Reporter: Nick Boldt
When moving Tern from the 4.42.x and 4.50.x target platforms into JST, we also moved minimal-json assuming nothing else required it.
But turns out that Feedhenry (Aerogear) also needs minimal-json.
So... we need to add that plugin back into the TPs. :(
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months