February 2014 - jbosstools-issues

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

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2848: ----------------------------- CDW release: + (was: ?) > 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: Alexey Kazakov > Priority: Critical > Labels: QE_JBDS80_needinfo > > 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

11 years, 10 months

1
0
0 / 0

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

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2848: ------------------------------- CDW qa_ack: + (was: ?) > 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: Alexey Kazakov > Priority: Critical > Labels: QE_JBDS80_needinfo > > 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

11 years, 10 months

1
0
0 / 0

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

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-2848: ------------------------------------ It's not optimal to be adding support for more and more usage all the way up to GA. However, if most of these are completed in Beta1, and the remainder in Beta2, then QE can 'ack' this requirement. <ldimaggi_wfh> jpallich, maxandersen when can we stop adding usage? in beta2? <jpallich> ldimaggi_wfh: no new features after B2 - correct > 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: Alexey Kazakov > Priority: Critical > Labels: QE_JBDS80_needinfo > > 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2864) Support faster turnarounds (with possibly hot deploy)

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2864: ----------------------------- CDW release: + (was: ?) > Support faster turnarounds (with possibly hot deploy) > ----------------------------------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2864) Support faster turnarounds (with possibly hot deploy)

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2864: ------------------------------- CDW qa_ack: + (was: ?) > Support faster turnarounds (with possibly hot deploy) > ----------------------------------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16665) Add Sapphire to TP

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16665?page=com.atlassian.jira.plugi... ] Snjezana Peco edited comment on JBIDE-16665 at 2/28/14 1:33 PM: ---------------------------------------------------------------- No, it isn't. was (Author: snjeza): No, It isn't. > Add Sapphire to TP > ------------------ > > Key: JBIDE-16665 > URL: https://issues.jboss.org/browse/JBIDE-16665 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, testing-tools > Affects Versions: 4.2.0.Alpha2 > Reporter: Snjezana Peco > > Reason: Required by new feature described in JBIDE-15394 > License and owner: EPL, Eclipse > Original repository: http://download.eclipse.org/sapphire/0.7/repository > JBoss Mirrored repository: http://downloads.jboss.org/jbosstools/updates/requirements/sapphire > Source: Yes > Affected projects: arquillian > Required in devstudio: No > Type of dependency: > List of bundles added: > org.eclipse.sapphire.java > org.eclipse.sapphire.java.jdt > org.eclipse.sapphire.java.jdt.ui > org.eclipse.sapphire.modeling > org.eclipse.sapphire.modeling.xml > org.eclipse.sapphire.osgi > org.eclipse.sapphire.osgi.fragment > org.eclipse.sapphire.platform > org.eclipse.sapphire.ui > org.eclipse.sapphire.ui.swt.gef > org.eclipse.sapphire.ui.swt.xml.editor > org.eclipse.sapphire.workspace > org.eclipse.sapphire.workspace.ui > org.objectweb.asm -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16665) Add Sapphire to TP

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16665?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16665: --------------------------------------- No, It isn't. > Add Sapphire to TP > ------------------ > > Key: JBIDE-16665 > URL: https://issues.jboss.org/browse/JBIDE-16665 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, testing-tools > Affects Versions: 4.2.0.Alpha2 > Reporter: Snjezana Peco > > Reason: Required by new feature described in JBIDE-15394 > License and owner: EPL, Eclipse > Original repository: http://download.eclipse.org/sapphire/0.7/repository > JBoss Mirrored repository: http://downloads.jboss.org/jbosstools/updates/requirements/sapphire > Source: Yes > Affected projects: arquillian > Required in devstudio: No > Type of dependency: > List of bundles added: > org.eclipse.sapphire.java > org.eclipse.sapphire.java.jdt > org.eclipse.sapphire.java.jdt.ui > org.eclipse.sapphire.modeling > org.eclipse.sapphire.modeling.xml > org.eclipse.sapphire.osgi > org.eclipse.sapphire.osgi.fragment > org.eclipse.sapphire.platform > org.eclipse.sapphire.ui > org.eclipse.sapphire.ui.swt.gef > org.eclipse.sapphire.ui.swt.xml.editor > org.eclipse.sapphire.workspace > org.eclipse.sapphire.workspace.ui > org.objectweb.asm -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16667) Arquillian VM arguments parameters not saved

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16667?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16667: ----------------------------------- Component/s: testing-tools > Arquillian VM arguments parameters not saved > -------------------------------------------- > > Key: JBIDE-16667 > URL: https://issues.jboss.org/browse/JBIDE-16667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.Final > Reporter: Rich DiCroce > > Open Window -> Preferences and navigate to JBoss Tools -> Arquillian. > Check off "Enable default VM arguments" and click Apply. > Close and re-open Eclipse and navigate back to the same screen. > "Enable default VM arguments" is not checked. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16667) Arquillian VM arguments parameters not saved

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16667?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-16667: -------------------------------------- Assignee: Snjezana Peco > Arquillian VM arguments parameters not saved > -------------------------------------------- > > Key: JBIDE-16667 > URL: https://issues.jboss.org/browse/JBIDE-16667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.Final > Reporter: Rich DiCroce > Assignee: Snjezana Peco > > Open Window -> Preferences and navigate to JBoss Tools -> Arquillian. > Check off "Enable default VM arguments" and click Apply. > Close and re-open Eclipse and navigate back to the same screen. > "Enable default VM arguments" is not checked. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16651) Remove hard-coded enterprise dependency resolution for upcoming archetypes embedding the RedHat Maven repo

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16651?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-16651. --------------------------------- Resolution: Done Patch applied > Remove hard-coded enterprise dependency resolution for upcoming archetypes embedding the RedHat Maven repo > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16651 > URL: https://issues.jboss.org/browse/JBIDE-16651 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: maven, project-examples > Affects Versions: 4.1.1.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.2.CR1 > > > In JBoss Central, when an Enterprise runtime is selected for any given Archetype, we check if the Red Hat Enterprise repository is available by trying to resolve a redhat version of org.jboss.spec:jboss-javaee-web-6.0. Then, if some essential dependencies are defined in stacks.yaml, we also try to resolve these. If the dependencies can't be resolved, a warning message appears with a link allowing users to add the RH repo to their Maven settings.xml > Upcoming archetypes will have the Red Hat repository already added to the generated pom.xml, so adding it to settings.xml becomes unnecessary. However, we'd get false positive warning by trying to resolve org.jboss.spec:jboss-javaee-web-6.0 from the settings.xml *before* generating the archetype. > Our goal is to remove the hardcoded check from MavenArtifactHelper and, when necessary, declare org.jboss.spec:jboss-javaee-web-6.0 as an essential dependency in stacks.yaml for *old* archetypes that do not add the RH repo to the gen'd pom.xml -- 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

11 years, 10 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 February 2014