October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21036) Infinite cycle in ParametedType.isAssignableTo()

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21036?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21036: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > Infinite cycle in ParametedType.isAssignableTo() > ------------------------------------------------ > > Key: JBIDE-21036 > URL: https://issues.jboss.org/browse/JBIDE-21036 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.3.0.Final > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > java.lang.StackOverflowError is reported in > http://stackoverflow.com/questions/33301776/an-internal-error-occurred-du... > Infinitely cycling calls are > org.jboss.tools.common.java.ParametedType.isAssignableTo(ParametedType.java:398) at org.jboss.tools.common.java.ParametedType.isAssignableTo(ParametedType.java:402) at org.jboss.tools.common.java.ParametedType.areTypeParametersAssignableTo(ParametedType.java:430) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21036) Infinite cycle in ParametedType.isAssignableTo()

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-21036: --------------------------------------------- Summary: Infinite cycle in ParametedType.isAssignableTo() Key: JBIDE-21036 URL: https://issues.jboss.org/browse/JBIDE-21036 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Affects Versions: 4.3.0.Final Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.3.1.Beta1 java.lang.StackOverflowError is reported in http://stackoverflow.com/questions/33301776/an-internal-error-occurred-du... Infinitely cycling calls are org.jboss.tools.common.java.ParametedType.isAssignableTo(ParametedType.java:398) at org.jboss.tools.common.java.ParametedType.isAssignableTo(ParametedType.java:402) at org.jboss.tools.common.java.ParametedType.areTypeParametersAssignableTo(ParametedType.java:430) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21033) Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21033?page=com.atlassian.jira.plugi... ] Len DiMaggio resolved JBIDE-21033. ---------------------------------- Fix Version/s: 4.3.0.Final Resolution: Done > Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test > --------------------------------------------------- > > Key: JBIDE-21033 > URL: https://issues.jboss.org/browse/JBIDE-21033 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3554 at 10/30/15 4:09 PM: ------------------------------------------------------------ PRs merged. Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... >= 465 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_ma... >= 4107 was (Author: nickboldt): PRs merged. Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... >= 465 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_ma... >= 4106 > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > Attachments: p2diff.log.txt > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > [^p2diff.log.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-3553. ------------------------------ Resolution: Done PRs merged. Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... >= 465 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >= 131 > Integrate/Enable CodeRecommenders substring completion in JBDS 9 > ---------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: new_and_noteworthy > Fix For: 9.1.0.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > mistria@mistria-laptop:~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64$ ./p2diff http://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.51.0.Fina... file:/home/mistria/git/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ > > org.eclipse.recommenders.jdt [2.2.4.v20150914-0857] > > org.eclipse.recommenders.overrides [2.2.4.v20150914-0857] > > org.eclipse.recommenders.injection [2.2.4.v20150914-0857] > > org.eclipse.aether.maven.feature.feature.group [3.1.0.20140706-2237] > > org.eclipse.aether.transport.http [1.0.1.v20141111] > > org.eclipse.aether.api [1.0.1.v20141111] > > org.eclipse.aether.transport.http.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.aether.transport.file.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.recommenders.overrides.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.utils [2.2.4.v20150914-0857] > > org.eclipse.aether.connector.basic.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.aether.spi [1.0.1.v20141111] > > com.google.inject.multibindings [3.0.0.v201402270930] > > org.eclipse.recommenders.completion.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.maven.feature.feature.jar [3.1.0.20140706-2237] > > org.apache.commons.lang3 [3.1.0.v201403281430] > > org.eclipse.aether.feature.feature.group [1.0.1.v20141111] > > org.eclipse.recommenders.types.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.calls.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.connector.basic.feature.feature.group [1.0.1.v20141111] > > org.apache.commons.pool [1.6.0.v201204271246] > > org.eclipse.aether.maven [3.1.0.v20140706-2237] > > org.eclipse.recommenders.models [2.2.4.v20150914-0857] > > org.eclipse.recommenders.jayes [2.2.4.v20150914-0857] > > org.eclipse.aether.transport.file [1.0.1.v20141111] > > org.apache.commons.math [2.1.0.v201105210652] > > org.eclipse.recommenders.coordinates [2.2.4.v20150914-0857] > > org.eclipse.recommenders.subwords.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.models.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.transport.http.feature.feature.group [1.0.1.v20141111] > > org.eclipse.recommenders.chain.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.apidocs [2.2.4.v20150914-0857] > > org.eclipse.recommenders.rcp.feature.feature.jar [2.2.4.v20150914-0857] > > org.eclipse.recommenders.constructors [2.2.4.v20150914-0857] > > org.eclipse.recommenders.calls [2.2.4.v20150914-0857] > > org.apache.solr.client.solrj [3.5.0.v20150506-0844] > > org.eclipse.aether.impl [1.0.1.v20141111] > > org.eclipse.recommenders.jayes.io [2.2.4.v20150914-0857] > > com.google.inject [3.0.0.v201312141243] > > org.eclipse.aether.connector.basic [1.0.1.v20141111] > > ch.qos.logback.slf4j [1.0.7.v201505121915] > > org.eclipse.aether.util [1.0.1.v20141111] > > org.eclipse.recommenders.utils.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.net [2.2.4.v20150914-0857] > > org.eclipse.recommenders.constructors.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.feature.feature.jar [1.0.1.v20141111] > > org.eclipse.recommenders.rcp [2.2.4.v20150914-0857] > > org.eclipse.recommenders.apidocs.rcp [2.2.4.v20150914-0857] > > org.eclipse.aether.transport.file.feature.feature.group [1.0.1.v20141111] > > org.eclipse.recommenders.rcp.feature.feature.group [2.2.4.v20150914-0857] > > org.eclipse.recommenders.coordinates.rcp [2.2.4.v20150914-0857] > === Summary === > file:/home/mistria/git/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ contains 51 unique IUs > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-3554. ------------------------------ Resolution: Done PRs merged. Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... >= 465 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_ma... >= 4106 > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > Attachments: p2diff.log.txt > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > [^p2diff.log.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21030) Use newer Easymport (update Neon TP)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21030?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-21030. -------------------------------- Resolution: Done PR merged. Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... >= 465 > Use newer Easymport (update Neon TP) > ------------------------------------ > > Key: JBIDE-21030 > URL: https://issues.jboss.org/browse/JBIDE-21030 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20... > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-508: ---------------------------------- Luna now updated - I think we're done with this Jira. The working URLs after updating the IS are clean. https://github.com/jbosstools/jbosstools-download.jboss.org/commit/78646f... https://github.com/jbdevstudio/jbdevstudio-website/commit/5663364be88cb88... > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20842) Need to implement npm support

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20842?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20842: ----------------------------------- Description: Initially npm support should include the following commands: 1) [init|https://docs.npmjs.com/cli/init] - package.json creation 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder See a short demo: https://vimeo.com/143263045 was: Initially npm support should include the following commands: 1) [init|https://docs.npmjs.com/cli/init] - package.json creation 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder > Need to implement npm support > ----------------------------- > > Key: JBIDE-20842 > URL: https://issues.jboss.org/browse/JBIDE-20842 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Initially npm support should include the following commands: > 1) [init|https://docs.npmjs.com/cli/init] - package.json creation > 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version > 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder > See a short demo: https://vimeo.com/143263045 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-20845: --------------------------------------- See http://screencast.com/t/vNYWg1Bps > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png, lineNumber.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 October 2015