February 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on JBDS-2734: ------------------------------------------ Update on this. As of Forge 2.1.1, we have support for the Merged/Single-page wizards you are asking for. So 6 with 1-2 options each page becomes 1 page with 5-12 options in order. The scaffold just needs to be updated to use this (minor change.) So this is in line. > Forge 2 in JBDS > --------------- > > Key: JBDS-2734 > URL: https://issues.jboss.org/browse/JBDS-2734 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: forge, requirements > Reporter: Burr Sutter > Assignee: Koen Aers > Fix For: 8.0.0.Beta1 > > > Is Forge 2 ready to be included in JBDS ? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2913) Console log when running EAP 6.2.x not formatted correctly

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-2913?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-2913: ----------------------------------- I am also unable to replicate in jbds 7.1 on a linux environment. When I open the launch configuration, I see "-Dorg.jboss.logmanager.nocolor=true " in the vm-args. Do you see that as well? If I remove those flags, then I see the incorrect color characters, but, with a new server, the launch config has the proper flags and the server doesn't show the color characters. > Console log when running EAP 6.2.x not formatted correctly > ---------------------------------------------------------- > > Key: JBDS-2913 > URL: https://issues.jboss.org/browse/JBDS-2913 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: server > Affects Versions: 7.1.0.GA > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Fix For: 7.1.1.CR1 > > Attachments: EAP-6.1.0.png, EAP-6.2.1.png > > > When running EAP from JBDS the console logging shows strange characters from the logging. See screen shots comparing EAP 6.1.0 to EAP 6.2.1 (this also happens on EAP 6.2.0) -- 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, 1 month

1
0
0 / 0

[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

12 years, 1 month

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

12 years, 1 month

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

12 years, 1 month

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

12 years, 1 month

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

12 years, 1 month

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

12 years, 1 month

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

12 years, 1 month

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

12 years, 1 month

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