January 2014 - jbosstools-issues - Jboss List Archives

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2851: --------------------------------------- Docs Q: Are there any JBDS plug-ins providing version control (cvs/svn/git) actions? > 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) > Components: requirements > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2848) Usage Stats for actual used features

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2848: --------------------------------------- Docs: Once this is implemented will need info about what exactly is being tracked in order to update the documentation [1]. [1] https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... > Usage Stats for actual used features > ------------------------------------ > > 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) > Components: requirements, usage > 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 and https://devstudio.jboss.com/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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2848) Usage Stats for actual used features

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2848: ---------------------------------- Description: 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 and https://devstudio.jboss.com/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. was: 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. > Usage Stats for actual used features > ------------------------------------ > > 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) > Components: requirements, usage > 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 and https://devstudio.jboss.com/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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2732) Add usage tracking for installs from JBDS central

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2732?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2732: ---------------------------------- Description: It would be interesting to know which connectors/plugins gets installed from central We will also need to update http://www.jboss.org/tools/usage and https://devstudio.jboss.com/usage/ was:It would be interesting to know which connectors/plugins gets installed from central > Add usage tracking for installs from JBDS central > ------------------------------------------------- > > Key: JBDS-2732 > URL: https://issues.jboss.org/browse/JBDS-2732 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: requirements, usage > Reporter: Max Rydahl Andersen > > It would be interesting to know which connectors/plugins gets installed from central > We will also need to update http://www.jboss.org/tools/usage and https://devstudio.jboss.com/usage/ -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2732) Add usage tracking for installs from JBDS central

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2732?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2732: --------------------------------------- Docs Q: What additional usage info is this collecting? Is it just the *name* of additional JBDS/JBT and third-party plug-ins installed from JBoss Central? What other info might/will be collected about installs from Central plug-ins? > Add usage tracking for installs from JBDS central > ------------------------------------------------- > > Key: JBDS-2732 > URL: https://issues.jboss.org/browse/JBDS-2732 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: requirements, usage > Reporter: Max Rydahl Andersen > > It would be interesting to know which connectors/plugins gets installed from central -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2686) Investigate use of SpringSource's Quick Search in JBT/JBDS Central

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2686?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2686: ---------------------------------- Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Parent: JBDS-2869 Issue Type: Sub-task (was: Enhancement) > Investigate use of SpringSource's Quick Search in JBT/JBDS Central > ------------------------------------------------------------------ > > Key: JBDS-2686 > URL: https://issues.jboss.org/browse/JBDS-2686 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, discovery, requirements, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.0.Alpha2 > > > @fbricon wrote: > {quote} > This looks very interesting > http://blog.springsource.org/2013/07/11/eclipse-quick-search/ > And it -apparently- doesn't depend on other spring stuff, so I > think it's a good candidate for integration in JBT/JBDS. > {quote} > Update site: > http://dist.springsource.com/release/TOOLS/eclipse-integration-commons/ -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2515) JBDS70_0011: [Commit] (Dev) (P3) Scan ~/jboss-runtimes automatically

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2515?page=com.atlassian.jira.plugin.... ] Michelle Murray edited comment on JBDS-2515 at 1/14/14 11:50 PM: ----------------------------------------------------------------- Docs Q: I envisage this working as follows: * A runtime detection scan action occurs when someone creates a new workspace (either via switching and therefore creating a new workspace, or providing a path for a new workspace on IDE startup). * The scan action is the same as the scan action that currently occurs if runtime detection is triggered to scan a path on every IDE startup. * The action would scan the default path as listed in the Paths table of Window > Preferences > JBoss Tools > JBoss Runtime Detection (e.g., ~/path/to/jbdevstudio/runtimes). Is that right? Please correct me where I am wrong. was (Author: mmurray): I envisage this working as follows: * A runtime detection scan action occurs when someone creates a new workspace (either via switching and therefore creating a new workspace, or providing a path for a new workspace on IDE startup). * The scan action is the same as the scan action that currently occurs if runtime detection is triggered to scan a path on every IDE startup. * The action would scan the default path as listed in the Paths table of Window > Preferences > JBoss Tools > JBoss Runtime Detection (e.g., ~/path/to/jbdevstudio/runtimes). Is that right? Please correct me where I am wrong. > JBDS70_0011: [Commit] (Dev) (P3) Scan ~/jboss-runtimes automatically > -------------------------------------------------------------------- > > Key: JBDS-2515 > URL: https://issues.jboss.org/browse/JBDS-2515 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Max Rydahl Andersen > Priority: Minor > > Usecase is to not have to setup runtimes every time you create a new workspace. Useful for demos and training sessions and those using many runtimes (e.g. EAP 5.0.1, EAP 6.0.0, EAP 6.0.1, SOA-P 5.x.y, etc) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2564) JBDS70_1214: [Commit] (?) (P?) Fix support for multi-module maven projects

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2564?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2564: --------------------------------------- Docs Q: I am assuming this will not change what users have to do. Please correct me if I am wrong. > JBDS70_1214: [Commit] (?) (P?) Fix support for multi-module maven projects > -------------------------------------------------------------------------- > > Key: JBDS-2564 > URL: https://issues.jboss.org/browse/JBDS-2564 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Jiri Pallich > Assignee: Andre Dietisheim > Fix For: 8.0.0.GA > > > Could be better at detecting proper packaging type for the openshift profile. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2515) JBDS70_0011: [Commit] (Dev) (P3) Scan ~/jboss-runtimes automatically

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2515?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2515: --------------------------------------- I envisage this working as follows: * A runtime detection scan action occurs when someone creates a new workspace (either via switching and therefore creating a new workspace, or providing a path for a new workspace on IDE startup). * The scan action is the same as the scan action that currently occurs if runtime detection is triggered to scan a path on every IDE startup. * The action would scan the default path as listed in the Paths table of Window > Preferences > JBoss Tools > JBoss Runtime Detection (e.g., ~/path/to/jbdevstudio/runtimes). Is that right? Please correct me where I am wrong. > JBDS70_0011: [Commit] (Dev) (P3) Scan ~/jboss-runtimes automatically > -------------------------------------------------------------------- > > Key: JBDS-2515 > URL: https://issues.jboss.org/browse/JBDS-2515 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Max Rydahl Andersen > Priority: Minor > > Usecase is to not have to setup runtimes every time you create a new workspace. Useful for demos and training sessions and those using many runtimes (e.g. EAP 5.0.1, EAP 6.0.0, EAP 6.0.1, SOA-P 5.x.y, etc) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2564) JBDS70_1214: [Commit] (?) (P?) Fix support for multi-module maven projects

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2564?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2564: ----------------------------- CDW pm_ack: ? CDW release: ? > JBDS70_1214: [Commit] (?) (P?) Fix support for multi-module maven projects > -------------------------------------------------------------------------- > > Key: JBDS-2564 > URL: https://issues.jboss.org/browse/JBDS-2564 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Jiri Pallich > Assignee: Andre Dietisheim > Fix For: 8.0.0.GA > > > Could be better at detecting proper packaging type for the openshift profile. -- 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, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2014