[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Len DiMaggio updated JBIDE-18177:
---------------------------------
Labels: f2f2014 new_and_noteworthy requirements (was: f2f2014 new_and_noteworthy)
> Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18177
> URL: https://issues.jboss.org/browse/JBIDE-18177
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Labels: f2f2014, new_and_noteworthy, requirements
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, restart.jpg
>
>
> Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner)
> if he says okey - we set a flag somewhere to not start xulrunner.
> user restart - user is happy.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19145) BrowserSim: debugging with dev tools stops working
by Konstantin Marmalyukov (JIRA)
Konstantin Marmalyukov created JBIDE-19145:
----------------------------------------------
Summary: BrowserSim: debugging with dev tools stops working
Key: JBIDE-19145
URL: https://issues.jboss.org/browse/JBIDE-19145
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: browsersim, cordovasim
Affects Versions: 4.3.0.Alpha1
Reporter: Konstantin Marmalyukov
Assignee: Konstantin Marmalyukov
Fix For: 4.3.0.Alpha1
Debugging with dev tools stops working because we have jetty 8 and 9 bundles in target platform, and jetty 9 bundles is used.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18900) CordovaSim: Can't run default FeedHenry app locally
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18900?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-18900:
--------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-aerogear/pull/102, https://github.com/jbosstools/jbosstools-aerogear/pull/106 (was: https://github.com/jbosstools/jbosstools-aerogear/pull/102)
> CordovaSim: Can't run default FeedHenry app locally
> ---------------------------------------------------
>
> Key: JBIDE-18900
> URL: https://issues.jboss.org/browse/JBIDE-18900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Affects Versions: 4.2.1.Final
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Fix For: 4.3.0.Alpha1
>
> Attachments: configuration.png, cordovasimFH.png, FHshortcuts.png, hello_tom.png, newLaunch.png, preferences.png, ToolsProject-Cloud-App.zip, ToolsProject-Cordova-App.zip
>
>
> Basically, the situation is the following:
> 1. *ToolsProject-Cordova-App.zip* - is a basic FH hybrid app (all the app does is saying Hello + 'username' from the input field )
> 2. To run this app one simply needs to unpack the archive and import it as a cordova project to the studio
> 3. The application will work with a *remote* server like a charm !hello_tom.png|thumbnail!
> 4. However, there is an option to use *local* server instead of *remote* one
> 5. *ToolsProject-Cloud-App.zip* - is a app for running local server via grunt task runner
> 6. In order to run local server one needs:
> - unpack the app
> - run *npm install .*
> - run *grunt serve*
> Need to find the way to made CordovaSim use this *local* server
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19049) Enable JBoss servers to run with java 9
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19049?page=com.atlassian.jira.plugi... ]
Len DiMaggio updated JBIDE-19049:
---------------------------------
Labels: Java9 (was: )
> Enable JBoss servers to run with java 9
> ---------------------------------------
>
> Key: JBIDE-19049
> URL: https://issues.jboss.org/browse/JBIDE-19049
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.2.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: Java9
> Fix For: 4.3.0.Alpha1
>
>
> I briefly tried to use java 9 for our tooling and to run servers.
> I downloaded it from here:
> https://jdk9.java.net/download/
> {code}
> nattura:8.0.2 rasp$ java -version
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b45)
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode)
> {code}
> I use OS X 10.10 Yosemite.
> There are a couple of problems:
> 1. When I add a WildFly 8.2 server into JBDS 8.0.2, I cannot change the runtime to use java 9 - it seems we restrict that.
> 2. Even if I could, we need to make sure -XX:MaxPermSize is not used in the server launch command. When I tried to run WildFly 8.2 from the terminal, it wouldn't work unless I removed the max perm size argument. Apparently java 9 does not just ignore this parameter (as java 8 did), but it does not allow it at all.
> {code}
> nattura:bin rasp$ ./standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final
> JAVA: /Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> Unrecognized VM option 'MaxPermSize=256m'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> Of course it's questionable if we should allow java 9 for current servers at all as they don't support it officially. But I would say there is no need to restrict it if it works.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months