[jbosstools-issues] [JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

[Alexey Kazakov (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025313#comment-13025313 ] 

Alexey Kazakov commented on JBIDE-18177:
----------------------------------------

I added a few comments in github - https://github.com/jbosstools/jbosstools-vpe/pull/295
But I think we are not ready to push this PR to 4.2.1. We have one day for development and a week for testing before 4.2.1.Final.
What I'm suggesting:
1. Finish review of the PR ([~maxandersen], [~dgolovin], [~fbricon], any input?), fix all found issues/questions)
2. Merge it to master
3. Ask [~vpakan] to test it in the next nightly build (Vlado, please speak up if you have any problems with this)
4. If everything is OK then push it to 4.2.2 stream.

So, I'm moving the issue to 4.2.2.Final.
[~maxandersen], guys, WDYT?

> 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, respin-a
>             Fix For: 4.2.2.Final, 4.3.0.Alpha1
>
>
> 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.8#6338)