May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13890) OpenOn for <div data-role="page">: "Open With BrowserSim" and "Open With Browser"

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13890?page=com.atlassian.jira.plugi... ] Yahor Radtsevich commented on JBIDE-13890: ------------------------------------------ [~dazarov], might we do not add [the build time dependencies|https://github.com/jbosstools/jbosstools-vpe/pull/74/files#L2L9] from browsersim to jst? > OpenOn for <div data-role="page">: "Open With BrowserSim" and "Open With Browser" > --------------------------------------------------------------------------------- > > Key: JBIDE-13890 > URL: https://issues.jboss.org/browse/JBIDE-13890 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > > This feature may be useful for multi-page documents. > 1. Open any jQueryMobile html page with HTML Editor. > 2. Ctrl+Click on <div data-role="page"> > 3. There should be "Open With BrowserSim" and "Open With Browser" options available which opens this page with BrowserSim and Default Browser. > http://www.screenr.com/B697 -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14473) Add jbosstools-arquillian to JBoss Tools site

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14473?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-14473: ---------------------------------------- [~maxandersen]: In which categor(y|ies) should arquillian appear? GeneralTools? > Add jbosstools-arquillian to JBoss Tools site > --------------------------------------------- > > Key: JBIDE-14473 > URL: https://issues.jboss.org/browse/JBIDE-14473 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Beta1 > > > Add the jbosstools-arquillian feature to jbosstools site. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14473) Add jbosstools-arquillian to JBoss Tools site

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-14473: -------------------------------------- Summary: Add jbosstools-arquillian to JBoss Tools site Key: JBIDE-14473 URL: https://issues.jboss.org/browse/JBIDE-14473 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Reporter: Mickael Istria Assignee: Mickael Istria Fix For: 4.1.0.Beta1 Add the jbosstools-arquillian feature to jbosstools site. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14454) setup build for jbosstools-arquillian

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14454?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-14454. ------------------------------------ Resolution: Done > setup build for jbosstools-arquillian > ------------------------------------- > > Key: JBIDE-14454 > URL: https://issues.jboss.org/browse/JBIDE-14454 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.1.0.Beta1 > > > start by using https://github.com/maxandersen/jbosstools-arquillian, we'll move it to jbosstools org shortly after. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14407) Manage different Cordova versions

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14407?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-14407: ------------------------------------ Assignee: Gorkem Ercan A new bundle for hosting the Cordova libraries is introduced. In the future we may add migration logic if we see that it is needed. > Manage different Cordova versions > --------------------------------- > > Key: JBIDE-14407 > URL: https://issues.jboss.org/browse/JBIDE-14407 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: LATER > > > Ability to target different supported cordova versions... Tools at least should offer the ability to migrate to the latest supported Cordova version. > Also all the cordova templates and files should be able to update independent of the rest of the plugins. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14433) Migrate hibernate tools to Kepler M7

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14433?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-14433: ----------------------------------- https://github.com/jbosstools/jbosstools-hibernate/commit/5d3bb06f14cf2d8... and https://github.com/jbosstools/jbosstools-hibernate/commit/0785a188a9dfd48... solve the compilation issues. Both commits have been pushed into master. Now there seems to be a test issue on jenkins though... > Migrate hibernate tools to Kepler M7 > ------------------------------------ > > Key: JBIDE-14433 > URL: https://issues.jboss.org/browse/JBIDE-14433 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.1.0.Beta1 > > > There are 182 errors to fix under Eclipse Kepler M7 in Hibernate JPT integration plug-ins -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14072) Messaging for JPP 6 in JBDS plugin

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14072?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14072: --------------------------------------- The user will be informed about what a quickstart requires. The description would contain a text similar to the text in the summary of this jira. This would work until we find a better solution. > Messaging for JPP 6 in JBDS plugin > ---------------------------------- > > Key: JBIDE-14072 > URL: https://issues.jboss.org/browse/JBIDE-14072 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Portal/GateIn > Affects Versions: 4.0.2.Final, 4.1.0.Beta1 > Environment: All > Reporter: Divya Mehra > Assignee: Snjezana Peco > Priority: Minor > Fix For: 4.1.0.Beta1 > > > Starting from GateIn 3.5/JPP 6.0, Maven quick starts would be the recommended way to bootstrap a portal project. > Older technology, for example JSF 1.2 and Rich Faces 3 portlets, would not work if deployed on GateIn 3.5/JPP 6.0 (or later versions). > It is desirable that we message prominently in the JBDS plugin for portal that the developer should use the quick starts (instead of the plugin) for deployments on GateIn 3.5/JPP 6.0 or later versions. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14289) Open launch configuration for Live Reload servers displays error messages

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14289?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-14289. ----------------------------------- Resolution: Done Fixed in https://github.com/jbosstools/jbosstools-livereload/pull/9 > Open launch configuration for Live Reload servers displays error messages > ------------------------------------------------------------------------- > > Key: JBIDE-14289 > URL: https://issues.jboss.org/browse/JBIDE-14289 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.Alpha2 > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Fix For: 4.1.0.Beta1 > > Attachments: error0.png, error1.png > > > 1. Add LiveReload server to server view > 2. Double click on created server > 3. Click on link Open launch configuration in opened editor > ERROR: > !error0.png! > !error1.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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14333) have context sensitive parameterized commands for open file, show type etc. with proper API

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14333?page=com.atlassian.jira.plugi... ] Snjezana Peco edited comment on JBIDE-14333 at 5/16/13 11:29 AM: ----------------------------------------------------------------- {quote} variable substitution from where ? Eclipse global variables ? should be possible to register a "cheatsheet.project" variable here would it not ? But for now \{project\} is probably fine. {quote} Cheatsheet variables are set within a cheatsheet. I think, we can't set this variable since we don't know the project name when creating a cheatsheet. {quote} What does "profile" refer to for launchJunitTest ? junit doesn't sound like something to know about maven nor arquillian... {quote} The profile parameter is optional. The command will work without m2e or arquillian. I needed that feature for the kitchensink sheatsheet. {quote} Can you point me to do api/docs for what you are making here ? {quote} There are three simple commands: OpenFileInEditorHandler, RunOnServerHandler and LaunchJUnitTestHandler {quote} btw. the old actions will still work, right? these are additional commands, correct? {quote} Correct. {quote} So I grok you added commands that could be invoked from cheatsheets, the JUnit test shows how you programatically invoke those commands, do you have a real cheatsheet example that would demonstrate the use for the new commands? {quote} No, but you can replace the actions in the existing cheatsheet (kitchensink, for instance) with the commands described in the previous message. was (Author: snjeza): {quote} variable substitution from where ? Eclipse global variables ? should be possible to register a "cheatsheet.project" variable here would it not ? But for now \{project\} is probably fine. {quote} Cheatsheet variables are set within a cheatsheet. I think, we can't set this varijable since we don't know the project name when creating a cheatcheet. {quote} What does "profile" refer to for launchJunitTest ? junit doesn't sound like something to know about maven nor arquillian... {quote} The profile parameter is optional. The command will work without m2e or arquillian. I needed that feature for the kitchensink sheatsheet. {quote} Can you point me to do api/docs for what you are making here ? {quote} There are three simple commands: OpenFileInEditorHandler, RunOnServerHandler and LaunchJUnitTestHandler {quote} btw. the old actions will still work, right? these are additional commands, correct? {quote} Correct. {quote} So I grok you added commands that could be invoked from cheatsheets, the JUnit test shows how you programatically invoke those commands, do you have a real cheatsheet example that would demonstrate the use for the new commands? {quote} No, but you can replace the actions in the existing cheatsheet (kitchensink, for instance) with the commands described in the previous message. > have context sensitive parameterized commands for open file, show type etc. with proper API > ------------------------------------------------------------------------------------------- > > Key: JBIDE-14333 > URL: https://issues.jboss.org/browse/JBIDE-14333 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Reporter: Max Rydahl Andersen > Fix For: 4.1.0.Beta1, 4.1.0.Beta2 > > > currently our custom cheatsheet commands requires the project name(s) to be known upfront. We should make them less reliant on project names and if at all possible have the project name calculated based on the project the cheatsheet file is open in. > The commands should also actually be commands with named parameters so the order of parameters does not matter and we should make sure these have a good and long term API so cheatsheets will continue to work well in the future. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14333) have context sensitive parameterized commands for open file, show type etc. with proper API

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14333?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14333: --------------------------------------- {quote} variable substitution from where ? Eclipse global variables ? should be possible to register a "cheatsheet.project" variable here would it not ? But for now \{project\} is probably fine. {quote} Cheatsheet variables are set within a cheatsheet. I think, we can't set this varijable since we don't know the project name when creating a cheatcheet. {quote} What does "profile" refer to for launchJunitTest ? junit doesn't sound like something to know about maven nor arquillian... {quote} The profile parameter is optional. The command will work without m2e or arquillian. I needed that feature for the kitchensink sheatsheet. {quote} Can you point me to do api/docs for what you are making here ? {quote} There are three simple commands: OpenFileInEditorHandler, RunOnServerHandler and LaunchJUnitTestHandler {quote} btw. the old actions will still work, right? these are additional commands, correct? {quote} Correct. {quote} So I grok you added commands that could be invoked from cheatsheets, the JUnit test shows how you programatically invoke those commands, do you have a real cheatsheet example that would demonstrate the use for the new commands? {quote} No, but you can replace the actions in the existing cheatsheet (kitchensink, for instance) with the commands described in the previous message. > have context sensitive parameterized commands for open file, show type etc. with proper API > ------------------------------------------------------------------------------------------- > > Key: JBIDE-14333 > URL: https://issues.jboss.org/browse/JBIDE-14333 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Reporter: Max Rydahl Andersen > Fix For: 4.1.0.Beta1, 4.1.0.Beta2 > > > currently our custom cheatsheet commands requires the project name(s) to be known upfront. We should make them less reliant on project names and if at all possible have the project name calculated based on the project the cheatsheet file is open in. > The commands should also actually be commands with named parameters so the order of parameters does not matter and we should make sure these have a good and long term API so cheatsheets will continue to work well in the future. -- 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

13 years, 1 month

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 May 2013