January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2564) JBDS70_1214: [Commit] (?) (P?) Fix support for multi-module maven projects

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2564?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2564: ---------------------------------- Target Release: 8.0.0.GA > JBDS70_1214: [Commit] (?) (P?) Fix support for multi-module maven projects > -------------------------------------------------------------------------- > > Key: JBDS-2564 > URL: https://issues.jboss.org/browse/JBDS-2564 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Jiri Pallich > Assignee: Andre Dietisheim > Fix For: 8.0.0.GA > > > Could be better at detecting proper packaging type for the openshift profile. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1108) Can we host screencasts on redhat.com/docs?

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-1108?page=com.atlassian.jira.plugin.... ] Michelle Murray resolved JBDS-1108. ----------------------------------- Resolution: Out of Date If issue still relevant then please reopen or re-report it. > Can we host screencasts on redhat.com/docs? > ------------------------------------------- > > Key: JBDS-1108 > URL: https://issues.jboss.org/browse/JBDS-1108 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: requirements > Affects Versions: 4.0.0.GA > Reporter: Rodney Russ > Assignee: Isaac Rooskov > Fix For: LATER > > > Isaac mentions the following in JBDS-1092: > In future releases I would like to look for a way to host the screencasts on redhat.com/docs so it's part of the enterprise instead of linking enterprise customers to a community site. > This Jira is just to capture the task to see if his request is possible (and not lose it :) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1108) Can we host screencasts on redhat.com/docs?

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-1108?page=com.atlassian.jira.plugin.... ] Michelle Murray closed JBDS-1108. --------------------------------- > Can we host screencasts on redhat.com/docs? > ------------------------------------------- > > Key: JBDS-1108 > URL: https://issues.jboss.org/browse/JBDS-1108 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: requirements > Affects Versions: 4.0.0.GA > Reporter: Rodney Russ > Assignee: Isaac Rooskov > Fix For: LATER > > > Isaac mentions the following in JBDS-1092: > In future releases I would like to look for a way to host the screencasts on redhat.com/docs so it's part of the enterprise instead of linking enterprise customers to a community site. > This Jira is just to capture the task to see if his request is possible (and not lose it :) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugi... ] Michelle Murray commented on JBIDE-16355: ----------------------------------------- Not too sure how the current list is produced. Is it with queries? If so then the queries seem a bit off. For example, JBIDE-15121 was listed under the enhancements section which to me would indicate that it was done. But on opening the jira I found that it was closed as out of date. So perhaps we need to consider more carefully the queries being used/provided to users via sourceforge. I'm including a link to the queries provided in JBDS 7.1.0 Release Notes for users in case these queries are of any assistance in this discussion [1]. [1] https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... > replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query > -------------------------------------------------------------------------------------- > > Key: JBIDE-16355 > URL: https://issues.jboss.org/browse/JBIDE-16355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > > Re: files like: > http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/... > {quote} > (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees > (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;) > (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these. > (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean. > (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;) > (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this. > {quote} > Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query. > That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final). > We can also produce a query for both JBT and JBDS. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16345) General Palette improvements

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16345?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-16345: ---------------------------------- Description: Improve Palette in order not to allow insert elements from Palette to the wrong places. 1. Insert elements from Palette to the Editor by setting text cursor or selecting text in the Editor then pressing on Palette Item ||Before Insertion||After Insertion|| |!PaletteBefore1.png!|!PaletteAfter1.png!| |!PaletteBefore2.png!|!PaletteAfter2.png!| |!PaletteBefore3.png!|!PaletteAfter3.png!| |!PaletteBefore4.png!|!PaletteAfter4.png!| |!PaletteBefore5.png!|!PaletteAfter5.png!| 2. Insert elements from Palette to the Editor by dragging elements from Palette and dropping them to the Editor !PaletteDragAndDrop1.png! !PaletteDragAndDrop2.png! was: Improve Palette in order not to allow insert elements from Palette to the wrong places. 1. Insert elements from Palette to the Editor by setting text cursor or selecting text in the Editor then pressing on Palette Item ||Before Insertion||After Insertion|| |!PaletteBefore1.png!|!PaletteAfter1.png!| |!PaletteBefore2.png!|!PaletteAfter2.png!| |!PaletteBefore3.png!|!PaletteAfter3.png!| |!PaletteBefore4.png!|!PaletteAfter4.png!| |!PaletteBefore5.png!|!PaletteAfter5.png!| > General Palette improvements > ---------------------------- > > Key: JBIDE-16345 > URL: https://issues.jboss.org/browse/JBIDE-16345 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Fix For: 4.2.0.Alpha2 > > Attachments: PaletteAfter1.png, PaletteAfter2.png, PaletteAfter3.png, PaletteAfter4.png, PaletteAfter5.png, PaletteBefore1.png, PaletteBefore2.png, PaletteBefore3.png, PaletteBefore4.png, PaletteBefore5.png, PaletteDragAndDrop1.png, PaletteDragAndDrop2.png > > > Improve Palette in order not to allow insert elements from Palette to the wrong places. > 1. Insert elements from Palette to the Editor by setting text cursor or selecting text in the Editor then pressing on Palette Item > ||Before Insertion||After Insertion|| > |!PaletteBefore1.png!|!PaletteAfter1.png!| > |!PaletteBefore2.png!|!PaletteAfter2.png!| > |!PaletteBefore3.png!|!PaletteAfter3.png!| > |!PaletteBefore4.png!|!PaletteAfter4.png!| > |!PaletteBefore5.png!|!PaletteAfter5.png!| > 2. Insert elements from Palette to the Editor by dragging elements from Palette and dropping them to the Editor > !PaletteDragAndDrop1.png! > !PaletteDragAndDrop2.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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16345) General Palette improvements

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16345?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-16345: ---------------------------------- Attachment: PaletteDragAndDrop2.png PaletteDragAndDrop1.png > General Palette improvements > ---------------------------- > > Key: JBIDE-16345 > URL: https://issues.jboss.org/browse/JBIDE-16345 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Fix For: 4.2.0.Alpha2 > > Attachments: PaletteAfter1.png, PaletteAfter2.png, PaletteAfter3.png, PaletteAfter4.png, PaletteAfter5.png, PaletteBefore1.png, PaletteBefore2.png, PaletteBefore3.png, PaletteBefore4.png, PaletteBefore5.png, PaletteDragAndDrop1.png, PaletteDragAndDrop2.png > > > Improve Palette in order not to allow insert elements from Palette to the wrong places. > 1. Insert elements from Palette to the Editor by setting text cursor or selecting text in the Editor then pressing on Palette Item > ||Before Insertion||After Insertion|| > |!PaletteBefore1.png!|!PaletteAfter1.png!| > |!PaletteBefore2.png!|!PaletteAfter2.png!| > |!PaletteBefore3.png!|!PaletteAfter3.png!| > |!PaletteBefore4.png!|!PaletteAfter4.png!| > |!PaletteBefore5.png!|!PaletteAfter5.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, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-446) document how to debug on openshift JEE applications

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-446?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-446: ------------------------------------- Fix Version/s: 4.1.2 > document how to debug on openshift JEE applications > --------------------------------------------------- > > Key: TOOLSDOC-446 > URL: https://issues.jboss.org/browse/TOOLSDOC-446 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Reporter: Max Rydahl Andersen > Assignee: Michelle Murray > Fix For: 4.1.2, 4.2.0 > > > would be great if Docs at https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... > could outline how to enable/disable debugging and how to use port forwarding to connect to the debugger. > References: > https://community.jboss.org/en/tools/blog/2012/02/08/debugging-and-browsi... > http://vimeo.com/44548968 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-446) document how to debug on openshift JEE applications

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-446?page=com.atlassian.jira.plug... ] Max Rydahl Andersen commented on TOOLSDOC-446: ---------------------------------------------- [~mmurray] no particular reason for version of the link - it was what [~burrsutter] gave me when asking where docs were for debugging which resulted in this bug being opened. > document how to debug on openshift JEE applications > --------------------------------------------------- > > Key: TOOLSDOC-446 > URL: https://issues.jboss.org/browse/TOOLSDOC-446 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Reporter: Max Rydahl Andersen > Assignee: Michelle Murray > Fix For: 4.2.0 > > > would be great if Docs at https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... > could outline how to enable/disable debugging and how to use port forwarding to connect to the debugger. > References: > https://community.jboss.org/en/tools/blog/2012/02/08/debugging-and-browsi... > http://vimeo.com/44548968 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16356) To Commit or not to Commit

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16356?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-16356: ------------------------------------- a screenshot of what my directory structure looks like after the git clone, before the import http://screencast.com/t/2Dk4yQ1q > To Commit or not to Commit > -------------------------- > > Key: JBIDE-16356 > URL: https://issues.jboss.org/browse/JBIDE-16356 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Burr Sutter > Attachments: contacts-mobile-basic.zip > > > I am getting an odd error message. > Here are the steps: > 1) git clone https://github.com/joshuawilson/jboss-wfk-quickstarts.git > 2) git checkout WFK-113 > 3) JBDS 7.1 import as Maven project > 4) tweak the pom.xml (it was broken but now fixed) > 5) it deploys to a local EAP, now attempt to send to OpenShift > 6) run the OpenShift wizard as seen in the video > http://screencast.com/t/NVTPK4pL -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2866) CordovaSim Debugger

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2866: ----------------------------- CDW devel_ack: ? CDW qa_ack: ? > CordovaSim Debugger > ------------------- > > Key: JBDS-2866 > URL: https://issues.jboss.org/browse/JBDS-2866 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: browsersim, requirements > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Attachments: DevToolsMenu.png > > > The current FireBug Lite in CordovaSim has the following limitations: > 1) When using LiveReload, the window closes with every reload > 2) Various "page load" events with console.log statements are not visible in FireBug Lite console, like having console.log() in your deviceready > http://screencast.com/t/RRGhV9PV > Note: I forgot to add the Console Cordova plugin, not sure if that is necessary but the window closes, so not sure how I would see the message -- 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, 2 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 January 2014