[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:
-----------------------------------------
[~kmarmaliykov], [~ibuziuk]:
* Is JavaFx default for Windows 32-bit also? Or if Safari is installed does BrowserSim by default use SWT Webkit?
* Is the option for 64-bit Windows users to install Safari and use 32-bit jvm still available?
> 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: Konstantin Marmalyukov
> 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, 10 months
[JBoss JIRA] (JBDS-3060) Download page typo: EAP > JBoss EAP
by Michelle Murray (JIRA)
Michelle Murray created JBDS-3060:
-------------------------------------
Summary: Download page typo: EAP > JBoss EAP
Key: JBDS-3060
URL: https://issues.jboss.org/browse/JBDS-3060
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: website
Affects Versions: 8.0.0.Beta2
Reporter: Michelle Murray
http://www.qa.jboss.com/binaries/RHDS/builds/development/8.0.0.Beta2a-bui...
In the 'Installers' list, second bullet is 'Installer with EAP'. EAP is not an accepted acronym, JBoss EAP is the shortest abbreviation.
In reality, because this page mentions JBoss EAP nowhere else, the product name should be used in full in this first instance. So 'Installer with Red Hat JBoss Enterprise Application Platform'. But I'll leave that to your discretion.
I realise this is an internal page but reporting issue in case it propagates to external pages too.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (TOOLSDOC-453) Generate Release Notes doc for JBDS 8.0.0Beta2
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-453?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-453:
-------------------------------------
Sprint: 2014/S9 (26-May > 8-Jun)
> Generate Release Notes doc for JBDS 8.0.0Beta2
> ----------------------------------------------
>
> Key: TOOLSDOC-453
> URL: https://issues.jboss.org/browse/TOOLSDOC-453
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Release Notes
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta2
>
> Original Estimate: 6 hours
> Remaining Estimate: 6 hours
>
> Doc sections:
> 1. Introduction to Red Hat JBoss Developer Studio
> 1.1. About Red Hat JBoss Developer Studio
> 1.2. Use Cases of JBoss Developer Studio
> 2. About this Release
> 3. New Features
> 4. Resolved Issues
> 5. Known Issues
> 6. Apply this Release
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBTIS-280) Update JBT IS TP build to latest tycho (and discover missing dependencies!)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-280?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-280:
----------------------------------
With updated PR 195 (3rd commit) everything resolved locally so with the PR merged into master, I've kicked this:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/SOAT... >=175
[~pleacu]I set the job to use STAGE = true and VERSION = 4.2.0.Beta1-SNAPSHOT so it wouldn't conflict w/ the existing Alpha3 TP you have... in case we have to rollback or something.
> Update JBT IS TP build to latest tycho (and discover missing dependencies!)
> ---------------------------------------------------------------------------
>
> Key: JBTIS-280
> URL: https://issues.jboss.org/browse/JBTIS-280
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: target-platform
> Affects Versions: 4.2.0.Alpha1-TP
> Reporter: Nick Boldt
> Fix For: 4.2.0.Beta1-TP
>
>
> Wanted to see if the JBT IS TP could fetch sources, and it can. As it was building, I noticed that you're using Tycho 0.18.1 (not 0.20.0 or 0.21.0-SNAPSHOT) and a very old version of org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0.CR2.
> So, I bumped you up to 0.20.0 and 0.19.0-SNAPSHOT, and got this error:
> {code}
> Unable to satisfy dependency from
> org.springframework.osgi.io 1.2.1 to
> package org.springframework.util [2.5.6,4.0.0).;
> No solution found because the
> problem is unsatisfiable.
> {code}
> Attached is a PR which shows what I tried, how it failed, and what I tried to do to fix it.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17480) Error in validation of jboss-deployment-structure.xml
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17480?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17480:
-------------------------------------
I think I pulled all the schema files from here: http://www.jboss.org/schema/jbossas/jboss-deployment-structure-1_2.xsd
Not sure if there's a new updated folder... I'll try to look into it.
> Error in validation of jboss-deployment-structure.xml
> -----------------------------------------------------
>
> Key: JBIDE-17480
> URL: https://issues.jboss.org/browse/JBIDE-17480
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Environment: Version: 8.0.0.Beta1
> Build id: Beta1-v20140408-2350-B93
> Build date: 20140408-2350
> Reporter: Emil Cervenan
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Beta3
>
>
> Wrong validation error on jboss-deployment-structure.xml file:
> {code}
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
> <deployment>
> <dependencies>
> <module name="org.apache.log4j" slot="main" export="true"/>
> </dependencies>
> <exclusions>
> <module name="org.hibernate"/>
> </exclusions>
> </deployment>
> </jboss-deployment-structure>
> {code}
> Error:
> {code}
> cvc-complex-type.2.4.b: The content of element 'deployment' is not complete. One of '{"urn:jboss:deployment-structure:1.2":module-alias, "urn:jboss:deployment-structure:1.2":exports, "urn:jboss:deployment-structure:1.2":resources, "urn:jboss:deployment-structure:1.2":transformers, "urn:jboss:deployment-structure:1.2":local-last, "urn:jboss:deployment-structure:1.2":exclude-subsystems}' is expected.
> {code}
> Same for urn:jboss:deployment-structure:1.1.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17510) JBT 4.2.0.Beta2 on Fedora 18 x64 crashes with SIGSEGV
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17510?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-17510:
-------------------------------
Environment:
JBT 4.2.0.Beta2 (not respin-a)
Fedora 18 x64
$➔ uname -a
Linux thunk 3.11.9-100.fc18.x86_64 #1 SMP Wed Nov 20 21:22:39 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
$➔ java -version
java version "1.8.0"
Java(TM) SE Runtime Environment (build 1.8.0-b132)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
was:
JBDS 8.0.beta2
RHEL 6.5
uname -a
Linux 2.6.32-431.11.2.el6.x86_64 #1 SMP Mon Mar 3 13:32:45 EST 2014 x86_64 x86_64 x86_64 GNU/Linux
OpenJDK 1.7
> JBT 4.2.0.Beta2 on Fedora 18 x64 crashes with SIGSEGV
> -----------------------------------------------------
>
> Key: JBIDE-17510
> URL: https://issues.jboss.org/browse/JBIDE-17510
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Environment: JBT 4.2.0.Beta2 (not respin-a)
> Fedora 18 x64
> $➔ uname -a
> Linux thunk 3.11.9-100.fc18.x86_64 #1 SMP Wed Nov 20 21:22:39 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> $➔ java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build 1.8.0-b132)
> Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
> Reporter: Len DiMaggio
> Assignee: Snjezana Peco
> Priority: Critical
>
> On Fedora 18 x64 w/ JDK 1.8.0, I get fairly frequent crashes. Sample Eclipse console log showing the crash and SIGSEGV:
> https://issues.jboss.org/secure/attachment/12382836/12382836_eclipse.log....
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months