[JBoss JIRA] (JBDS-3169) For JBDS 8.0.0.CR2: Prepare for CR2 release
by Nick Boldt (JIRA)
Nick Boldt created JBDS-3169:
--------------------------------
Summary: For JBDS 8.0.0.CR2: Prepare for CR2 release
Key: JBDS-3169
URL: https://issues.jboss.org/browse/JBDS-3169
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: installer
Reporter: Nick Boldt
Priority: Blocker
Fix For: 8.0.0.CR2
For JBDS 8.0.0.CR2: Please perform the following tasks:
0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise, for all other projects:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA.
[Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions
{code}
mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT
mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT
{code}
5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*:
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
4. 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.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18464) For JBIDE 4.2.0.CR2: Prepare for CR2 release
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18464:
----------------------------------
Summary: For JBIDE 4.2.0.CR2: Prepare for CR2 release
Key: JBIDE-18464
URL: https://issues.jboss.org/browse/JBIDE-18464
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.2.0.CR2
For JBIDE 4.2.0.CR2: Please perform the following tasks:
0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise, for all other projects:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA.
[Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions
{code}
mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT
mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT
{code}
5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*:
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
4. 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...]
See also: JBDS-3169
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18465) For JBIDE 4.2.0.CR2: Prepare for CR2 release [Aerogear]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18465:
----------------------------------
Summary: For JBIDE 4.2.0.CR2: Prepare for CR2 release [Aerogear]
Key: JBIDE-18465
URL: https://issues.jboss.org/browse/JBIDE-18465
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: aerogear-hybrid
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.CR2 [Aerogear]: Please perform the following tasks:
0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise, for all other projects:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA.
[Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions
{code}
mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT
mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT
{code}
5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*:
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
4. 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 Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18466) For JBIDE 4.2.0.CR2: Prepare for CR2 release [JST]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18466:
----------------------------------
Summary: For JBIDE 4.2.0.CR2: Prepare for CR2 release [JST]
Key: JBIDE-18466
URL: https://issues.jboss.org/browse/JBIDE-18466
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.CR2 [JST]: Please perform the following tasks:
0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise, for all other projects:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA.
[Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions
{code}
mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT
mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT
{code}
5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*:
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
4. 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 JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18467) For JBIDE 4.2.0.CR2: Prepare for CR2 release [VPE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18467:
----------------------------------
Summary: For JBIDE 4.2.0.CR2: Prepare for CR2 release [VPE]
Key: JBIDE-18467
URL: https://issues.jboss.org/browse/JBIDE-18467
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: visual-page-editor-core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.CR2 [VPE]: Please perform the following tasks:
0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise, for all other projects:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA.
[Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions
{code}
mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT
mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT
{code}
5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*:
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
4. 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.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18468) For JBIDE 4.2.0.CR2: Prepare for CR2 release [JBT Update Sites]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18468:
----------------------------------
Summary: For JBIDE 4.2.0.CR2: Prepare for CR2 release [JBT Update Sites]
Key: JBIDE-18468
URL: https://issues.jboss.org/browse/JBIDE-18468
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: updatesite
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.CR2 [JBT Update Sites]: Please perform the following tasks:
0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise, for all other projects:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA.
[Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions
{code}
mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT
mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT
{code}
5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*:
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
4. 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 JBT Update Sites task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-15816) [Config Editor] Add new lines when adding Preferences or Access to cordova config.xml via Cordova Configuration Editor
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15816?page=com.atlassian.jira.plugi... ]
Gorkem Ercan reassigned JBIDE-15816:
------------------------------------
Assignee: Gorkem Ercan
> [Config Editor] Add new lines when adding Preferences or Access to cordova config.xml via Cordova Configuration Editor
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15816
> URL: https://issues.jboss.org/browse/JBIDE-15816
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: JBT 4.1.1 Beta1a Beta1-v20131026-0906-B486
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Minor
> Fix For: 4.3.0.Alpha1
>
>
> 1. Create new Hybrid Mobile project
> 2. Open config.xml file in Cordova Configuration Editor
> 3. Add Preference or Access
> ASSERT: Preference or Access is added to config.xml source
> It would be nice if added Preferences or Access is added to new line in config.xml instead of adding it directly at the end of previously added item
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months