[JBoss JIRA] (TOOLSDOC-492) Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-492?page=com.atlassian.jira.plug... ]
Nick Boldt updated TOOLSDOC-492:
--------------------------------
Attachment: xref-do-not-render.png
[~mmurray] Found a couple new problems w/ the conversion:
a) chapters have TWO, not ONE top-level entries (=), so in the adoc files we now have in ~/userguide/src/main/asciidoc/ I've indented everything down one level so all the = titles become ==, the == become ===, etc. That fixes an asciidoctor maven build error:
{code}
asciidoctor: ERROR: openshift_tools.adoc: line 5: invalid part, must have at least one section (e.g., chapter, appendix, etc.)
{code}
b) <xref> tags render as "?" and all the content is lost. Do we need to retain these? Screenshot illustrating the adoc vs. docbook code:
!xref-do-not-render.png!
> Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
> -------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-492
> URL: https://issues.jboss.org/browse/TOOLSDOC-492
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta2
>
> Attachments: asciidoc-to-html5-with-sidebar-toc.png, converted-adoc-asciidoc-css-not-github-css.png, converted-adoc-github-css-actual.png, converted-adoc-github-css.png, openshift-chapter-generated-epub.png, openshift-chapter-generated-pdf.png, xref-do-not-render.png
>
>
> With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc!
> What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these:
> http://tools.jboss.org/features/ (with icons that link to projects' latest doc)
> or
> http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked)
> And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release.
> Questions:
> a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype)
> b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1).
> c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported?
> d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming.
> [0] https://github.com/oreillymedia/docbook2asciidoc
> e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone?
> [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio...
> f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]?
> [2] http://tools.jboss.org/downloads/overview.html
> [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17234) Cannot launch BrowserSim on Windows 8.1 (32- or 64-bit) w/ JDK 7 or 8
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17234?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-17234 at 5/6/14 9:13 PM:
------------------------------------------------------------
Additional nitpick...
one error message says "BrowserSim failed to start" (no punctuation), while the other says "BrowserSim failed to start with the following error: ..."
Could they both be amended to use the same "with the following error:" suffix, as it's just better English?
PR w/ suggestions (feel free to cherrypick / adjust as needed):
https://github.com/jbosstools/jbosstools-browsersim/pull/3
was (Author: nickboldt):
Additional nitpick...
one error message says "BrowserSim failed to start" (no punctuation), while the other says "BrowserSim failed to start with the following error: ..."
Could they both be amended to use the same "with the following error:" suffix, as it's just better English?
I suppose I could throw together a PR for this...
> Cannot launch BrowserSim on Windows 8.1 (32- or 64-bit) w/ JDK 7 or 8
> ---------------------------------------------------------------------
>
> Key: JBIDE-17234
> URL: https://issues.jboss.org/browse/JBIDE-17234
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.Beta1
> Environment: Windows 8.1 Pro, 64-bit
> Reporter: Nick Boldt
> Assignee: Ilya Buziuk
> Fix For: 4.2.0.Beta2
>
> Attachments: jbds8b1-win81-failure-to-launch_with_32-bit-jdk.png, jbds8b1-win81-failure-to-launch_with_32-bit-jdk7_installed_d32.png, win81pro-details.png
>
>
> System details: [^win81pro-details.png]
> I have tried the following:
> a) install jbdevstudio-product-universal-8.0.0.Beta1-v20140408-2350-B93.jar via commandline, using JDK 7 (32- and 64-bit) and JDK 8 (64-bit). Using the 32-bit JDK, I've both used and omitted the -d32 flag.
> JDK versions:
> * jdk1.7.0_55 (32- and 64-bit)
> * jdk1.8.0_05 (64-bit)
> b) In Central, click either `Start from scratch > HTML5 Project`, or `Start from a sample > Mobile Applications > kitchensink-html5-mobile`
> c) In Project Explorer, open `src > main > webapp > index.html`
> d) right-click the file and select `Open With > BrowserSim`
> If JBDS was installed in 32-bit mode, you get this error:
> !jbds8b1-win81-failure-to-launch_with_32-bit-jdk7_installed_d32.png!
> If JBDS was installed in 64-bit mode, you get this error:
> !jbds8b1-win81-failure-to-launch_with_32-bit-jdk.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17234) Cannot launch BrowserSim on Windows 8.1 (32- or 64-bit) w/ JDK 7 or 8
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17234?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-17234:
------------------------------------
Additional nitpick...
one error message says "BrowserSim failed to start" (no punctuation), while the other says "BrowserSim failed to start with the following error: ..."
Could they both be amended to use the same "with the following error:" suffix, as it's just better English?
I suppose I could throw together a PR for this...
> Cannot launch BrowserSim on Windows 8.1 (32- or 64-bit) w/ JDK 7 or 8
> ---------------------------------------------------------------------
>
> Key: JBIDE-17234
> URL: https://issues.jboss.org/browse/JBIDE-17234
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.Beta1
> Environment: Windows 8.1 Pro, 64-bit
> Reporter: Nick Boldt
> Assignee: Ilya Buziuk
> Fix For: 4.2.0.Beta2
>
> Attachments: jbds8b1-win81-failure-to-launch_with_32-bit-jdk.png, jbds8b1-win81-failure-to-launch_with_32-bit-jdk7_installed_d32.png, win81pro-details.png
>
>
> System details: [^win81pro-details.png]
> I have tried the following:
> a) install jbdevstudio-product-universal-8.0.0.Beta1-v20140408-2350-B93.jar via commandline, using JDK 7 (32- and 64-bit) and JDK 8 (64-bit). Using the 32-bit JDK, I've both used and omitted the -d32 flag.
> JDK versions:
> * jdk1.7.0_55 (32- and 64-bit)
> * jdk1.8.0_05 (64-bit)
> b) In Central, click either `Start from scratch > HTML5 Project`, or `Start from a sample > Mobile Applications > kitchensink-html5-mobile`
> c) In Project Explorer, open `src > main > webapp > index.html`
> d) right-click the file and select `Open With > BrowserSim`
> If JBDS was installed in 32-bit mode, you get this error:
> !jbds8b1-win81-failure-to-launch_with_32-bit-jdk7_installed_d32.png!
> If JBDS was installed in 64-bit mode, you get this error:
> !jbds8b1-win81-failure-to-launch_with_32-bit-jdk.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17238) Fix broken server build
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17238?page=com.atlassian.jira.plugi... ]
Denis Golovin closed JBIDE-17238.
---------------------------------
Resolution: Done
verified. closing.
> Fix broken server build
> -----------------------
>
> Key: JBIDE-17238
> URL: https://issues.jboss.org/browse/JBIDE-17238
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.2.0.Beta2
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.0.Beta2
>
>
> Server build is broken. It fails with compilation errors.
> {code}[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.20.0:compile (default-compile) on project org.jboss.ide.eclipse.as.classpath.core: Compilation failure: Compilation failure:
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/cache/internal/RuntimeClasspathModelIO.java:[97]
> [ERROR] IMemento[] children = parent.getChildren();
> [ERROR] ^^^^^^^^^^^
> [ERROR] The method getChildren(String) in the type XMLMemento is not applicable for the arguments ()
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/cache/internal/RuntimeClasspathModelIO.java:[100]
> [ERROR] String name = children[i].getNodeName();
> [ERROR] ^^^^^^^^^^^
> [ERROR] The method getNodeName() is undefined for the type IMemento
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/path/internal/RuntimePathProviderFileset.java:[54]
> [ERROR] public String getDisplayString() {
> [ERROR] ^^^^^^^^^^^^^^^^^^
> [ERROR] The method getDisplayString() of type RuntimePathProviderFileset must override a superclass method
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/path/internal/RuntimePathProviderFileset.java:[59]
> [ERROR] public void saveInMemento(XMLMemento memento) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The method saveInMemento(XMLMemento) of type RuntimePathProviderFileset must override a superclass method
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/cache/internal/InternalRuntimeClasspathModel.java:[104]
> [ERROR] public IRuntimePathProvider[] getStandardProviders() {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The method getStandardProviders() of type InternalRuntimeClasspathModel must override a superclass method
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/cache/internal/InternalRuntimeClasspathModel.java:[109]
> [ERROR] public IRuntimePathProvider[] getProvidersForFacet(String id) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The method getProvidersForFacet(String) of type InternalRuntimeClasspathModel must override a superclass method
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/cache/internal/InternalRuntimeClasspathModel.java:[115]
> [ERROR] public IRuntimePathProvider[] getProvidersForFacet(String id, String version) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The method getProvidersForFacet(String, String) of type InternalRuntimeClasspathModel must override a superclass method
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/path/internal/LayeredProductPathProvider.java:[66]
> [ERROR] public void setVariableResolver(IVariableResolver resolver) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The method setVariableResolver(IVariableResolver) of type LayeredProductPathProvider must override a superclass method
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/path/internal/LayeredProductPathProvider.java:[71]
> [ERROR] public String getDisplayString() {
> [ERROR] ^^^^^^^^^^^^^^^^^^
> [ERROR] The method getDisplayString() of type LayeredProductPathProvider must override a superclass method
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.classpath.core/src/org/jboss/ide/eclipse/as/classpath/core/runtime/path/internal/LayeredProductPathProvider.java:[76]
> [ERROR] public void saveInMemento(XMLMemento memento) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The method saveInMemento(XMLMemento) of type LayeredProductPathProvider must override a superclass method
> [ERROR] 10 problems (10 errors)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17234) Cannot launch BrowserSim on Windows 8.1 (32- or 64-bit) w/ JDK 7 or 8
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17234?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov edited comment on JBIDE-17234 at 5/6/14 7:12 PM:
------------------------------------------------------------------------
[~mmurray], I'm working on it just now. If you haven't got Safari and use Oracle VM with javafx - BrowserSim with javaFx browser will be opened and error message will be shown in preferences.
was (Author: kmarmaliykov):
[~mmurray], I'm working on it just now.
> Cannot launch BrowserSim on Windows 8.1 (32- or 64-bit) w/ JDK 7 or 8
> ---------------------------------------------------------------------
>
> Key: JBIDE-17234
> URL: https://issues.jboss.org/browse/JBIDE-17234
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.Beta1
> Environment: Windows 8.1 Pro, 64-bit
> Reporter: Nick Boldt
> Assignee: Ilya Buziuk
> Fix For: 4.2.0.Beta2
>
> Attachments: jbds8b1-win81-failure-to-launch_with_32-bit-jdk.png, jbds8b1-win81-failure-to-launch_with_32-bit-jdk7_installed_d32.png, win81pro-details.png
>
>
> System details: [^win81pro-details.png]
> I have tried the following:
> a) install jbdevstudio-product-universal-8.0.0.Beta1-v20140408-2350-B93.jar via commandline, using JDK 7 (32- and 64-bit) and JDK 8 (64-bit). Using the 32-bit JDK, I've both used and omitted the -d32 flag.
> JDK versions:
> * jdk1.7.0_55 (32- and 64-bit)
> * jdk1.8.0_05 (64-bit)
> b) In Central, click either `Start from scratch > HTML5 Project`, or `Start from a sample > Mobile Applications > kitchensink-html5-mobile`
> c) In Project Explorer, open `src > main > webapp > index.html`
> d) right-click the file and select `Open With > BrowserSim`
> If JBDS was installed in 32-bit mode, you get this error:
> !jbds8b1-win81-failure-to-launch_with_32-bit-jdk7_installed_d32.png!
> If JBDS was installed in 64-bit mode, you get this error:
> !jbds8b1-win81-failure-to-launch_with_32-bit-jdk.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17234) Cannot launch BrowserSim on Windows 8.1 (32- or 64-bit) w/ JDK 7 or 8
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17234?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-17234:
------------------------------------------------
[~mmurray], I'm working on it just now.
> Cannot launch BrowserSim on Windows 8.1 (32- or 64-bit) w/ JDK 7 or 8
> ---------------------------------------------------------------------
>
> Key: JBIDE-17234
> URL: https://issues.jboss.org/browse/JBIDE-17234
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.Beta1
> Environment: Windows 8.1 Pro, 64-bit
> Reporter: Nick Boldt
> Assignee: Ilya Buziuk
> Fix For: 4.2.0.Beta2
>
> Attachments: jbds8b1-win81-failure-to-launch_with_32-bit-jdk.png, jbds8b1-win81-failure-to-launch_with_32-bit-jdk7_installed_d32.png, win81pro-details.png
>
>
> System details: [^win81pro-details.png]
> I have tried the following:
> a) install jbdevstudio-product-universal-8.0.0.Beta1-v20140408-2350-B93.jar via commandline, using JDK 7 (32- and 64-bit) and JDK 8 (64-bit). Using the 32-bit JDK, I've both used and omitted the -d32 flag.
> JDK versions:
> * jdk1.7.0_55 (32- and 64-bit)
> * jdk1.8.0_05 (64-bit)
> b) In Central, click either `Start from scratch > HTML5 Project`, or `Start from a sample > Mobile Applications > kitchensink-html5-mobile`
> c) In Project Explorer, open `src > main > webapp > index.html`
> d) right-click the file and select `Open With > BrowserSim`
> If JBDS was installed in 32-bit mode, you get this error:
> !jbds8b1-win81-failure-to-launch_with_32-bit-jdk7_installed_d32.png!
> If JBDS was installed in 64-bit mode, you get this error:
> !jbds8b1-win81-failure-to-launch_with_32-bit-jdk.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17229) Is BrowserSim 'select JRE' option obsolete?
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17229?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov resolved JBIDE-17229.
--------------------------------------------
Resolution: Rejected
This feature is pretty useful and must stay.
> Is BrowserSim 'select JRE' option obsolete?
> -------------------------------------------
>
> Key: JBIDE-17229
> URL: https://issues.jboss.org/browse/JBIDE-17229
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Konstantin Marmalyukov
>
> The preference to select a JRE with which to run BrowserSim was introduced so that 64-bit Windows users could run the IDE as 64-bit but use BrowserSim in 32-bit (since Apple Safari was only available as 32-bit for Windows).
> Now there is JavaFX option for 32-bit and 64-bit Windows users to run BrowserSIm. So 64-bit Windows users no longer need to install 32-bit Apple Safari and run BrowserSim 32-bit while IDE runs in 64-bit.
> So is there a use case any longer for users to be able to set a preference for a different JRE from the one running the IDE?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17229) Is BrowserSim 'select JRE' option obsolete?
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17229?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-17229:
-----------------------------------------
[~kmarmaliykov], please feel free to resolve as 'not a bug' or 'rejected'. As you point out being able to change what jvm to use is a useful feature.
> Is BrowserSim 'select JRE' option obsolete?
> -------------------------------------------
>
> Key: JBIDE-17229
> URL: https://issues.jboss.org/browse/JBIDE-17229
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Konstantin Marmalyukov
>
> The preference to select a JRE with which to run BrowserSim was introduced so that 64-bit Windows users could run the IDE as 64-bit but use BrowserSim in 32-bit (since Apple Safari was only available as 32-bit for Windows).
> Now there is JavaFX option for 32-bit and 64-bit Windows users to run BrowserSIm. So 64-bit Windows users no longer need to install 32-bit Apple Safari and run BrowserSim 32-bit while IDE runs in 64-bit.
> So is there a use case any longer for users to be able to set a preference for a different JRE from the one running the IDE?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17229) Is BrowserSim 'select JRE' option obsolete?
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17229?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-17229:
-----------------------------------------
Regarding Window 64-bit - switching to 32-bit JRE for BrowserSim might not be necessary if JavaFX is implemented > see JBIDE-17234.
> Is BrowserSim 'select JRE' option obsolete?
> -------------------------------------------
>
> Key: JBIDE-17229
> URL: https://issues.jboss.org/browse/JBIDE-17229
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Konstantin Marmalyukov
>
> The preference to select a JRE with which to run BrowserSim was introduced so that 64-bit Windows users could run the IDE as 64-bit but use BrowserSim in 32-bit (since Apple Safari was only available as 32-bit for Windows).
> Now there is JavaFX option for 32-bit and 64-bit Windows users to run BrowserSIm. So 64-bit Windows users no longer need to install 32-bit Apple Safari and run BrowserSim 32-bit while IDE runs in 64-bit.
> So is there a use case any longer for users to be able to set a preference for a different JRE from the one running the IDE?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17234) Cannot launch BrowserSim on Windows 8.1 (32- or 64-bit) w/ JDK 7 or 8
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17234?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-17234:
-----------------------------------------
[~ibuziuk], now that JavaFX is implemented I think I was expecting JavaFX to be the default for Windows 32- and 64-bit so users don't have to install Safari anymore. Can we get this in for Beta2?
> Cannot launch BrowserSim on Windows 8.1 (32- or 64-bit) w/ JDK 7 or 8
> ---------------------------------------------------------------------
>
> Key: JBIDE-17234
> URL: https://issues.jboss.org/browse/JBIDE-17234
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.Beta1
> Environment: Windows 8.1 Pro, 64-bit
> Reporter: Nick Boldt
> Assignee: Ilya Buziuk
> Fix For: 4.2.0.Beta2
>
> Attachments: jbds8b1-win81-failure-to-launch_with_32-bit-jdk.png, jbds8b1-win81-failure-to-launch_with_32-bit-jdk7_installed_d32.png, win81pro-details.png
>
>
> System details: [^win81pro-details.png]
> I have tried the following:
> a) install jbdevstudio-product-universal-8.0.0.Beta1-v20140408-2350-B93.jar via commandline, using JDK 7 (32- and 64-bit) and JDK 8 (64-bit). Using the 32-bit JDK, I've both used and omitted the -d32 flag.
> JDK versions:
> * jdk1.7.0_55 (32- and 64-bit)
> * jdk1.8.0_05 (64-bit)
> b) In Central, click either `Start from scratch > HTML5 Project`, or `Start from a sample > Mobile Applications > kitchensink-html5-mobile`
> c) In Project Explorer, open `src > main > webapp > index.html`
> d) right-click the file and select `Open With > BrowserSim`
> If JBDS was installed in 32-bit mode, you get this error:
> !jbds8b1-win81-failure-to-launch_with_32-bit-jdk7_installed_d32.png!
> If JBDS was installed in 64-bit mode, you get this error:
> !jbds8b1-win81-failure-to-launch_with_32-bit-jdk.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months