[JBoss JIRA] (JBIDE-19050) BrowserSim will not start with Oracle JDK 9 EA
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19050?page=com.atlassian.jira.plugi... ]
Len DiMaggio updated JBIDE-19050:
---------------------------------
Labels: Java9 (was: )
> BrowserSim will not start with Oracle JDK 9 EA
> ----------------------------------------------
>
> Key: JBIDE-19050
> URL: https://issues.jboss.org/browse/JBIDE-19050
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.2.Final
> Reporter: Martin Malina
> Assignee: Konstantin Marmalyukov
> Labels: Java9
> Fix For: 4.3.0.Alpha1
>
> Attachments: jdk9-mac-paths.txt
>
>
> Today I briefly tried out Oracle JDK 9 Early Access from here:
> https://jdk9.java.net/download/
> {code}
> nattura:8.0.2 rasp$ java -version
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b45)
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode)
> {code}
> When I had JBDS 8.0.2 running with this Java and then clicked the BrowserSim button, I got this error:
> {code}
> javafx/embed/swt/FXCanvas
> Stack trace:
> java.lang.NoClassDefFoundError: javafx/embed/swt/FXCanvas
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:759)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:262)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:28)
> at org.jboss.tools.vpe.browsersim.ui.skin.ResizableSkin.createControls(ResizableSkin.java:92)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim.initSkin(BrowserSim.java:183)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim.open(BrowserSim.java:162)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim.open(BrowserSim.java:137)
> at org.jboss.tools.vpe.browsersim.BrowserSimRunner.main(BrowserSimRunner.java:105)
> Caused by: java.lang.ClassNotFoundException: javafx.embed.swt.FXCanvas
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:262)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 18 more
> {code}
> This seems like JavaFX might be missing. But on the download page, there are many mentions of JavaFX, so I'm not sure.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19132) For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [OpenShift]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19132?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19132:
------------------------------------
That one was one step: "upversion".
This one is three steps:
1. "upversion"
2. "use the correct parent pom"
3. "build with latest target platform"
> For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [OpenShift]
> ---------------------------------------------------------------------
>
> Key: JBIDE-19132
> URL: https://issues.jboss.org/browse/JBIDE-19132
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: task
> Fix For: 4.2.3.Beta1
>
>
> For JBIDE 4.2.3.Beta1 [OpenShift]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3.
> Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.3.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version:
> {code}
> mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT
> {code}
> 2. 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 OpenShift 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-19132) For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [OpenShift]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19132?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19132:
-------------------------------
Description:
For JBIDE 4.2.3.Beta1 [OpenShift]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3.
Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.3.Beta1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version:
{code}
mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT
{code}
4. 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 OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
was:
For JBIDE 4.2.3.Beta1 [OpenShift]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3.
Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.3.Beta1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version:
{code}
mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT
{code}
2. 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 OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [OpenShift]
> ---------------------------------------------------------------------
>
> Key: JBIDE-19132
> URL: https://issues.jboss.org/browse/JBIDE-19132
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: task
> Fix For: 4.2.3.Beta1
>
>
> For JBIDE 4.2.3.Beta1 [OpenShift]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3.
> Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.3.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version:
> {code}
> mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT
> {code}
> 4. 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 OpenShift 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] (JBDS-3338) JBDS Build fails with Tycho 0.22
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3338?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3338:
--------------------------------------
This seems to be caused by Tycho now looking directly in target/ folder for a p2 repo, which in most case should be an empty repository. But for JBDS, there are some composite_.xml files that are created and that make Tycho believe there is actually a repo there (which is wrong).
> JBDS Build fails with Tycho 0.22
> --------------------------------
>
> Key: JBDS-3338
> URL: https://issues.jboss.org/browse/JBDS-3338
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 9.0.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 9.0.0.Alpha1
>
>
> JBDS build is failing with Tycho 0.22
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products (default-publish-products) on project installer:
> Execution default-publish-products of goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products failed:
> org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at
> file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/.
> No repository found at file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/jbds/.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3338) JBDS Build fails with Tycho 0.22
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3338?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3338:
-----------------------------
Component/s: build
updatesite
> JBDS Build fails with Tycho 0.22
> --------------------------------
>
> Key: JBDS-3338
> URL: https://issues.jboss.org/browse/JBDS-3338
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 9.0.0.Alpha1
> Reporter: Mickael Istria
> Priority: Blocker
> Fix For: 9.0.0.Alpha1
>
>
> JBDS build is failing with Tycho 0.22
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products (default-publish-products) on project installer:
> Execution default-publish-products of goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products failed:
> org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at
> file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/.
> No repository found at file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/jbds/.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3338) JBDS Build fails with Tycho 0.22
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3338?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3338:
-----------------------------
Affects Version/s: 9.0.0.Alpha1
> JBDS Build fails with Tycho 0.22
> --------------------------------
>
> Key: JBDS-3338
> URL: https://issues.jboss.org/browse/JBDS-3338
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 9.0.0.Alpha1
> Reporter: Mickael Istria
> Priority: Blocker
> Fix For: 9.0.0.Alpha1
>
>
> JBDS build is failing with Tycho 0.22
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products (default-publish-products) on project installer:
> Execution default-publish-products of goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products failed:
> org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at
> file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/.
> No repository found at file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/jbds/.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3338) JBDS Build fails with Tycho 0.22
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3338?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-3338:
--------------------------------
Assignee: Mickael Istria
> JBDS Build fails with Tycho 0.22
> --------------------------------
>
> Key: JBDS-3338
> URL: https://issues.jboss.org/browse/JBDS-3338
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 9.0.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 9.0.0.Alpha1
>
>
> JBDS build is failing with Tycho 0.22
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products (default-publish-products) on project installer:
> Execution default-publish-products of goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products failed:
> org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at
> file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/.
> No repository found at file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/jbds/.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19096:
---------------------------------------------
by "pasting' do you mean that users will provide a unique key instead of their password ?
so could just use the exact same UI for now, right?
> Connection wizard: Allow v2 and v3 Connections
> ----------------------------------------------
>
> Key: JBIDE-19096
> URL: https://issues.jboss.org/browse/JBIDE-19096
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Andre Dietisheim
> Labels: connection_wizard
> Fix For: 4.3.0.Alpha1
>
> Attachments: fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png
>
>
> !screenshot-openshift-signin.png!
> In order to allow us to present v2 and v3 connections we have to change the connection wizard:
> When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different:
> * v2 connections currently use username/password (and will most likely also allow x509, kerberos)
> * v3 connections will most likely require OAuth settings.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months