October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15597) Environmental Variables UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15597: ------------------------------------------ added environment variables to advanced section > Environmental Variables UI > -------------------------- > > Key: JBIDE-15597 > URL: https://issues.jboss.org/browse/JBIDE-15597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Martes Wigglesworth > Priority: Blocker > Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg > > > GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13228) Support CDI 1.1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13228?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-13228: ------------------------------------- I'm using the very latest code pulled from the github repo. I created JBIDE-15641 > Support CDI 1.1 > --------------- > > Key: JBIDE-13228 > URL: https://issues.jboss.org/browse/JBIDE-13228 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.x > > > CDI 1.1 spec - http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html > The full list of changes in CDI 1.1 - https://issues.jboss.org/sr/jira.issueviews:searchrequest-printable/12314... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15641) Unable to change the CDI Facet from 1.0 to 1.1

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-15641: ----------------------------------- Summary: Unable to change the CDI Facet from 1.0 to 1.1 Key: JBIDE-15641 URL: https://issues.jboss.org/browse/JBIDE-15641 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Affects Versions: 4.2.0.Alpha1 Reporter: Fred Bricon Fix For: 4.2.0.Alpha1 - Create a CDI project with Facet 1.0 - Right-click on project > Properties > Project Facets - change the CDI version to 1.1 => "Cannot change version of project facet CDI (...) to 1.1" No indications whatsoever of why you can't change it. Constraints seem ok. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13364) Consider changing the way in which BrowserSim uses WebKit engine

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13364?page=com.atlassian.jira.plugi... ] Yahor Radtsevich commented on JBIDE-13364: ------------------------------------------ JavaFX WebView ships its own WebKit and supports Debugger API. See JBIDE-15640. > Consider changing the way in which BrowserSim uses WebKit engine > ---------------------------------------------------------------- > > Key: JBIDE-13364 > URL: https://issues.jboss.org/browse/JBIDE-13364 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Fix For: 4.2.x > > > A perfect solution for BrowserSim must match the following criteria: > * Be Java-based > * Allow to fully customize the application window [skinning] > * Work on every supported platform (Windows, Mac and Linux) > * Use browser already installed in the system [to avoid library conflicts and reduce the size of our plugins] > * Allow to execute JavaScript and/or modify DOM [to simulate some mobile * JavaScript events and Cordova API] > * Allow to change User-Agent header > * Allow to disable web security or support extensions [for Cordova cross-domain requests] > * Support debugging protocol or support extensions [for better LiveEdit/LiveReload] > * Support debugging protocol or ability to launch Web Inspector/Chrome Developer Tools [for JavaScript debugging capabilities] > Unfortunately, there is no perfect solution, at least I do not know any. > This is the list of the libraries I consider for BrowserSim (+=Pros, -=Cons, ?=questionable): > * Java wrapper for [Chromium Embedded Framework|http://code.google.com/p/javachromiumembedded/] > ** + I was able to run it on Windows > ** - It failed in a half of a minute :) > ** - Not supported since 2010 > ** ? probably will work better with the most recent version of CEF > ** ? looks like there is no Linux support > * [Qt WebKit bindings for SWT|http://code.google.com/p/qtwidgetsinswt/] > ** + I was able successfully run on Windows (32-bit) with Qt 4.8 and MinGW > ** + At least during my smoketesting it did not fail > ** - The plugin page claims that only win32 and cocoa32 are supported > ** - requires Qt (and MSVC or MinGW for Windows) libraries to be bundled with it > ** - Does not have existing API for invoking JavaScript. > ** - Not supported since 2010 > ** ? I do not know how easy it would be to run it on Linux > ** ? I do not know if it will work with Qt 5 > * [AppJS|http://appjs.org/] - a JavaScript SDK for creating Chromium based desktop applications > ** + Supports Windows, Mac and Linux! > ** + Allows to disable web security > ** + Has active community > ** + Did not fail at my smoketest > ** ? need to ensure that applications may be run without borders > * [node-webkit|https://github.com/rogerwang/node-webkit#readme] - the idea is the same as with AppJS - allows to create desktop apps with JavaScript > ** + supported by Intel in some way > ** ? I did not try it yet > * [Google Chrome Frame|http://www.google.com/chromeframe] > ** + the only way to embed _already installed_ Chrome into our application (all other require libraries to be bundled) > ** - Windows only > ** - [no success to use it as Ole object|http://code.google.com/p/chromium/issues/attachmentText?id=25448&a...] > ** ? Probably will work if use it with Browser(SWT.NONE) > * Stay with existing SWT bindings for WebKit > ** + We already use it > ** + Support all platforms > ** + Allow JavaScript to be executed > ** + Do not require to be bundled with our plugins > ** + Allow skinning > ** - Require Safari on Windows [no updates since May 9, 2012] > ** - Web security cannot be disabled > ** - Do not support extensions > ** - Do not support remote debugging protocol > ** - Do not support Web Inspector/Chrome Developer Tools > *To conclude:* > * Firstly, moving to a JavaScript SDK potentially could resolve all our problems, but now I do not think it is worth it. > * Secondly, it would be great if we had good SWT bindings for Chromium, but they do not exist. The only way to get them is to implement them by ourself. > * Thirdly, the last option does not look too bad. And probably it does not worth it to create Chromium bindings or to move to another non-Java language. Especially, if we would be able to create a good workaround for cross-domain requests for Cordova, then almost everything else is ok. > * Fourthly, the biggest issue with existing SWT bindings is that Safari is not supported anymore on Windows. It is an OS specific issue and we could consider a replacement of SWT bindings on Windows only (e.g. use Chrome Frame or Qt on Windows). -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15640) BrowserSim: use JavaFX WebView as a browser engine

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15640?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-15640: ------------------------------------- Component/s: browsersim > BrowserSim: use JavaFX WebView as a browser engine > -------------------------------------------------- > > Key: JBIDE-15640 > URL: https://issues.jboss.org/browse/JBIDE-15640 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Fix For: 4.2.x > > > JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html‎] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser. > *Pros:* > # WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...] > # It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows > # Can be used together with the SWT Browser (i.e. if there is no JavaFX present, we can fallback to the SWT Browser in runtime) > *Cons:* > # Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone) > # window.localStorage is not supported (may be a problem for CordovaSim) > # Character encoding problems on some installations > # Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15640) BrowserSim: use JavaFX WebView as a browser engine

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15640?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-15640: ------------------------------------- Description: JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html‎] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser. *Pros:* # WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...] # It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows # Can be used together with the SWT Browser (i.e. if there is no JavaFX present, we can fallback to the SWT Browser in runtime) *Cons:* # Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone) # window.localStorage is not supported (may be a problem for CordovaSim) # Character encoding problems on some installations # Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs was: JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html‎] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser. *Pros:* # WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...] # It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows *Cons:* # Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone) # window.localStorage is not supported (may be a problem for CordovaSim) # Character encoding problems on some installations # Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs > BrowserSim: use JavaFX WebView as a browser engine > -------------------------------------------------- > > Key: JBIDE-15640 > URL: https://issues.jboss.org/browse/JBIDE-15640 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Fix For: 4.2.x > > > JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html‎] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser. > *Pros:* > # WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...] > # It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows > # Can be used together with the SWT Browser (i.e. if there is no JavaFX present, we can fallback to the SWT Browser in runtime) > *Cons:* > # Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone) > # window.localStorage is not supported (may be a problem for CordovaSim) > # Character encoding problems on some installations > # Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15640) BrowserSim: use JavaFX WebView as a browser engine

