[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-18177:
-------------------------------------
Open in Default Browser works fine either HTML Preview is rendering web page properly
> 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.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png
>
>
> 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, 4 months
[JBoss JIRA] (JBIDE-19239) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [BrowserSim]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19239?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-19239.
------------------------------
Resolution: Done
Done but JIRA left open.
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [BrowserSim]
> ---------------------------------------------------------
>
> Key: JBIDE-19239
> URL: https://issues.jboss.org/browse/JBIDE-19239
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: browsersim
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [BrowserSim]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha1x
> git push origin jbosstools-4.3.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for BrowserSim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-18177:
------------------------------------------------
{quote}HTML5 page not rendered - visual part of VPE should contain similar message as in case HTML5 support is enabled for XHTML page informing users about possibility to enable HTML5 suppport.{quote}
in this case please try to open html5 page in default browser(using button on action bar). If url is localgost:port/blablabla - maybe there is smth with page. Before this fix html5 page was displayed somehow.
> 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.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png
>
>
> 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, 4 months
[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-18177:
-------------------------------------
When support is changed page is opened and then Eclipse is restarted it would look better if page won't be opened before Eclipse is restarted. Page should be opened after restart.
> 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.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png
>
>
> 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, 4 months
[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-18177:
-------------------------------------
VPE Preference page should contain also third Radio Box with choice: "Always ask" otherwise user will never be able to get dialog asking to choose between JSF and HTML5 support once he will check check box "Do not show this message again".
> 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.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png
>
>
> 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, 4 months
[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-18177:
-------------------------------------
Tested with build Alpha2-v20150212-0919-B9496 on Fedora 20 gnome 64bit:
* GKT2 - xulrunner loaded - JSF support is default value for first use - choice for JSF/HTML5 support is available within VPE Preference page
** JSF support enabled
*** HTML5 page not rendered - {color:red}*visual part of VPE should contain similar message as in case HTML5 support is enabled for XHTML page informing users about possibility to enable HTML5 suppport*{color}. Dialog displayed to choose between JSF/HTML5 support
*** XHTML page properly rendered. No dialog displayed to choose between JSF/HTML5 support
** HTML5 support enabled
*** HTML5 page rendered. No dialog displayed to choose between JSF/HTML5 support
*** XHTML page is not rendered - visual part of VPE contains message informing users about possibility to enable JSF support. Dialog displayed to choose between JSF/HTML5 support * GKT2 - xulrunner not loaded
** no dialog displayed to choose between JSF/HTML5 support
** HTML5 page rendered properly
** XHTML page is not rendered and visual part of VPE contains information about disabled xulrunner via org.jboss.tools.vpe.loadxulrunner property
** no choice for JSF/HTML5 support within VPE Preference page
* GKT3 - xulrunner not loaded or loaded
** no dialog displayed to choose between JSF/HTML5 support
** HTML5 page rendered properly
** XHTML page is not rendered and visual part of VPE contains information about xulrunner not available on with GTK3
** no choice for JSF/HTML5 support within VPE Preference page
> 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.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png
>
>
> 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, 4 months
[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBDS-3345:
-----------------------------------------
I installed JBDS with jdk 1.8.0_25 and the runtime set with jdk 1.7.0_71 (both are oracle jdk)
> Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
> -----------------------------------------------------------------
>
> Key: JBDS-3345
> URL: https://issues.jboss.org/browse/JBDS-3345
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: runtime
> Affects Versions: 8.0.2.GA
> Environment: Fedora 21 x86_64
> JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71
> Reporter: Andrej Podhradsky
> Priority: Critical
> Attachments: errors.txt
>
>
> FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file.
> Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually.
> Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19238) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Forge]
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19238?page=com.atlassian.jira.plugi... ]
Koen Aers closed JBIDE-19238.
-----------------------------
Assignee: Koen Aers
Resolution: Done
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Forge]
> ----------------------------------------------------
>
> Key: JBIDE-19238
> URL: https://issues.jboss.org/browse/JBIDE-19238
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: forge
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [Forge]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha1x
> git push origin jbosstools-4.3.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19233) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Hibernate]
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19233?page=com.atlassian.jira.plugi... ]
Koen Aers closed JBIDE-19233.
-----------------------------
Assignee: Koen Aers
Resolution: Done
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Hibernate]
> --------------------------------------------------------
>
> Key: JBIDE-19233
> URL: https://issues.jboss.org/browse/JBIDE-19233
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: hibernate
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [Hibernate]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha1x
> git push origin jbosstools-4.3.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months