November 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2821) Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2821?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2821: ----------------------------- CDW release: + (was: ?) > Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill > ----------------------------------------------------------------------------------- > > Key: JBDS-2821 > URL: https://issues.jboss.org/browse/JBDS-2821 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.1.0.Beta1 > Reporter: Michelle Murray > Assignee: Nick Boldt > Labels: respin-a > Fix For: 7.1.0.CR1 > > Attachments: Central_updates_exp.png > > > In JBoss Central, software/updates tab, Hybrid Mobile is labelled as > 1. "JBoss Hybrid Mobile Tools + CordovaSim *(Experimental)*" > 2. "by JBoss by ..., *Experimental*" > I think it is overkill to have "Experimental" twice. Can it just be in 2? Then 1. could be shortened and would look better. > !Central_updates_exp.png! -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2821) Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2821?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2821: ----------------------------- CDW pm_ack: + (was: ?) > Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill > ----------------------------------------------------------------------------------- > > Key: JBDS-2821 > URL: https://issues.jboss.org/browse/JBDS-2821 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.1.0.Beta1 > Reporter: Michelle Murray > Assignee: Nick Boldt > Labels: respin-a > Fix For: 7.1.0.CR1 > > Attachments: Central_updates_exp.png > > > In JBoss Central, software/updates tab, Hybrid Mobile is labelled as > 1. "JBoss Hybrid Mobile Tools + CordovaSim *(Experimental)*" > 2. "by JBoss by ..., *Experimental*" > I think it is overkill to have "Experimental" twice. Can it just be in 2? Then 1. could be shortened and would look better. > !Central_updates_exp.png! -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2821) Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2821?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2821: ----------------------------- CDW devel_ack: ? CDW pm_ack: ? CDW qa_ack: ? > Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill > ----------------------------------------------------------------------------------- > > Key: JBDS-2821 > URL: https://issues.jboss.org/browse/JBDS-2821 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.1.0.Beta1 > Reporter: Michelle Murray > Assignee: Nick Boldt > Labels: respin-a > Fix For: 7.1.0.CR1 > > Attachments: Central_updates_exp.png > > > In JBoss Central, software/updates tab, Hybrid Mobile is labelled as > 1. "JBoss Hybrid Mobile Tools + CordovaSim *(Experimental)*" > 2. "by JBoss by ..., *Experimental*" > I think it is overkill to have "Experimental" twice. Can it just be in 2? Then 1. could be shortened and would look better. > !Central_updates_exp.png! -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2821) Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2821?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2821: ----------------------------- CDW release: ? Status: New (was: New) CDW exception: + CDW blocker: + Target Release: 7.1.0.GA > Duplicate "Experimental" labelling for Hybrid Mobile etc. in update tab is overkill > ----------------------------------------------------------------------------------- > > Key: JBDS-2821 > URL: https://issues.jboss.org/browse/JBDS-2821 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.1.0.Beta1 > Reporter: Michelle Murray > Assignee: Nick Boldt > Labels: respin-a > Fix For: 7.1.0.CR1 > > Attachments: Central_updates_exp.png > > > In JBoss Central, software/updates tab, Hybrid Mobile is labelled as > 1. "JBoss Hybrid Mobile Tools + CordovaSim *(Experimental)*" > 2. "by JBoss by ..., *Experimental*" > I think it is overkill to have "Experimental" twice. Can it just be in 2? Then 1. could be shortened and would look better. > !Central_updates_exp.png! -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15630) Have "Report Bug" dialog actually report bugs

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15630?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-15630: ---------------------------------------- [~mickael_istria], [~dazarov] is already working on this new dialog based on JIRA Rest API. But we agreed with Max that we should gather all requirements first and describe what we want to get before we start implementing this dialog. > Have "Report Bug" dialog actually report bugs > --------------------------------------------- > > Key: JBIDE-15630 > URL: https://issues.jboss.org/browse/JBIDE-15630 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.1.1.Alpha1 > Reporter: Mickael Istria > Assignee: Daniel Azarov > Fix For: 4.2.x > > > When Mylyn/Jira connector is installed, the "Report Error" dialog should provide the possiblity to directly push report as a Jira, just like Mylyn does for Eclipse. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ] Brian Leathem commented on JBDS-2727: ------------------------------------- [~fbricon] I have no progress to report at this point. Any update on the timing constraints [~burrsutter]? > Cheatsheets for JBoss Central archetypes > ---------------------------------------- > > Key: JBDS-2727 > URL: https://issues.jboss.org/browse/JBDS-2727 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 7.1.0.GA > > Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md > > > Our archetypes should have cheatsheets when imported/opened into eclipse. > Priority > 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim > 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java > Basically walk the user through the flow of events (from the UI to the backend) in the application > 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16063) Aborting a command has strange behavior

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16063?page=com.atlassian.jira.plugi... ] Lincoln Baxter III commented on JBIDE-16063: -------------------------------------------- When I say I fixed it, I mean I changed "[killed]" to "^C". We won't be fixing the inconsistent abort behavior in Forge 1, since the architecture is really not designed to accommodate this. This is being fixed in Forge 2, so I think we should close this issue and re-open if it continues to be a problem there, but Koen is already looking at this tomorrow morning in the Forge 2 branch. > Aborting a command has strange behavior > ---------------------------------------- > > Key: JBIDE-16063 > URL: https://issues.jboss.org/browse/JBIDE-16063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Labels: respin-a > Fix For: 4.1.1.CR1 > > Attachments: forge-screen-1.png, forge-screen-2.png > > > I see 2 problems how aborting a command currently works. > * If the console is empty and you send Ctrl+C, then the text "[killed]" appears in the console. I guess nothing was actually killed. Then I try to for example create a new project and trigger: 'new-project --named testProject' and this command is swallowed or killed? Please see attached screenshot: > !forge-screen-1.png! > * Second, .. I tried several times to abort "an already in progress new-project" command but sometimes it succeeds and sometimes not. Like on my next screenshot. I figured out that it depends on the speed how fast I press the abort keys on the keyboard. It wasn't very hard for me to simulate the error. > !forge-screen-2.png! -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16063) Aborting a command has strange behavior

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16063?page=com.atlassian.jira.plugi... ] Lincoln Baxter III commented on JBIDE-16063: -------------------------------------------- Hey Pavol. This is a core feature of Forge 1 itself, so not a JBIDE issue. But I've fixed it as much as we will be able to, nonetheless. I don't believe this is critical, and will probably not make it into this release. Unless you think it is critical, we will probably not do another release of Forge 1 just for this. > Aborting a command has strange behavior > ---------------------------------------- > > Key: JBIDE-16063 > URL: https://issues.jboss.org/browse/JBIDE-16063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Labels: respin-a > Fix For: 4.1.1.CR1 > > Attachments: forge-screen-1.png, forge-screen-2.png > > > I see 2 problems how aborting a command currently works. > * If the console is empty and you send Ctrl+C, then the text "[killed]" appears in the console. I guess nothing was actually killed. Then I try to for example create a new project and trigger: 'new-project --named testProject' and this command is swallowed or killed? Please see attached screenshot: > !forge-screen-1.png! > * Second, .. I tried several times to abort "an already in progress new-project" command but sometimes it succeeds and sometimes not. Like on my next screenshot. I figured out that it depends on the speed how fast I press the abort keys on the keyboard. It wasn't very hard for me to simulate the error. > !forge-screen-2.png! -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16063) Aborting a command has strange behavior

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16063?page=com.atlassian.jira.plugi... ] Lincoln Baxter III commented on JBIDE-16063: -------------------------------------------- I would personally close this issue with "Wont Fix", but I think that's up to you anyway :) Let me know what you decide. > Aborting a command has strange behavior > ---------------------------------------- > > Key: JBIDE-16063 > URL: https://issues.jboss.org/browse/JBIDE-16063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Labels: respin-a > Fix For: 4.1.1.CR1 > > Attachments: forge-screen-1.png, forge-screen-2.png > > > I see 2 problems how aborting a command currently works. > * If the console is empty and you send Ctrl+C, then the text "[killed]" appears in the console. I guess nothing was actually killed. Then I try to for example create a new project and trigger: 'new-project --named testProject' and this command is swallowed or killed? Please see attached screenshot: > !forge-screen-1.png! > * Second, .. I tried several times to abort "an already in progress new-project" command but sometimes it succeeds and sometimes not. Like on my next screenshot. I figured out that it depends on the speed how fast I press the abort keys on the keyboard. It wasn't very hard for me to simulate the error. > !forge-screen-2.png! -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16068) update to latest jboss.org theme, especially "tabzilla"

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-16068: ------------------------------------------- Summary: update to latest jboss.org theme, especially "tabzilla" Key: JBIDE-16068 URL: https://issues.jboss.org/browse/JBIDE-16068 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: website Reporter: Max Rydahl Andersen talking with [~pmuir] and he pointed out we were missing the "tabzilla" component which is present on sites like wildfly.org. the upper right "red hat" button. That is probably just missing because we got our styles/css from earlier versions of .org theme. -- 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, 5 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 November 2013