November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15973) Handle info tag on plugin.xml

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15973?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-15973: -------------------------------------- Decided to go with the tabbed properties for displaying info. The new properties view should also handle the new metadata that has been added to plugins with https://issues.apache.org/jira/browse/CB-5128 > Handle info tag on plugin.xml > ----------------------------- > > Key: JBIDE-15973 > URL: https://issues.jboss.org/browse/JBIDE-15973 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.2.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The information should be presented after Cordova plugin installation is completed. Should be able to handle several info tags that can be present on a single installation via wizard. -- 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-15973) Handle info tag on plugin.xml

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15973?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-15973: --------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.2.x) > Handle info tag on plugin.xml > ----------------------------- > > Key: JBIDE-15973 > URL: https://issues.jboss.org/browse/JBIDE-15973 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.2.0.Alpha1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The information should be presented after Cordova plugin installation is completed. Should be able to handle several info tags that can be present on a single installation via wizard. -- 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-16020) jboss-kitchensink-backbone does not work due to missing deps

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16020?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-16020: ------------------------------------ Affects: Documentation (Ref Guide, User Guide, etc.) > jboss-kitchensink-backbone does not work due to missing deps > ------------------------------------------------------------ > > Key: JBIDE-16020 > URL: https://issues.jboss.org/browse/JBIDE-16020 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.1.CR1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.1.1.Final > > > backbone example requires org.jboss.bom.wfk.jboss-javaee-6.0-with-tools.2.4.0-redhat-2 but it cannot be found. It is missing in online enterprise repository. -- 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-16028) Update Forge Embedded Runtime to 1.4.3.Final

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16028?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-16028: ------------------------------------ Affects: Documentation (Ref Guide, User Guide, etc.) > Update Forge Embedded Runtime to 1.4.3.Final > -------------------------------------------- > > Key: JBIDE-16028 > URL: https://issues.jboss.org/browse/JBIDE-16028 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.1.1.CR1 > Reporter: Pavol Srna > Assignee: Koen Aers > Labels: respin-a > Fix For: 4.1.1.CR1 > > -- 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-15973) Handle info tag on plugin.xml

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15973?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-15973: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Assignee: Gorkem Ercan > Handle info tag on plugin.xml > ----------------------------- > > Key: JBIDE-15973 > URL: https://issues.jboss.org/browse/JBIDE-15973 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.2.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The information should be presented after Cordova plugin installation is completed. Should be able to handle several info tags that can be present on a single installation via wizard. -- 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-16042) Server Editor: "Open launch configuration" errors

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16042?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-16042: ------------------------------------ Affects: Documentation (Ref Guide, User Guide, etc.) > Server Editor: "Open launch configuration" errors > ------------------------------------------------- > > Key: JBIDE-16042 > URL: https://issues.jboss.org/browse/JBIDE-16042 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: open-launch-config-error.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] (TOOLSDOC-414) Update screen captures in docs that explicitly reference JBDS 7.0

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-414?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-414. -------------------------------------- Resolution: Done > Update screen captures in docs that explicitly reference JBDS 7.0 > ----------------------------------------------------------------- > > Key: TOOLSDOC-414 > URL: https://issues.jboss.org/browse/TOOLSDOC-414 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Getting Started Guide, Installation Guide, Migration Guide, User Guide > Affects Versions: 4.1.1 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > Original Estimate: 4 hours > Time Spent: 3 hours, 25 minutes > Remaining Estimate: 0 minutes > > Screen captures that will need updating for 7.1 docs > *Installation Guide* > * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal *[removed as refs specific JBDS version; update post GA]* > * Figure 3.2. Installation Step 3: Select Target Folder *[done]* > * Figure 3.3. Installation Step 4: Select Java VM *[done]* > * Figure 3.5. Installation Step 7: Installation Progress in Finished State *[done]* > * Figure 3.6. Install JBoss Developer Studio BYOE via Eclipse Marketplace *[done]* > * Figure 3.7. Confirm Selected Features Window *[no change anticipated; review post GA]* > * Figure 3.10. Work from an Online Website *[no change anticipated; review post GA]* > * Figure 3.11. work from a Local Copy of the Update .zip File *[done]* > * Figure 3.12. Available Software Window Listing JBoss Developer Studio 7.0 - Bring Your Own Eclipse *[done]* > * Figure 6.2. Uninstall JBoss Developer Studio via Eclipse Marketplace *[done]* > * Figure 6.3. Confirm Selected Features Window *[no change anticipated; review post GA]* > *Migration Guide* > * Figure 3.1. jbdevstudio.ini File Open in a Text Editor *[little change anticipated; review post GA]* > *Getting Started Guide* (all Fig. shared with Installation Guide) > * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal *[removed as refs specific JBDS version; update post GA]* > * Figure 3.2. Installation Step 3: Select Target Folder *[done]* > * Figure 3.3. Installation Step 4: Select Java VM *[done]* > * Figure 3.5. Installation Step 7: Installation Progress in Finished State *[done]* > *User Guide* > * Figure 2.4. JBoss Buzz *[done; update again post GA]* > * Figure 2.22. Set Cheat Sheet Behavior in Project Examples Pane of Preferences Window *[done]* -- 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-15742) Make Content Assistant Additional Info window to support URLs.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15742?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15742: ----------------------------------- Description: There are two kinds of links which we should support: 1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser: !html.png|thumbnail! *Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message. 2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window): !javadoc.png|thumbnail! *Steps to test:* 1. Make sure JDK sources are available in Eclipse 2. Create a JSF 2 KickStart project. 3. Open greeting.xhtml 4. Type #{user.name.l and press Ctrl+Space 5. Select length 6. There should be a description dialog with javalement links to length() and CharSequence: !javadoc.png|thumbnail! was: Need to make Content Assistant Additional Info to support URL links to: - Web-sites' pages (need to open such pages) - JavaElement's (need to browse to the Add.Info of according Java Element as it works in Java Content Assistant) > Make Content Assistant Additional Info window to support URLs. > -------------------------------------------------------------- > > Key: JBIDE-15742 > URL: https://issues.jboss.org/browse/JBIDE-15742 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Final > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Priority: Minor > Fix For: 4.2.x > > Attachments: html.png, javadoc.png > > > There are two kinds of links which we should support: > 1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser: > !html.png|thumbnail! > *Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message. > 2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window): > !javadoc.png|thumbnail! > *Steps to test:* > 1. Make sure JDK sources are available in Eclipse > 2. Create a JSF 2 KickStart project. > 3. Open greeting.xhtml > 4. Type #{user.name.l and press Ctrl+Space > 5. Select length > 6. There should be a description dialog with javalement links to length() and CharSequence: > !javadoc.png|thumbnail! -- 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] (TOOLSDOC-427) Generate Release Notes doc for JBDS 7.1.0.GA

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-427?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-427: ------------------------------------- Sprint: Sprint 7 w4 (CR1 build out) (was: Sprint 8 w3 ()) > Generate Release Notes doc for JBDS 7.1.0.GA > -------------------------------------------- > > Key: TOOLSDOC-427 > URL: https://issues.jboss.org/browse/TOOLSDOC-427 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Release Notes > Affects Versions: 4.1.1 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > > Holder JIRA for all of the elements that RNs for GA need to document. > *CR1 N&N* > * Show a warning when enterprise maven repo is missing for enterprise quickstarts (JBIDE-15860) > * Update Forge Embedded Runtime to 1.4.2.Final (JBIDE-15859) > * Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install (JBIDE-15449) > * Update to VJET 0.10.0.201309201624 in Central (for 4.1.1.CR1) (JBIDE-15677, JBDS-2710) > * Support EAP 6.2 (JBDS-2784) > * Central TP zip (TOOLSDOC-426) -- 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] (TOOLSDOC-378) Documentation on adding EAP to JBDS 7 is not as effective as documentation for JBDS 6

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-378?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-378: ------------------------------------- Sprint: Sprint 7 w4 (CR1 build out) (was: Sprint 8 w3 ()) > Documentation on adding EAP to JBDS 7 is not as effective as documentation for JBDS 6 > ------------------------------------------------------------------------------------- > > Key: TOOLSDOC-378 > URL: https://issues.jboss.org/browse/TOOLSDOC-378 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Getting Started Guide, Installation Guide > Affects Versions: 4.1.0 > Reporter: Nick Boldt > Assignee: Michelle Murray > > For JBDS 6 we had this, complete with screenshots and example content: > https://access.redhat.com/site/documentation/en-US/JBoss_Developer_Studio... > Now, we have this: > {code:title=https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Developer_Studio/7.0/html-single/Getting_Started_Guide/index.html#Set_Up_a_Runtime_Server_Using_Server_Manager} > 5.2. Set Up a Server Using Runtime Detection > Servers can be set up from within the Java EE Web Project wizard. But for the purposes of exploring JBoss Developer Studio the procedure below sets up the server first. > Procedure 5.2. Set Up a Server Using Runtime Detection > Click Window→Preferences, expand JBoss Tools and select JBoss Tools Runtime Detection. > Click Add. > Select the directory containing the JBoss Enterprise Application Platform 6.0 or JBoss Enterprise Application Platform 6.1 installation and click OK. The directory is now scanned for application servers and JBoss Enterprise Application Platform 6.x found. > To create a server for JBoss Enterprise Application Platform 6.x, ensure the jboss-eap-6.x check box is selected and click OK. > Click Apply and click OK to close the Preferences window. The server is listed in the Servers tab. > The server is initially shown in stopped mode. To start the server, right-click jboss-eap-6.x and click Start. After a short pause, the view switches to the Console tab and shows the startup output of the server. > {code} > AND we have this, which is more verbose but fails to mention any EAP 6.x specific examples. > https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... > Additionally, the html anchor "Set_Up_a_Runtime_Server_Using_Server_Manager" for "5.2 Set Up a Server Using Runtime Detection" doesn't match the content. > https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... > ----- > Could the content in both places be updated/merged to equally complete, and could screenshots be added too? -- 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