[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 updated JBDS-3345:
------------------------------------
Steps to Reproduce:
0. Install FSW 6.0.0.GA (with or without patch) with JDK 7
1. Install JBDS 8 with JDK 8
2. Window > Preferences > Java > Installed JREs
3. Add standard VM with JDK 7
4. Create new server with Create the appropriate runtime for FSW in JBDS and set runtime jre to JDK 7
5. Start the server
was:
1. Install JBDS 8 with JDK 8
2. Add another JDK, say 7
3. Install FSW 6.0.0.GA (with or without patch) with JDK 7
4. Create the appropriate runtime for FSW in JBDS and set runtime jre to JDK 7
5. Start the server
> 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] (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 don't have any project, I'm just trying to run empty FSW server. The problem is that JBDS doesn't run the FSW server correctly with other jdk.
Why I'm doing this? I'm testing backward compatibility. For example, in the future there will JBDS which can be installed only with JDK 8 or higher.
How will we support servers such as FSW which can be run only with JDK 7? We should be able to run the server from JBDS with any JDK which was added to JBDS.
So, the problem is:
I installed JBDS 8 with JDK 8, how can I run the FSW server correctly? (FSW server can be run only with JDK 6 or 7)
> 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-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:
-------------------------------------
JBIDE-19259 created
> 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-19259) JSF or HTML5 support choosing issues
by Vlado Pakan (JIRA)
Vlado Pakan created JBIDE-19259:
-----------------------------------
Summary: JSF or HTML5 support choosing issues
Key: JBIDE-19259
URL: https://issues.jboss.org/browse/JBIDE-19259
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: visual-page-editor-core, xulrunner
Affects Versions: 4.3.0.Alpha1
Environment: Fedora 20 GNOME 64 bit, Open JDK 7, Alpha2-v20150212-0919-B9496
Reporter: Vlado Pakan
# GKT2 + xulrunner loaded + JSF support enabled: 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
# VPE Preference page should contain checkbox 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"
# 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
# With GTK3 "Visual Editor Browser Engine" group within VPE prefrences page is hidden it would be more user friendly just disable it and add some label why it's disabled?.The same way as selecting of GTK for BrowserSim/CordovaSim works.
# Confusing scenario #1:
## Set HTML5 support
## Open .xhtml page and say "Stay with HTML5"
## Open .html page
## Restart Eclipse
## Close .html page
## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed. It's confusing to ask this when page is closed.
# Confusing scenario #2:
## Set HTML5 support
## Open .xhtml page and say "Stay with HTML5"
## Restart Eclipse
## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed before workspace window appears. This dialog should be displayed once worspace is visible and user actually can see page he is going to open.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18961) Simplify the release process wrt link to blog announcement in products.yml
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18961?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-18961:
----------------------------------
Fix Version/s: 4.3.x
> Simplify the release process wrt link to blog announcement in products.yml
> --------------------------------------------------------------------------
>
> Key: JBIDE-18961
> URL: https://issues.jboss.org/browse/JBIDE-18961
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: website
> Affects Versions: 4.2.1.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.x
>
>
> We could change the way the blog announcement is link to the release by adding specific attributes in the blog file, which avoid having to link to it from the products.yml file, which happens to be a bit tricky in term of flow, because the blog author should not really care about the products.yml, which is rather the responsability of the release engineers.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months