August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4009) Improve Error Reporting in DevSuite Installer

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4009: ----------------------------------- Summary: Improve Error Reporting in DevSuite Installer Key: JBDS-4009 URL: https://issues.jboss.org/browse/JBDS-4009 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Epic Reporter: Denis Golovin -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4002) OpenJDK detection does not work for build 1.8.0_101

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4002?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4002: -------------------------------- Fix Version/s: 10.1.0.GA > OpenJDK detection does not work for build 1.8.0_101 > --------------------------------------------------- > > Key: JBDS-4002 > URL: https://issues.jboss.org/browse/JBDS-4002 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > > Because of changed format for version console output, installer cannot detect installed JVM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23008) openshift.cdk.feature.source missing from JBT site; causes baseline check to fail

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23008?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23008: ------------------------------------ Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=1517 > openshift.cdk.feature.source missing from JBT site; causes baseline check to fail > --------------------------------------------------------------------------------- > > Key: JBIDE-23008 > URL: https://issues.jboss.org/browse/JBIDE-23008 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift, updatesite > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Since the weekend (after I published an AM3 build into /neon/staging/updates/): > {code} > [INFO] --- tycho-source-plugin:0.25.0:plugin-source (plugin-source) @ org.jboss.tools.openshift.cdk.server --- > [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT-sources.jar > [INFO] > [INFO] --- target-platform-configuration:0.25.0:target-platform (default-target-platform) @ org.jboss.tools.openshift.cdk.server --- > [INFO] > [INFO] --- tycho-packaging-plugin:0.25.0:package-plugin (default-package-plugin) @ org.jboss.tools.openshift.cdk.server --- > [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT.jar > [INFO] > [INFO] --- tycho-p2-plugin:0.25.0:p2-metadata-default (default-p2-metadata-default) @ org.jboss.tools.openshift.cdk.server --- > [WARNING] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml: baseline and build artifacts have same version but different contents > [INFO] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml > The main artifact has been replaced with the baseline version. > The following attached artifacts are not present in the baseline and have been removed: [sources]{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22880) List of modules filtered by "deployed" is always empty on the ServerEditor Deployment tab

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22880?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22880: ------------------------------------- https://github.com/jbosstools/jbosstools-base/pull/524 https://github.com/jbosstools/jbosstools-server/pull/443/files The server pull depends on the base pull. > List of modules filtered by "deployed" is always empty on the ServerEditor Deployment tab > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22880 > URL: https://issues.jboss.org/browse/JBIDE-22880 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final, 4.4.0.Final > Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. > Reporter: Mikhail Kalkov > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > Attachments: test-projects.zip > > > It is impossible to select "filter by" dropdown or press "Refresh Table" on the deployment tab of ServerEditor in JBoss Developer Studio when anything is deployed. I think it should be possible to change filter configuration but do not edit the table itself. Otherwise, both "Refresh" button and some of filter options becomes useless. See Steps to Reproduce for more details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3879) AERI - Closing the 'configure projects' dialog disables enabled projects

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3879?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3879: --------------------------------- Fix Version/s: 10.1.0.GA (was: 10.1.0.AM3) > AERI - Closing the 'configure projects' dialog disables enabled projects > ------------------------------------------------------------------------ > > Key: JBDS-3879 > URL: https://issues.jboss.org/browse/JBDS-3879 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: aeri, target-platform > Affects Versions: 10.0.0.Alpha1 > Environment: Version: 10.0.0.Alpha1 > Build id: Alpha1-v20160430-1625-B5264 > Build date: 20160430-1625 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 10.1.0.GA > > Attachments: after.png, before.png > > > To recreate: > * Navigate to: Preferences->General->Error Reporting > * Open 'configure projects' dialog > * Enable one or more projects, click on "Enable" > * Open 'configure projects' dialog > * Close the dialog (select the 'x' at upper right) > * Open 'configure projects' dialog > * Observe that the selections are now disabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-391) Enable JSDT Outline view in Neon [EBZ#499788]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-391?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk commented on ERT-391: --------------------------------- [~amisevsk], pushed to master. One thing I noticed while checking the gerrit change is that Outline view is not refreshing on js file change. In order to update outline I have to close and open the file again. Do you experience the same behaviour ? > Enable JSDT Outline view in Neon [EBZ#499788] > --------------------------------------------- > > Key: ERT-391 > URL: https://issues.jboss.org/browse/ERT-391 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Angel Misevski > Labels: 3.8.1, General, bzira > Fix For: Neon.1 (4.6) > > > As reported in [#1], the Outline view showing the AST of a JavaScript source file is not working properly. > Steps to reproduce: > - unzip and start eclipse-javascript-neon-R > - create a javascript project and paste the code at: http://pastebin.com/BqnJBy5C > - observe the outline does not show the .js AST: http://imgur.com/HMUqjBi.png > This issue is urgent as we have one last sprint before shipping Neon.1. > > [#1] http://stackoverflow.com/questions/38955947/enabling-the-jsdt-outline-vie... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22699) BrowserUtilTest.testCreateBrowser failure

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22699?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22699: ----------------------------------- Sprint: devex #119 August 2016 (was: RHDEVDOCS Sprint 119) > BrowserUtilTest.testCreateBrowser failure > ----------------------------------------- > > Key: JBIDE-22699 > URL: https://issues.jboss.org/browse/JBIDE-22699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.4.1.AM1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.4.1.Final > > > org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:712) > at org.junit.Assert.assertNotNull(Assert.java:722) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser(BrowserUtilTest.java:32) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-837) JBTIS Target Platform - Neon - sync with JBT 4.4.1.AM3

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-837?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-837: ----------------------------- Description: *Reason:* Sync w/ 4.4.1.AM3 *Project page/sources:* *Version:* .4.4.0.Alpha2 *License and owner:* EPL *Original p2 repo:* *JBoss mirror:* *Include Sources:* Yes *Affected JBoss Tools components:* IS *Include in JBDS:* Yes (IS) *Type of dependency:* distribution *List of bundles added/removed:* {code} < org.jboss.tools.project.examples.feature.feature.group [3.1.1.v20160614-2134] < org.jboss.tools.project.examples [3.1.1.v20160614-2134] < org.jboss.tools.project.examples.feature.feature.jar [3.1.1.v20160614-2134] > org.jboss.tools.project.examples.feature.feature.group [3.1.1.v20160812-0234] > org.jboss.tools.project.examples [3.1.1.v20160812-0234] > org.jboss.tools.project.examples.feature.feature.jar [3.1.1.v20160812-0234] === Summary === file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 3 unique IUs file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 3 unique IUs < org.jboss.tools.project.examples.feature.feature.jar [3.1.1.v20160614-2134] < org.jboss.tools.project.examples.feature.feature.group [3.1.1.v20160614-2134] < org.jboss.tools.project.examples [3.1.1.v20160614-2134] > org.jboss.tools.project.examples [3.1.1.v20160812-0234] > org.jboss.tools.project.examples.feature.feature.jar [3.1.1.v20160812-0234] > org.jboss.tools.project.examples.feature.feature.group [3.1.1.v20160812-0234] === Summary === file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 3 unique IUs file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 3 unique IUs {code} was: *Reason:* Sync w/ 4.4.1.AM3 *Project page/sources:* *Version:* .4.4.0.Alpha2 *License and owner:* EPL *Original p2 repo:* *JBoss mirror:* *Include Sources:* Yes *Affected JBoss Tools components:* IS *Include in JBDS:* Yes (IS) *Type of dependency:* distribution *List of bundles added/removed:* {code} {code} > JBTIS Target Platform - Neon - sync with JBT 4.4.1.AM3 > ------------------------------------------------------ > > Key: JBTIS-837 > URL: https://issues.jboss.org/browse/JBTIS-837 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.0.Alpha1-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > > *Reason:* Sync w/ 4.4.1.AM3 > *Project page/sources:* > *Version:* .4.4.0.Alpha2 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* IS > *Include in JBDS:* Yes (IS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > < org.jboss.tools.project.examples.feature.feature.group [3.1.1.v20160614-2134] > < org.jboss.tools.project.examples [3.1.1.v20160614-2134] > < org.jboss.tools.project.examples.feature.feature.jar [3.1.1.v20160614-2134] > > org.jboss.tools.project.examples.feature.feature.group [3.1.1.v20160812-0234] > > org.jboss.tools.project.examples [3.1.1.v20160812-0234] > > org.jboss.tools.project.examples.feature.feature.jar [3.1.1.v20160812-0234] > === Summary === > file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 3 unique IUs > file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 3 unique IUs > < org.jboss.tools.project.examples.feature.feature.jar [3.1.1.v20160614-2134] > < org.jboss.tools.project.examples.feature.feature.group [3.1.1.v20160614-2134] > < org.jboss.tools.project.examples [3.1.1.v20160614-2134] > > org.jboss.tools.project.examples [3.1.1.v20160812-0234] > > org.jboss.tools.project.examples.feature.feature.jar [3.1.1.v20160812-0234] > > org.jboss.tools.project.examples.feature.feature.group [3.1.1.v20160812-0234] > === Summary === > file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 3 unique IUs > file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 3 unique IUs > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20362) Extracting of a download runtime is slow on Mac

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20362?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20362: ------------------------------------- [~mmalina] Ok... I'm, not gonna say "you're crazy!", even if I'm thinking it... ... but If you look at my changes, they are 100% UI only. I think it's extremely unlikely (almost unthinkable really) that changes to our UI is what's causing this. But let's think about this. What could possibly be causing your download speed to slow down? 1) Is the label reporting 2.3mb/s? or is the label reporting 20mb but behaving as if it's 2.3mb/s? 2) If the label is REPORTING 2.3mb/sec, then it means the actual download speed is 2.3mb/sec and it's not just a slow UI that's having trouble updating. If the label is listing it as 20mb but it's just slow, then that's a UI issue clearly. 3) Progress monitor work is almost always done asynchronously... at least when it comes to UI, and the UI is by far the slowest part. Question is, is it done asynchronously so it's not blocking the actual download? I'll need to check, but I can't see how it would be. Tests: With patch: new server wizard: consistant 6mb/s... preference page: also 6mb/s - 3 attempts each Without patch: new server wizard: consistant 6mb/s... preference page: also 6mb/s - 3 attempts each Basically, what's changed here is that we still update the progress monitor in 100% exactly the same way as before, we've just changed which root progress monitor is being used. The root progress monitor being used now will only fire Display.asynch swt updates less frequently. I believe there is another layer of progress monitor delegation, but this happens all the time any time someone makes a subprogress monitor or a wrapped progress monitor, which happens seriously all the time. So one extra layer of progress monitor passing shouldn't affect download speed at all, especially not on the order of 90% speed drop. It's almost unheard of. [~fbricon] Can you test this patch? It'd be really helpful to get another data point. I'm not noticing any slowdown. > Extracting of a download runtime is slow on Mac > ----------------------------------------------- > > Key: JBIDE-20362 > URL: https://issues.jboss.org/browse/JBIDE-20362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > While playing with the Download runtime fuctionality, I noticed that once a runtime (e.g. EAP 6.2) is downloaded, the extraction takes very long. I think it used to be fast and the extraction was done without any progress reporting. But now it seems that every subdirectory in the archive is being printed out which slows it down. > This extraction process took 1 min 23 sec for EAP 6.2 and I have an SSD. On a command line, this would take a few seconds. > I think the solution may be to simply show "Extracting" without printing out each file/directory that is being extracted. > (Furthermore, the progress bar does not reflect the progress - it seems there is still only perhaps 5 % done and then it's suddenly over.) > I can record a screencast if you like, but I think this should be easy to replicate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4007) Need a new check for existing OpenJDK installed as an msi package

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4007?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4007: -------------------------------- Fix Version/s: 10.1.0.GA > Need a new check for existing OpenJDK installed as an msi package > ----------------------------------------------------------------- > > Key: JBDS-4007 > URL: https://issues.jboss.org/browse/JBDS-4007 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > > Now that OpenJDK is being installed using the msi installer, a new possible issue has arisen: > Basically it's the same problem we had with Vagrant and Virtualbox - one cannot simply try to reinstall msi package into a different folder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 August 2016