May 2015 - jbosstools-issues - Jboss List Archives

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

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19750: ---------------------------------- Summary: 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 Reporter: Nick Boldt {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-19750) Install grinder w/ SWTBot 2.2.1.201402241301 fails to run on RHEL7: No more handles!

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19750?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19750: ---------------------------------- Assignee: Mickael Istria > 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 > 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-19637) Runtime download not working from New Server dialog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19637: -------------------------------- Labels: help_wanted (was: ) > Runtime download not working from New Server dialog > --------------------------------------------------- > > Key: JBIDE-19637 > URL: https://issues.jboss.org/browse/JBIDE-19637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: help_wanted > Fix For: 4.3.0.Beta1 > > > When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything. > If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work. > This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19637) Runtime download not working from New Server dialog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19637: ------------------------------------- Breakpoints on Exception and Throwable are also not being hit on Fred's Mac. I've verified other servertools code that has links (for example the "Download Additional Server Adapters" link on the first page of new server wizard) work properly, and I've compared their code to mine and they both extend selectionAdapter, with same method implemented, so no obvious differences there. But I can't see at all why it's working this way. > Runtime download not working from New Server dialog > --------------------------------------------------- > > Key: JBIDE-19637 > URL: https://issues.jboss.org/browse/JBIDE-19637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything. > If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work. > This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19637) Runtime download not working from New Server dialog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19637: ------------------------------------- So... Fred was not able to replicate in jbds alpha2. Fred *was* able to reproduce in jbt+master. But... this is extremely extremely weird. No breakpoints are hit when clicking the link. Clicking the link appears to select it, but the selection adapter is not notified. Typing the spacebar AFTER attempting to click *does* open the downloadRuntimes page, and the selectionAdapter breakpoint gets hit. I'm not able to replicate at all on Linux, no matter the usecase. So... I'm pretty much stumped, and without full-time access to a Mac, I'm really not sure I can get any further on this issue. [~mmalina] Can you verify this is happening in jbt or jbds? Very strange stuff here. > Runtime download not working from New Server dialog > --------------------------------------------------- > > Key: JBIDE-19637 > URL: https://issues.jboss.org/browse/JBIDE-19637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything. > If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work. > This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19749) Enhancements to jbosstools-devdoc

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19749: ---------------------------------- Summary: Enhancements to jbosstools-devdoc Key: JBIDE-19749 URL: https://issues.jboss.org/browse/JBIDE-19749 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: build Affects Versions: 4.3.0.Beta1 Reporter: Nick Boldt * Switch URLs to use git:// instead of git@ - https://github.com/jbosstools/jbosstools-devdoc/pull/42/files#r29133660 * introduce hub earlier and refer to the hub way instead of the git way to do stuff * tweak instructions for checking out and tracking branches - https://github.com/jbosstools/jbosstools-devdoc/pull/42/files#r29133881 {code} git checkout -b \{localname} \{remote}/\{upstream-name} - for when you want a local branch name different from upstream git checkout --track \{remote}/\{upstreambranchname} - for when you want a local topic branch with the same name as upstream {code} - https://github.com/jbosstools/jbosstools-devdoc/pull/42/files#r29175940 * remove refs to Central/EA target platforms because in Max's definition they're not target platforms unless a dev uses the .target file * remove refs to /static/ when talking about target platform publishing locations; create a doc explaining where things are published (JBDS-3208) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19749) Enhancements to jbosstools-devdoc

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19749?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19749: ------------------------------- Fix Version/s: 4.3.0.Beta1 > Enhancements to jbosstools-devdoc > --------------------------------- > > Key: JBIDE-19749 > URL: https://issues.jboss.org/browse/JBIDE-19749 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Fix For: 4.3.0.Beta1 > > > * Switch URLs to use git:// instead of git@ - https://github.com/jbosstools/jbosstools-devdoc/pull/42/files#r29133660 > * introduce hub earlier and refer to the hub way instead of the git way to do stuff > * tweak instructions for checking out and tracking branches - https://github.com/jbosstools/jbosstools-devdoc/pull/42/files#r29133881 > {code} > git checkout -b \{localname} \{remote}/\{upstream-name} - for when you want a local branch name different from upstream > git checkout --track \{remote}/\{upstreambranchname} - for when you want a local topic branch with the same name as upstream > {code} - https://github.com/jbosstools/jbosstools-devdoc/pull/42/files#r29175940 > * remove refs to Central/EA target platforms because in Max's definition they're not target platforms unless a dev uses the .target file > * remove refs to /static/ when talking about target platform publishing locations; create a doc explaining where things are published (JBDS-3208) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19749) Enhancements to jbosstools-devdoc

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19749?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19749: ---------------------------------- Assignee: Nick Boldt > Enhancements to jbosstools-devdoc > --------------------------------- > > Key: JBIDE-19749 > URL: https://issues.jboss.org/browse/JBIDE-19749 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > * Switch URLs to use git:// instead of git@ - https://github.com/jbosstools/jbosstools-devdoc/pull/42/files#r29133660 > * introduce hub earlier and refer to the hub way instead of the git way to do stuff > * tweak instructions for checking out and tracking branches - https://github.com/jbosstools/jbosstools-devdoc/pull/42/files#r29133881 > {code} > git checkout -b \{localname} \{remote}/\{upstream-name} - for when you want a local branch name different from upstream > git checkout --track \{remote}/\{upstreambranchname} - for when you want a local topic branch with the same name as upstream > {code} - https://github.com/jbosstools/jbosstools-devdoc/pull/42/files#r29175940 > * remove refs to Central/EA target platforms because in Max's definition they're not target platforms unless a dev uses the .target file > * remove refs to /static/ when talking about target platform publishing locations; create a doc explaining where things are published (JBDS-3208) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19735) Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)"

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19735?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-19735. --------------------------------- Fix Version/s: 4.3.0.Alpha2 Resolution: Done I fixed the offending version range. The problem only occurs when AngularJS tooling is already installed. > Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19735 > URL: https://issues.jboss.org/browse/JBIDE-19735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Fix For: 4.3.0.Alpha2 > > Attachments: jbosstools-diagnostics-20150428160436.zip > > > To recreate: > * Create from scratch a new AngularJS with Forge project. > * Have the project creation install AngularJS Eclipse > Observe this error reported in a dialog in the UI: > An error has occurred. See error log for more details. > invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" > The full .log is in the attached diagnostic file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3208: ----------------------------------- Can we remove old stuff from http://download.jboss.org/jbosstools/builds/staging/ or at least symlink it to the new content? > reorg/refactor directories for consistency across JBT/JBDS > ---------------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > Latest suggestion: > * /\{mars,9.0}/ > ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/ > *** /*updates*/ > **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/ > ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/ > *** /*builds*/ > **** /<job-name>/ > ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/ > --- > Older idea: > {code} > <download.jboss.org,devstudio.redhat.com> > <earlyaccess,updates,discovery>/<mars,9.0> > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last N builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- 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