September 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2767: ----------------------------- CDW devel_ack: ? (was: +) > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Rob Stryker > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2767: ----------------------------- CDW qa_ack: ? > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Rob Stryker > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2767: ----------------------------- CDW devel_ack: + (was: ?) > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Rob Stryker > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2767: ----------------------------- CDW devel_ack: ? > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Rob Stryker > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] Burr Sutter updated JBDS-2767: ------------------------------ CDW pm_ack: + (was: ?) Status: New (was: New) > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Rob Stryker > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-388) Update explicit 7.0 text references in docs to 7.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-388?page=com.atlassian.jira.plug... ] Nick Boldt commented on TOOLSDOC-388: ------------------------------------- I've already made changes in the 4.1.x/7.1.x branch so that references within JBDS to its update site (located at https://devstudio.jboss.com/updates/7.0/ ) refer to it as the 7.x site, not the 7.0 or 7.1 site. That way I won't have to update it again from 7.1 to 7.[whatever is decided*] later, when we do a maintenance release to pick up Kepler SR2. You might want to consider updating docs similarly to "7.x" so that you too won't need to change explicit refs in docs to "7.1" to "7.1.1" or "7.2" in 6 months when Kepler SR2 is out. > Update explicit 7.0 text references in docs to 7.1 > -------------------------------------------------- > > Key: TOOLSDOC-388 > URL: https://issues.jboss.org/browse/TOOLSDOC-388 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > Original Estimate: 5 hours, 30 minutes > Time Spent: 55 minutes > Remaining Estimate: 1 hour, 30 minutes > > Section that need updating > *Installation Guide* > * 2.2. Supported Operating Systems and Architectures > * 2.3. Computer Memory > * 2.4. Compatible Java Developer Kits > * 3.2. Install JBoss Developer Studio > * 3.3. Install JBoss Developer Studio BYOE > * 5.2. Upgrade JBoss Developer Studio > * 5.3. Upgrade JBoss Developer Studio BYOE > * B.1. Build the Universal Installer from Source > *Migration Guide* (2.2 and 2.3 shared with Installation Guide) > * 2.2. Upgrade JBoss Developer Studio > * 2.3. Upgrade JBoss Developer Studio BYOE > * 3.1. Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE > *Getting Started Guide* (3.2 shared with Installation Guide) > * 2.1. About Getting Started > * 3.1. Installation Assumptions > * 3.2. Install JBoss Developer Studio > * 4.3. Tutorial Assumptions > *User Guide* > * None -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15499: --------------------------------------- Since our and some other plugin (MPC) can't both register DND on the main Eclipse shell (Eclipse instance), I propose the following: - check for existence of the MPC plugin which can be done without introducing a dependency on the MPC plugin and a) if it doesn't exist, register our DND on the main Eclipse shell b) if exists, register DND on the JBoss Central editor The second solution would always register our DND on the JBoss Central editor. This would provide that our DND doesn't break MPC's DND. When DND accepts a valid URL, we would do the following: - check if there is a connector(s) a) if there isn't any connector, open a simple information dialog b) if there is one or more connectors, show a wizard similar to the Software/Update page with the following info: - connectors that don't exist - already installed connectors - connectors that aren't installed (they would be checked) The user would be able to install some or all non-installed connectors. Max, WDYT? {quote} in addition - if this could also be used to trigger start of wizards/import of quickstarts would be interesting too. {quote} Could you propose how they would be triggered? {quote} [~snjeza] be my guest to create a PR for this - use similar mechanisms as found in eclipse marketplace but with less bugs {quote} Could you point me to any of them? I would like to try to fix them. > Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15499 > URL: https://issues.jboss.org/browse/JBIDE-15499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.1.1.Beta1 > > > usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds. > Similar to eclipse marketplace for marketplace urls something like: > * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or > * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra... > would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e" > This would allow drag'n'drop install from html docs. > Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2769) Shortcut for Redo action is missing

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2769?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2769: ----------------------------- CDW pm_ack: ? CDW release: ? Target Release: 3.0.2.GA > Shortcut for Redo action is missing > ----------------------------------- > > Key: JBDS-2769 > URL: https://issues.jboss.org/browse/JBDS-2769 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: ui/branding > Affects Versions: 7.0.0.GA, 7.1.0.Alpha1 > Reporter: Andrej Podhradsky > > By default, there is no shortcut for Redo action like in Eclipse (ShiftCtrl+Z). > I think it would be cool if there is a shortcut for redo by default ;-) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2769) Shortcut for Redo action is missing

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBDS-2769: --------------------------------------- Summary: Shortcut for Redo action is missing Key: JBDS-2769 URL: https://issues.jboss.org/browse/JBDS-2769 Project: Developer Studio (JBoss Developer Studio) Issue Type: Enhancement Security Level: Public (Everyone can see) Components: ui/branding Affects Versions: 7.0.0.GA, 7.1.0.Alpha1 Reporter: Andrej Podhradsky By default, there is no shortcut for Redo action like in Eclipse (ShiftCtrl+Z). I think it would be cool if there is a shortcut for redo by default ;-) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2763) REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2763?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2763: ------------------------------------------- [~nickboldt] just add the PR and apply it once QE acks it. btw. it is not all about pixels. This constant wish for using the full name reminds me of this video: http://www.youtube.com/watch?v=EUXnJraKM3k > REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too? > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2763 > URL: https://issues.jboss.org/browse/JBDS-2763 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Attachments: 2763_3_places.png, 2763_cmdline.png, 2763_commandine_new.png, 2763_installer1_new.png > > > Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? > !https://issues.jboss.org/secure/attachment/12364502/12364502_ins-step-5.png! > Should we also rename the jbdevstudio-**.jar files to rhjbdevstudio-**.jar? > What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ? -- 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, 9 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