September 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2724) Include "Mylyn Builds Connector: Hudson/Jenkins" org.eclipse.mylyn.hudson.feature in both JBT & JBDS Central

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2724?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2724: ------------------------------- Component/s: requirements > Include "Mylyn Builds Connector: Hudson/Jenkins" org.eclipse.mylyn.hudson.feature in both JBT & JBDS Central > ------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2724 > URL: https://issues.jboss.org/browse/JBDS-2724 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Attachments: JBDS7_central.png > > > We should make it easier to work with jenkins for our devops users. > Start by including the Jenkins plugin (from Max: Mylyn build plugin) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2724) Include "Mylyn Builds Connector: Hudson/Jenkins" org.eclipse.mylyn.hudson.feature in both JBT & JBDS Central

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2724?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2724: ------------------------------- CDW pm_ack: + (was: ?) > Include "Mylyn Builds Connector: Hudson/Jenkins" org.eclipse.mylyn.hudson.feature in both JBT & JBDS Central > ------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2724 > URL: https://issues.jboss.org/browse/JBDS-2724 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Attachments: JBDS7_central.png > > > We should make it easier to work with jenkins for our devops users. > Start by including the Jenkins plugin (from Max: Mylyn build plugin) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2358) GWT Web example generates warnings

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2358?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2358: ----------------------------------- ping [~jfuerth] > GWT Web example generates warnings > ---------------------------------- > > Key: JBDS-2358 > URL: https://issues.jboss.org/browse/JBDS-2358 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 6.0.0.Alpha2 > Environment: Version: 6.0.0.Alpha2 > Build id: Alpha2-v20121004-2330-B40 > Build date: 20121004-2330 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: examplewarnings > Attachments: JavaBuildProjectPreferences.png > > > The GWT project generates these warnings: > No connection specified for project. No database-specific validation will be performed. > jboss-gwt-webapp > Overriding managed version 1.0.0.GA for validation-api > pom.xml /jboss-gwt-webapp > line 240 > No bean is eligible for injection to the injection point [JSR-299 §5.2.1] > KitchenSinkApp.java > /jboss-gwt-webapp/src/main/java/org/jboss/tools/gwt/kitchensink/client/local > line 41 > Unnecessary @SuppressWarnings("unused") > Resources.java > /jboss-gwt-webapp/src/main/java/org/jboss/tools/gwt/kitchensink/util > line 24 > Missing src folder configured in Java Build Path Project Preferences > !JavaBuildProjectPreferences.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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2725) Essential but trivial bugfixes/updates to individual plugins

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2725?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2725: ------------------------------- CDW pm_ack: + (was: ?) > Essential but trivial bugfixes/updates to individual plugins > ------------------------------------------------------------ > > Key: JBDS-2725 > URL: https://issues.jboss.org/browse/JBDS-2725 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: integration, requirements > Reporter: Max Rydahl Andersen > > We should include essential but trivial fixes for the bugs in plugins that have been found by QE/users. > All those should be linked to this jira. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14728) Distinguish between started and not started servers in MBean Explorer

by Jakub Niedermertl (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14728?page=com.atlassian.jira.plugi... ] Jakub Niedermertl closed JBIDE-14728. ------------------------------------- ok, closing Version: 7.1.0.Alpha1 Build id: Alpha1-v20130909-0132-B378 > Distinguish between started and not started servers in MBean Explorer > --------------------------------------------------------------------- > > Key: JBIDE-14728 > URL: https://issues.jboss.org/browse/JBIDE-14728 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > Lets imagine these steps: > STEP: define a lot of servers in servers view > STEP: run one of them > STEP: open MBean Explorer view > STEP: in opened view (MBean) try to connect to started server > last step is very difficult for user if there are many similar server names or he doesn't remember exactly which server he started before. > It would be useful if user has possibility to somehow recognize started and not started servers. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2725) Essential but trivial bugfixes/updates to individual plugins

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2725?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2725: ------------------------------- Component/s: requirements > Essential but trivial bugfixes/updates to individual plugins > ------------------------------------------------------------ > > Key: JBDS-2725 > URL: https://issues.jboss.org/browse/JBDS-2725 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: integration, requirements > Reporter: Max Rydahl Andersen > > We should include essential but trivial fixes for the bugs in plugins that have been found by QE/users. > All those should be linked to this jira. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2725) Essential but trivial bugfixes/updates to individual plugins

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2725?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2725: ----------------------------- CDW pm_ack: ? (was: +) > Essential but trivial bugfixes/updates to individual plugins > ------------------------------------------------------------ > > Key: JBDS-2725 > URL: https://issues.jboss.org/browse/JBDS-2725 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: integration, requirements > Reporter: Max Rydahl Andersen > > We should include essential but trivial fixes for the bugs in plugins that have been found by QE/users. > All those should be linked to this jira. -- 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, 7 months

1
0
0 / 0

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

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2727: ------------------------------- CDW pm_ack: + (was: ?) > 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 > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2745: ----------------------------------- IUs defined in <connectorDescriptor> elements can have a version attribute, so there may be a way to handle that use case (different versions for Experimental vs Supported). Needs more brainstorming though. > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- 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, 7 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2727: -------------------------------------- Component/s: requirements > 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 > > 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, 7 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 September 2013