May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19571) Add FSW to downloadable runtimes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19571?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19571: --------------------------------------- What we could do is have a prepared xml config (or is it a property file?) and use it to install FSW automatically, without user interaction/gui. But that would be cumbersome to maintain - it has to contain all the properties available during the installation. > Add FSW to downloadable runtimes > -------------------------------- > > Key: JBIDE-19571 > URL: https://issues.jboss.org/browse/JBIDE-19571 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > FSW 6.0 is not available in download runtimes -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-433) MASTER build of Fuse tooling in JBDS-IS 8.0.2.ER1

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-433: --------------------------------------- Summary: MASTER build of Fuse tooling in JBDS-IS 8.0.2.ER1 Key: JBTIS-433 URL: https://issues.jboss.org/browse/JBTIS-433 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 8.0.2.CR1 Reporter: Andrej Podhradsky Current build of JBDS-IS 8.0.2.ER1 contains MASTER build of Fuse tooling, namely 7.3.0.v20150428-1634-H488-MASTER. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-432) Cannot install JBoss Integration and SOA Development from non-earlyaccess site

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-432: --------------------------------------- Summary: Cannot install JBoss Integration and SOA Development from non-earlyaccess site Key: JBTIS-432 URL: https://issues.jboss.org/browse/JBTIS-432 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 8.0.2.CR1 Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.2.ER1 (without earlyaccess) Reporter: Andrej Podhradsky Cannot install JBoss Integration and SOA Development from non-earlyaccess site, namely if you try to install com.jboss.devstudio.integration-stack.soa.feature. Note that this is not a common use case since you have to uncheck 'Group items by category' during installation. The problem is that this feature includes switchyard features which are available only on early access. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-424) Wrong title at JBDS-IS 8.0.1.GA update site

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-424?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-424. ----------------------------------- Verified > Wrong title at JBDS-IS 8.0.1.GA update site > ------------------------------------------- > > Key: JBTIS-424 > URL: https://issues.jboss.org/browse/JBTIS-424 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Optional > Fix For: 8.0.1.GA > > > There a wrong title at > http://download.englab.brq.redhat.com/pub/rhel/jbossqa/services/http/bina... > "JBoss Developer Studio Integration Stack - Early Access Release Update Site" > but it is not an earlyaccess. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17284) OpenJDK seem to have issues with SSL/TLS handshakes when using URLConnection

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17284?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-17284: ------------------------------------- Not able to reproduce the issue on RHEL 7 x64 against OpenJDK 1.7.0_79. Works fine against both gtk 2 & gtk 3 !vpe.png|thumbnail! > OpenJDK seem to have issues with SSL/TLS handshakes when using URLConnection > ---------------------------------------------------------------------------- > > Key: JBIDE-17284 > URL: https://issues.jboss.org/browse/JBIDE-17284 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, xulrunner > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbds-via-html5-vpe.png, vpe.png > > > We've received multiple reports about instant crashes of users running JBoss Tools and Developer Studio. > The common issue is that it happens when they use OpenJDK vm, not Oracle. > The crash log normally contains something similar to: > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > j sun.security.pkcs11.wrapper.PKCS11.C_CreateObject(J[Lsun/security/pkcs11/wrapper/CK_ATTRIBUTE;)J+0 > j sun.security.pkcs11.P11ECKeyFactory.generatePublic(Ljava/security/spec/ECPoint;Ljava/security/spec/ECParameterSpec;)Ljava/security/PublicKey;+170 > j sun.security.pkcs11.P11ECKeyFactory.engineGeneratePublic(Ljava/security/spec/KeySpec;)Ljava/security/PublicKey;+80 > j java.security.KeyFactory.generatePublic(Ljava/security/spec/KeySpec;)Ljava/security/PublicKey;+25 > j sun.security.ssl.HandshakeMessage$ECDH_ServerKeyExchange.<init>(Lsun/security/ssl/HandshakeInStream;Ljava/security/PublicKey;[B[BLjava/util/Collection;Lsun/security/ssl/ProtocolVersion;)V+228 > Opening this bug to collect and use a key issue for hunting down the cause. > Note: This issue is *not* specific to JBoss Tools as far as I can see, but it does affect us since we lookup a file located behind https url at key times which seem to trigger the crash. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17284) OpenJDK seem to have issues with SSL/TLS handshakes when using URLConnection

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17284?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-17284: -------------------------------- Attachment: vpe.png > OpenJDK seem to have issues with SSL/TLS handshakes when using URLConnection > ---------------------------------------------------------------------------- > > Key: JBIDE-17284 > URL: https://issues.jboss.org/browse/JBIDE-17284 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, xulrunner > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbds-via-html5-vpe.png, vpe.png > > > We've received multiple reports about instant crashes of users running JBoss Tools and Developer Studio. > The common issue is that it happens when they use OpenJDK vm, not Oracle. > The crash log normally contains something similar to: > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > j sun.security.pkcs11.wrapper.PKCS11.C_CreateObject(J[Lsun/security/pkcs11/wrapper/CK_ATTRIBUTE;)J+0 > j sun.security.pkcs11.P11ECKeyFactory.generatePublic(Ljava/security/spec/ECPoint;Ljava/security/spec/ECParameterSpec;)Ljava/security/PublicKey;+170 > j sun.security.pkcs11.P11ECKeyFactory.engineGeneratePublic(Ljava/security/spec/KeySpec;)Ljava/security/PublicKey;+80 > j java.security.KeyFactory.generatePublic(Ljava/security/spec/KeySpec;)Ljava/security/PublicKey;+25 > j sun.security.ssl.HandshakeMessage$ECDH_ServerKeyExchange.<init>(Lsun/security/ssl/HandshakeInStream;Ljava/security/PublicKey;[B[BLjava/util/Collection;Lsun/security/ssl/ProtocolVersion;)V+228 > Opening this bug to collect and use a key issue for hunting down the cause. > Note: This issue is *not* specific to JBoss Tools as far as I can see, but it does affect us since we lookup a file located behind https url at key times which seem to trigger the crash. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19738) Failed runtime download offers no error message

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19738?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19738: --------------------------------------- OK, so I should have been more specific :) In my case it was directly connected to JBIDE-19571 (and I then assumed that it applies to other kinds of errors as well). So can you please try to point your Eclipse to the previous version of stacks.yaml? The one with the broken FSW definition? Of course a wrong definition should not happen, but I think the tools should still error properly in such case. I don't remember the property you need to supply to Eclipse with the custom url, but this is the file you should try: https://raw.githubusercontent.com/jboss-developer/jboss-stacks/84083f4b5e... > Failed runtime download offers no error message > ----------------------------------------------- > > Key: JBIDE-19738 > URL: https://issues.jboss.org/browse/JBIDE-19738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > While verifying JBIDE-19571 the runtime download failed and there was no error whatsoever. The download of FSW 6.0 almost started, but after a few seconds on the progress bar an error window showed up for a moment and then disappeared again and the download window was gone, too. After this, there was no error in the error view or the workspace log. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19750) Install grinder w/ SWTBot 2.2.1.201402241301 fails to run on RHEL7: No more handles!

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19750?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19750: ---------------------------------------- Thanks for opening the jira. I looked at it before the week-end and did not find the cause of the issue. Handles are typically consumed by graphics elements (color, images, fonts, shells...) and SWTBot doesn't create any graphic element, so it's very unlikely that this is related to SWTBot at all. I tried to reproduce it locally, but it worked without issue. I believe the main change might be the newer version of Central, using HTML now. so trying to hack the DefaultType of browser is a good idea. > Install grinder w/ SWTBot 2.2.1.201402241301 fails to run on RHEL7: No more handles! > ------------------------------------------------------------------------------------ > > Key: JBIDE-19750 > URL: https://issues.jboss.org/browse/JBIDE-19750 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > > {code} > 16:48:30 Installing org.eclipse.swtbot.eclipse.test.junit.feature.group 2.2.1.201402241301. > ... > 13:39:08 !MESSAGE Internal browser is not available: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet] > 13:43:18 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 253.079 sec > 13:43:18 > 13:43:18 Testcase: testInstall took 252.166 sec > {code} - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > I tried to run using `-Dorg.eclipse.swt.browser.DefaultType=webkit` as a script param for `testInstall.groovy` but it must not have passed through to the eclipse install process, as the above error suggests. > Wondering if ... > a) passing through a different *swt.browser.DefaultType*, &/or > b) using a newer SWTBot (which works with Luna [1] now?) > ... might help. > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=464619 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18772: ---------------------------------------- thanks for updating the mars jobs. I'd like to keep the jira open to track adoption of such profile and scripts for the aggregators. > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: jbds-publish-to-snapshots.png > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19751) Update Sapphire to latest 9.0.0.x version

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19751?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19751: ---------------------------------------- Here is the file that defines which version of Sapphire gets into the aggregator: http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/tree/sapphir... . Currently, it's still the older verison. > Update Sapphire to latest 9.0.0.x version > ----------------------------------------- > > Key: JBIDE-19751 > URL: https://issues.jboss.org/browse/JBIDE-19751 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: arquillian, batch, target-platform > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > > The current version (included in Mars 6 update site) is 9.0.0.201408261741. > It doesn't include some critical fixes. > We need to figure out what version will be included in Mars final and what we can do now: > - Update our TP to the latest sapphire nightly build? - https://hudson.eclipse.org/sapphire/job/9.0.x/ > - Wait for Mars Final? > - Set proper range for Sapphire dependencies in Batch plugin. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2015