December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16071) Duplicate cheat sheet options in Project Examples Preferences

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16071?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16071: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Duplicate cheat sheet options in Project Examples Preferences > ------------------------------------------------------------- > > Key: JBIDE-16071 > URL: https://issues.jboss.org/browse/JBIDE-16071 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.1.CR1 > Reporter: Michelle Murray > Assignee: Snjezana Peco > Fix For: 4.2.0.Alpha2 > > Attachments: Central_cheatsheet.png > > > Click Window > Preferences > JBoss Tools > Project Examples. > The check box options include 'show readme/cheatsheet file' and then further down specifically for cheat sheets radio buttons for cheat sheet behavior. > !Central_cheatsheet.png! > I think the labelling of 'show readme/cheatsheet file' is left over from earlier. With the new cheat sheet functionality, I think that option should just read 'show readme file'. And then the radio button 'Always show' etc. deal with cheat sheets. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2842) Add UI for central connectors update

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-2842?page=com.atlassian.jira.plugin.... ] Snjezana Peco updated JBDS-2842: -------------------------------- Fix Version/s: 8.0.0.Alpha2 (was: 8.0.0.Alpha1) > Add UI for central connectors update > ------------------------------------ > > Key: JBDS-2842 > URL: https://issues.jboss.org/browse/JBDS-2842 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.1.0.GA > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 8.0.0.Alpha2 > > > Provide UI to inform users that there is an updated connector in JBoss Central. > Currently, when a user has a connector installed (e.g. GPE) and this connector gets updated, the only indication of that is that the connector is visible in Central even though it has been installed (and therefore would not normally show up). > There should be some element telling users that a given installed connector can be updated, rather than it appearing as new. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15355) The JBoss Central quickstarts should include the .html version of the readme files.

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15355?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-15355: ---------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Alpha1) > The JBoss Central quickstarts should include the .html version of the readme files. > ----------------------------------------------------------------------------------- > > Key: JBIDE-15355 > URL: https://issues.jboss.org/browse/JBIDE-15355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Reporter: Burr Sutter > Assignee: Snjezana Peco > Fix For: 4.2.x > > > The helloworld quickstart on JBoss Central offers the end-user a readme.md - which is not easily readable by the average human. It includes a phrase that looks like > If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. > The JBoss Central quickstarts should include the .html version of the readme files. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14899) Select all features button on Software/Update tab would be handy

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14899?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-14899: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Select all features button on Software/Update tab would be handy > ---------------------------------------------------------------- > > Key: JBIDE-14899 > URL: https://issues.jboss.org/browse/JBIDE-14899 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.0.Beta2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.2.0.Alpha2 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14804) Uninstall from jboss central

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14804?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-14804: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Uninstall from jboss central > ---------------------------- > > Key: JBIDE-14804 > URL: https://issues.jboss.org/browse/JBIDE-14804 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Fix For: 4.2.0.Alpha2 > > > since I can install from central, shouldn't we also provide an uninstall button for our connectors? -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16198) For JBIDE 4.1.1.Final: Prepare for Final/GA release [VPE]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16198?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov reassigned JBIDE-16198: ---------------------------------------------- Assignee: Konstantin Marmalyukov > For JBIDE 4.1.1.Final: Prepare for Final/GA release [VPE] > --------------------------------------------------------- > > Key: JBIDE-16198 > URL: https://issues.jboss.org/browse/JBIDE-16198 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.1.1.Final > > > For JBIDE 4.1.1.Final [VPE]: Please perform the following tasks: > 0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise, for all other projects: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA > [Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.1.Final-SNAPSHOT</version> > </parent> > {code} > 2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.2.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.30.6.Final > mvn clean verify -Dtpc.version=4.31.1.Final > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16198) For JBIDE 4.1.1.Final: Prepare for Final/GA release [VPE]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16198?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov closed JBIDE-16198. ------------------------------------------ Resolution: Done > For JBIDE 4.1.1.Final: Prepare for Final/GA release [VPE] > --------------------------------------------------------- > > Key: JBIDE-16198 > URL: https://issues.jboss.org/browse/JBIDE-16198 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.1.1.Final > > > For JBIDE 4.1.1.Final [VPE]: Please perform the following tasks: > 0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise, for all other projects: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA > [Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.1.Final-SNAPSHOT</version> > </parent> > {code} > 2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.2.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.30.6.Final > mvn clean verify -Dtpc.version=4.31.1.Final > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-224) Final component updates - esb, fuse, teiid for 4.1.3.CR1/ .Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-224?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-224: ---------------------------------- https://github.com/jbosstools/jbosstools-integration-stack/pull/158 > Final component updates - esb, fuse, teiid for 4.1.3.CR1/ .Final > ---------------------------------------------------------------- > > Key: JBTIS-224 > URL: https://issues.jboss.org/browse/JBTIS-224 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.1.3.CR1 > Reporter: Paul Leacu > Assignee: Paul Leacu > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-224) Final component updates - esb, fuse, teiid for 4.1.3.CR1/ .Final

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-224: -------------------------------- Summary: Final component updates - esb, fuse, teiid for 4.1.3.CR1/ .Final Key: JBTIS-224 URL: https://issues.jboss.org/browse/JBTIS-224 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.1.3.CR1 Reporter: Paul Leacu Assignee: Paul Leacu -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-222) add org.jboss.tools.common.test plugin to JBT coretests for esb

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-222?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-222. ------------------------------ Fix Version/s: 4.1.5.CR2-TP Resolution: Done Added ESB JBT coretests plugins that were needed. > add org.jboss.tools.common.test plugin to JBT coretests for esb > --------------------------------------------------------------- > > Key: JBTIS-222 > URL: https://issues.jboss.org/browse/JBTIS-222 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.5.CR1-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.5.CR2-TP > > > respin TP for coretests missing dependency for esb -- 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, 4 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 December 2013