[JBoss JIRA] (JBDS-2846) For JBDS 7.1.0.GA: Prepare for Final/GA release
by Nick Boldt (JIRA)
Nick Boldt created JBDS-2846:
--------------------------------
Summary: For JBDS 7.1.0.GA: Prepare for Final/GA release
Key: JBDS-2846
URL: https://issues.jboss.org/browse/JBDS-2846
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public (Everyone can see)
Components: installer
Reporter: Nick Boldt
Priority: Blocker
Fix For: 7.1.0.GA
For JBDS 7.1.0.GA: Please perform the following tasks:
0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, 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.1.1.Final or 7.1.0.GA
[Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Final-SNAPSHOT</version>
</parent>
{code}
2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.2.Alpha1-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.30.6.Final
mvn clean verify -Dtpc.version=4.31.1.Final
{code}
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16195) For JBIDE 4.1.1.Final: Prepare for Final/GA release
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16195:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Prepare for Final/GA release
Key: JBIDE-16195
URL: https://issues.jboss.org/browse/JBIDE-16195
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.1.1.Final
For JBIDE 4.1.1.Final: Please perform the following tasks:
0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, 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.1.1.Final or 7.1.0.GA
[Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Final-SNAPSHOT</version>
</parent>
{code}
2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.2.Alpha1-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.30.6.Final
mvn clean verify -Dtpc.version=4.31.1.Final
{code}
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-2846
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16196) For JBIDE 4.1.1.Final: Prepare for Final/GA release [Aerogear]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16196:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Prepare for Final/GA release [Aerogear]
Key: JBIDE-16196
URL: https://issues.jboss.org/browse/JBIDE-16196
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: aerogear-hybrid
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Final [Aerogear]: Please perform the following tasks:
0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, 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.1.1.Final or 7.1.0.GA
[Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Final-SNAPSHOT</version>
</parent>
{code}
2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.2.Alpha1-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.30.6.Final
mvn clean verify -Dtpc.version=4.31.1.Final
{code}
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16197) For JBIDE 4.1.1.Final: Prepare for Final/GA release [JBT Update Sites]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16197:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Prepare for Final/GA release [JBT Update Sites]
Key: JBIDE-16197
URL: https://issues.jboss.org/browse/JBIDE-16197
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: updatesite
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Final [JBT Update Sites]: Please perform the following tasks:
0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, 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.1.1.Final or 7.1.0.GA
[Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Final-SNAPSHOT</version>
</parent>
{code}
2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.2.Alpha1-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.30.6.Final
mvn clean verify -Dtpc.version=4.31.1.Final
{code}
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2844) Management API Server Adapter
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2844?page=com.atlassian.jira.plugin.... ]
Burr Sutter updated JBDS-2844:
------------------------------
Description:
Related to JBIDE-14073 and EAP6-1
The current EAP/JBossAS/Wildfly Server Adapter often interacts with the underlying file-system of the app server. Users have asked that the following scenarios be supported:
- Remote Server Start/Stop
- Remote Server Deployment/Undeployment
- Remote Server single file update (e.g. html, js, jsp, xhtml, etc) with hot-deployment (to be worked out with the Wildfly team)
- Remote Server Log Viewing
and while the focus here in on remote servers, it should work just as well with localhost-based servers.
Also related, not having the actual server code locally installed, being able to work wholly with a remote server (comes up in the Data Virt/Teiid world).
was:
Related to JBIDE-14073
The current EAP/JBossAS/Wildfly Server Adapter often interacts with the underlying file-system of the app server. Users have asked that the following scenarios be supported:
- Remote Server Start/Stop
- Remote Server Deployment/Undeployment
- Remote Server single file update (e.g. html, js, jsp, xhtml, etc) with hot-deployment (to be worked out with the Wildfly team)
- Remote Server Log Viewing
and while the focus here in on remote servers, it should work just as well with localhost-based servers.
Also related, not having the actual server code locally installed, being able to work wholly with a remote server (comes up in the Data Virt/Teiid world).
> Management API Server Adapter
> -----------------------------
>
> Key: JBDS-2844
> URL: https://issues.jboss.org/browse/JBDS-2844
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: server
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
>
> Related to JBIDE-14073 and EAP6-1
> The current EAP/JBossAS/Wildfly Server Adapter often interacts with the underlying file-system of the app server. Users have asked that the following scenarios be supported:
> - Remote Server Start/Stop
> - Remote Server Deployment/Undeployment
> - Remote Server single file update (e.g. html, js, jsp, xhtml, etc) with hot-deployment (to be worked out with the Wildfly team)
> - Remote Server Log Viewing
> and while the focus here in on remote servers, it should work just as well with localhost-based servers.
> Also related, not having the actual server code locally installed, being able to work wholly with a remote server (comes up in the Data Virt/Teiid world).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16187) For JBIDE 4.1.1.Final: Code Freeze + Branch [JavaEE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16187:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Code Freeze + Branch [JavaEE]
Key: JBIDE-16187
URL: https://issues.jboss.org/browse/JBIDE-16187
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsf, cdi-extensions, seam2, cdi
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Final [JavaEE]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
1. *IN THE {color:blue}4.1.1.x{color} branch*, update your root pom to use parent pom version *4.1.1.Final-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Final-SNAPSHOT</version>
</parent>
{code}
2. *IN THE {color:orange}4.1.x{color} branch*, update your root pom to use parent pom version *4.1.2.Alpha1-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.2.Alpha1-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.30.6.Final
mvn clean verify -Dtpc.version=4.31.1.Final
{code}
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 JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16188) For JBIDE 4.1.1.Final: Code Freeze + Branch [JST]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16188:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Code Freeze + Branch [JST]
Key: JBIDE-16188
URL: https://issues.jboss.org/browse/JBIDE-16188
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Final [JST]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
1. *IN THE {color:blue}4.1.1.x{color} branch*, update your root pom to use parent pom version *4.1.1.Final-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Final-SNAPSHOT</version>
</parent>
{code}
2. *IN THE {color:orange}4.1.x{color} branch*, update your root pom to use parent pom version *4.1.2.Alpha1-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.2.Alpha1-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.30.6.Final
mvn clean verify -Dtpc.version=4.31.1.Final
{code}
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16189) For JBIDE 4.1.1.Final: Code Freeze + Branch [Forge]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16189:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Code Freeze + Branch [Forge]
Key: JBIDE-16189
URL: https://issues.jboss.org/browse/JBIDE-16189
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: forge
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Final [Forge]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
1. *IN THE {color:blue}4.1.1.x{color} branch*, update your root pom to use parent pom version *4.1.1.Final-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Final-SNAPSHOT</version>
</parent>
{code}
2. *IN THE {color:orange}4.1.x{color} branch*, update your root pom to use parent pom version *4.1.2.Alpha1-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.2.Alpha1-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.30.6.Final
mvn clean verify -Dtpc.version=4.31.1.Final
{code}
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 Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16192) For JBIDE 4.1.1.Final: Code Freeze + Branch [Central]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16192:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Code Freeze + Branch [Central]
Key: JBIDE-16192
URL: https://issues.jboss.org/browse/JBIDE-16192
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: central, maven, project-examples
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Final [Central]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
1. *IN THE {color:blue}4.1.1.x{color} branch*, update your root pom to use parent pom version *4.1.1.Final-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Final-SNAPSHOT</version>
</parent>
{code}
2. *IN THE {color:orange}4.1.x{color} branch*, update your root pom to use parent pom version *4.1.2.Alpha1-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.2.Alpha1-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.30.6.Final
mvn clean verify -Dtpc.version=4.31.1.Final
{code}
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 Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months