by Yahor Radtsevich (JIRA)

Yahor Radtsevich created JBIDE-15640: ---------------------------------------- Summary: BrowserSim: use JavaFX WebView as a browser engine Key: JBIDE-15640 URL: https://issues.jboss.org/browse/JBIDE-15640 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 4.2.x JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html‎] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser. *Pros:* # WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...] # It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows *Cons:* # Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone) # window.localStorage is not supported (may be a problem for CordovaSim) # Character encoding problems on some installations # Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15127) localhost seems hardcoded in livereload

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15127?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15127: ---------------------------------- Fix Version/s: 4.1.1.Beta1 > localhost seems hardcoded in livereload > --------------------------------------- > > Key: JBIDE-15127 > URL: https://issues.jboss.org/browse/JBIDE-15127 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Reporter: Max Rydahl Andersen > Fix For: 4.1.1.Beta1 > > > livereload server has a host field default to 'localhost' > When changing that to i.e. 127.0.0.1 or 192.168.1.55 it seems to ignore it and keep trying to start and serve from localhost instead of this specific ip. > This caused problems on a machine where locahost had issues but direct ip worked fine. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15475) Provide a "Link with Editor" button on the JUnit Test View

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15475?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15475: ---------------------------------- Fix Version/s: 4.2.x > Provide a "Link with Editor" button on the JUnit Test View > ---------------------------------------------------------- > > Key: JBIDE-15475 > URL: https://issues.jboss.org/browse/JBIDE-15475 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.x > > > Submitted a patch for https://bugs.eclipse.org/bugs/show_bug.cgi?id=372588 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-379) Technical Review of 7.0 Guides

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-379?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-379: ------------------------------------- Sprint: (was: Sprint 2) > Technical Review of 7.0 Guides > ------------------------------ > > Key: TOOLSDOC-379 > URL: https://issues.jboss.org/browse/TOOLSDOC-379 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > Original Estimate: 3 days, 6 hours > Remaining Estimate: 3 days, 6 hours > > Conduct a post release technical review of 7.0 docs to catch any previously missed technical or copy errors. -- 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, 6 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 October 2013