[JBoss JIRA] (JBDS-2838) OpenShift Usability
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2838?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2838:
----------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.)
> OpenShift Usability
> -------------------
>
> Key: JBDS-2838
> URL: https://issues.jboss.org/browse/JBDS-2838
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
> Fix For: 8.0.0.GA
>
>
> This task is to explore the overall usability of the OpenShift Wizard, OpenShift Explorer, the adapter in the Servers Tab and review things like Run As on OpenShift (JBIDE-16069)
--
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 Rodney Russ (JIRA)
[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ]
Rodney Russ updated JBDS-2848:
------------------------------
Assignee: Andre Dietisheim
> 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
> Assignee: Andre Dietisheim
>
> 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-16208) For JBIDE 4.1.1.Final: Prepare for Final/GA release [Arquillian]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16208?page=com.atlassian.jira.plugi... ]
Snjezana Peco resolved JBIDE-16208.
-----------------------------------
Resolution: Done
> 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
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Final
>
>
> 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-16208) For JBIDE 4.1.1.Final: Prepare for Final/GA release [Arquillian]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16208?page=com.atlassian.jira.plugi... ]
Snjezana Peco closed JBIDE-16208.
---------------------------------
> 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
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Final
>
>
> 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] (JBDS-2852) Database/source/connection Usability
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2852:
-----------------------------
CDW pm_ack: ?
CDW release: ?
> Database/source/connection Usability
> ------------------------------------
>
> Key: JBDS-2852
> URL: https://issues.jboss.org/browse/JBDS-2852
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
>
> Connecting to a database from within JBDS/Eclipse is a multi-step, multi-screen, potentially error-prone challenge.
> Forge is involved as it can generate entities from schema
> Datasources are needed in/on AS/Wildfly/EAP in order for the project deploy
> Persistence.xml may needed to be tweaked for the datasource
> End-user would like to navigate the schema in the DTP/Hibernate Tools, interactively review the data and there was once a feature for viewing an ORM diagram that I seem to have forgotten how it is displayed.
> What happens when a project that needs a database connection is imported into the IDE?
> This was partially addressed with
> https://issues.jboss.org/browse/JBIDE-15263
> Let's see if we can continue to improve the workflow by reducing steps, making it more obvious what steps are required (e.g. hey developer, get the mysql driver .jar), auto generating the -ds.xml, with a decent explanation for the end-user to follow.
--
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-2852) Database/source/connection Usability
by Burr Sutter (JIRA)
Burr Sutter created JBDS-2852:
---------------------------------
Summary: Database/source/connection Usability
Key: JBDS-2852
URL: https://issues.jboss.org/browse/JBDS-2852
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Burr Sutter
Connecting to a database from within JBDS/Eclipse is a multi-step, multi-screen, potentially error-prone challenge.
Forge is involved as it can generate entities from schema
Datasources are needed in/on AS/Wildfly/EAP in order for the project deploy
Persistence.xml may needed to be tweaked for the datasource
End-user would like to navigate the schema in the DTP/Hibernate Tools, interactively review the data and there was once a feature for viewing an ORM diagram that I seem to have forgotten how it is displayed.
What happens when a project that needs a database connection is imported into the IDE?
This was partially addressed with
https://issues.jboss.org/browse/JBIDE-15263
Let's see if we can continue to improve the workflow by reducing steps, making it more obvious what steps are required (e.g. hey developer, get the mysql driver .jar), auto generating the -ds.xml, with a decent explanation for the end-user to follow.
--
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-2851) Team Usability
by Burr Sutter (JIRA)
Burr Sutter created JBDS-2851:
---------------------------------
Summary: Team Usability
Key: JBDS-2851
URL: https://issues.jboss.org/browse/JBDS-2851
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Burr Sutter
It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as
- how to integrate with CVS, SVN, Git
- how to "import" a Maven-based project from SCM
"Check out Maven Projects from SCM" has misfired for some users
- how to "checkin" changes back to the SCM
To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things.
For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically.
--
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