[JBoss JIRA] (JBDS-2849) Document Offline Usage
by Burr Sutter (JIRA)
Burr Sutter created JBDS-2849:
---------------------------------
Summary: Document Offline Usage
Key: JBDS-2849
URL: https://issues.jboss.org/browse/JBDS-2849
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Burr Sutter
Working with the Training team, document how JBDS is to be used in an offline state.
--
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-2848) Anonymous Usage Stats
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2848:
-----------------------------
CDW pm_ack: ?
CDW release: ?
> Anonymous Usage Stats
> ---------------------
>
> Key: JBDS-2848
> URL: https://issues.jboss.org/browse/JBDS-2848
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
>
> We currently know that people are using JBDS/JBoss Tools but not specifically which features people are actively using. Our key base metric is "daily usage".
> Areas worth tracking include (in priority order):
> - Use of the OpenShift Wizard to successful completion vs error
> - Use of the archetypes on JBoss Central (adding Hybrid/Cordova in JBDS 8)
> - Successful installation of the features found on Software/Update tab of JBoss Central
> - Use of the JSF/RichFaces Visual Page Editor
> - Use of the Hibernate Tooling
> - Use of the jQuery Mobile Palette
> - Use of BrowserSim
> - Use of CordovaSim
> We will also need to update http://www.jboss.org/tools/usage
> Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool)
> Our metric gathering service should be "scalable" enough to allow for tracking of the individual SOA features such as Drools, jBPM, Switchyard, Camel, etc in the future.
--
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-16209) For JBIDE 4.1.1.Final: Prepare for Final/GA release [Central]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16209:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Prepare for Final/GA release [Central]
Key: JBIDE-16209
URL: https://issues.jboss.org/browse/JBIDE-16209
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 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 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
[JBoss JIRA] (JBIDE-16208) For JBIDE 4.1.1.Final: Prepare for Final/GA release [Arquillian]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16208:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Prepare for Final/GA release [Arquillian]
Key: JBIDE-16208
URL: https://issues.jboss.org/browse/JBIDE-16208
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: testing-tools
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Final [Arquillian]: 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 Arquillian 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-16211) For JBIDE 4.1.1.Final: Prepare for Final/GA release [LiveReload]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16211:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Prepare for Final/GA release [LiveReload]
Key: JBIDE-16211
URL: https://issues.jboss.org/browse/JBIDE-16211
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: livereload
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Final [LiveReload]: 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 LiveReload 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-16210) For JBIDE 4.1.1.Final: Prepare for Final/GA release [Portlet]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16210:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Prepare for Final/GA release [Portlet]
Key: JBIDE-16210
URL: https://issues.jboss.org/browse/JBIDE-16210
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: portal-gatein
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Final [Portlet]: 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 Portlet 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