May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-188) javascript include path not excluding folders from validaton [EBZ#489461]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-188: --------------------------------------- Summary: javascript include path not excluding folders from validaton [EBZ#489461] Key: ERT-188 URL: https://issues.jboss.org/browse/ERT-188 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Fix For: Neon (4.6) M7 Going to Project Properties > Javascript > Include Path, selecting the Source tab and adding folders to exclude is not working in Neon Milestone 4 (4.6.0M5). Errors from the folders I've set to exclude are still present. I've done the exact same thing in Luna and it worked as expected. Thanks all for the great work! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-189) Plugins need to comply with the Eclipse licensing guidelines - about required [EBZ#493168]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-189: --------------------------------------- Summary: Plugins need to comply with the Eclipse licensing guidelines - about required [EBZ#493168] Key: ERT-189 URL: https://issues.jboss.org/browse/ERT-189 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Priority: Blocker Fix For: Neon (4.6) RC1 [About missing] License consistency is required for the next plugins: [JSDT] org.eclipse.wst.jsdt.chromium_0.4.0.v201603211918.jar org.eclipse.wst.jsdt.chromium.debug_0.4.0.v201603211918.jar org.eclipse.wst.jsdt.chromium.debug.core_0.4.0.v201604282302.jar org.eclipse.wst.jsdt.chromium.debug.jsdtbridge_0.4.0.v201603211918.jar org.eclipse.wst.jsdt.chromium.debug.ui_0.4.0.v201604120226.jar org.eclipse.wst.jsdt.chromium.wip.eclipse_0.4.0.v201603211918.jar org.eclipse.wst.jsdt.chromium.wipbackend.dev_0.4.0.v201603211918.jar org.eclipse.wst.jsdt.chromium.wipbackend.protocol_1_0_0.4.0.v201603211918.jar org.eclipse.wst.jsdt.js.bower_1.0.0.v201602281542.jar org.eclipse.wst.jsdt.js.cli_1.0.0.v201602051019.jar org.eclipse.wst.jsdt.js.common_1.0.0.v201602231538.jar org.eclipse.wst.jsdt.js.grunt_1.0.0.v201604122023.jar org.eclipse.wst.jsdt.js.gulp_1.0.0.v201604122023.jar org.eclipse.wst.jsdt.js.node_1.0.0.v201604282302.jar org.eclipse.wst.jsdt.js.node.common_1.0.0.v201603162320.jar org.eclipse.wst.jsdt.js.npm_1.0.0.v201603041148.jar org.eclipse.wst.jsdt.nashorn.extension_1.0.0.v201603252255.jar org.eclipse.wst.json.bower.core_1.0.0.v201602251339.jar -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-190) JSON Editor icons [EBZ#493364]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-190: --------------------------------------- Summary: JSON Editor icons [EBZ#493364] Key: ERT-190 URL: https://issues.jboss.org/browse/ERT-190 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Friendly Jira Robot Created attachment 261611 new set of png icons including xcf source and png result The set of icons proposed for JSON Editor's elements. XCF Source for new images - editable with GIMP, the source for the new iconset, so it will be easy to make minor changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-191) ClassCastException from KeywordCompletionProposalComputer & IdentifierCompletionProposalComputer witn Neon M7 [EBZ#493393]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-191: --------------------------------------- Summary: ClassCastException from KeywordCompletionProposalComputer & IdentifierCompletionProposalComputer witn Neon M7 [EBZ#493393] Key: ERT-191 URL: https://issues.jboss.org/browse/ERT-191 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot The Eclipse Neon M7 provides KeywordCompletionProposalComputer & IdentifierCompletionProposalComputer classes which doesn't use "instanceof" to check that the given ContentAssistInvocationContext is a JavaContentAssistInvocationContext: ``` public class IdentifierCompletionProposalComputer implements IJavaCompletionProposalComputer { public List computeCompletionProposals(ContentAssistInvocationContext context, IProgressMonitor monitor) { JavaContentAssistInvocationContext javaContext = (JavaContentAssistInvocationContext) context; ``` It's a big problem for typescript.java which is based on JSDT and which defines TypeScriptContentAssistInvocationContext (see issue at https://github.com/angelozerr/typescript.java/issues/56) So with oEclipse Neon M7, when I do completion with my TypeScriptEditor based on JSDT Edit, I have a popup error with this error ``` java.lang.ClassCastException: ts.eclipse.ide.jsdt.internal.ui.editor.contentassist.TypeScriptContentAssistInvocationContext cannot be cast to org.eclipse.wst.jsdt.ui.text.java.JavaContentAssistInvocationContext at org.eclipse.wst.jsdt.internal.ui.text.java.KeywordCompletionProposalComputer.computeCompletionProposals(KeywordCompletionProposalComputer.java:45) ``` and ``` java.lang.ClassCastException: ts.eclipse.ide.jsdt.internal.ui.editor.contentassist.TypeScriptContentAssistInvocationContext cannot be cast to org.eclipse.wst.jsdt.ui.text.java.JavaContentAssistInvocationContext at org.eclipse.wst.jsdt.internal.ui.text.java.IdentifierCompletionProposalComputer.computeCompletionProposals(IdentifierCompletionProposalComputer.java:49) ``` It should b every cool if you could check that ContentAssistInvocationContext is an instanceof JavaContentAssistInvocationContext: ``` public class IdentifierCompletionProposalComputer implements IJavaCompletionProposalComputer { public List computeCompletionProposals(ContentAssistInvocationContext context, IProgressMonitor monitor) { if (context instanceof JavaContentAssistInvocationContext) { JavaContentAssistInvocationContext javaContext = (JavaContentAssistInvocationContext) context; ``` for : * http://git.eclipse.org/c/jsdt/webtools.jsdt.git/tree/bundles/org.eclipse.... * http://git.eclipse.org/c/jsdt/webtools.jsdt.git/tree/bundles/org.eclipse.... For your infomration, I have created my own TypeScriptContentAssistInvocationContext, because I need IResource and I don't use IJavaCompilationUnit. If http://git.eclipse.org/c/jsdt/webtools.jsdt.git/tree/bundles/org.eclipse.... could just define a getter for the Editor, I think I could use directly JavaContentAssistInvocationContext to retrieve my IResource from the getEditor getter. Hope this issue will be able to fixed for Neon release, otherwise typescript.java will not work with Eclipse Neon release -( (we must desactivate the whole JSDT completions to avoid having those 2 popup errors) Many thanks for your help! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20442) Create SWTBot integration tests for tern related features

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20442?page=com.atlassian.jira.plugi... ] Pavol Srna reassigned JBIDE-20442: ---------------------------------- Assignee: Pavol Srna (was: Denis Golovin) > Create SWTBot integration tests for tern related features > --------------------------------------------------------- > > Key: JBIDE-20442 > URL: https://issues.jboss.org/browse/JBIDE-20442 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Pavol Srna > Priority: Critical > Fix For: 4.3.x > > > There should be set of SWTBot tests that would cover functionality related to tern.java and angularjs-eclipse integration. These tests would simplify migration to new tern.java and angularjs-eclipse releases. > Current process for migration to new version of tern-java/angularjs-eclipse is manual. Steps below describe current approach: > 1. Manual mirroring of latest tern-java/angularjs-eclipse versions to local filesystem; > 2. Build jbosstools-jst with local mirrors and run JUnit tests; > 3. Install latest tern-java and angularjs-eclipse form mirrors done in (1) into JBDS nightly build from master branch (it has open version range for tern features) and restart; > 4. Run manual tests; > 5. If (2) and (3) idenify no problems then local mirrors should be published to http://download.jboss.org/jbosstools/updates/requirements/tern and http://download.jboss.org/jbosstools/updates/requirements/angularjs respectively; > 6. Update jbosstools-jst with new versions for tern-java/angularjs-eclipse and push local branch to upstream > With step 4 implemented as SWT bot tests and automated mirroring for tern-java and angularjs-eclipse (see jenkins job here https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/All/job/jbosstools-...) we can fully automate the process above. > QA also can skip step (1) and just use external p2 repos: > * http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ > * http://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/ > in step (2) by building jbosstools-jst as: > {code}mvn clean install -Dtern.repo.url=http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ -Dhttp://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/{code} > and installing latest versions for step (3). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20442) Create SWTBot integration tests for tern related features

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20442?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-20442: --------------------------------- Story Points: 15 (was: 8) > Create SWTBot integration tests for tern related features > --------------------------------------------------------- > > Key: JBIDE-20442 > URL: https://issues.jboss.org/browse/JBIDE-20442 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.x > > > There should be set of SWTBot tests that would cover functionality related to tern.java and angularjs-eclipse integration. These tests would simplify migration to new tern.java and angularjs-eclipse releases. > Current process for migration to new version of tern-java/angularjs-eclipse is manual. Steps below describe current approach: > 1. Manual mirroring of latest tern-java/angularjs-eclipse versions to local filesystem; > 2. Build jbosstools-jst with local mirrors and run JUnit tests; > 3. Install latest tern-java and angularjs-eclipse form mirrors done in (1) into JBDS nightly build from master branch (it has open version range for tern features) and restart; > 4. Run manual tests; > 5. If (2) and (3) idenify no problems then local mirrors should be published to http://download.jboss.org/jbosstools/updates/requirements/tern and http://download.jboss.org/jbosstools/updates/requirements/angularjs respectively; > 6. Update jbosstools-jst with new versions for tern-java/angularjs-eclipse and push local branch to upstream > With step 4 implemented as SWT bot tests and automated mirroring for tern-java and angularjs-eclipse (see jenkins job here https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/All/job/jbosstools-...) we can fully automate the process above. > QA also can skip step (1) and just use external p2 repos: > * http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ > * http://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/ > in step (2) by building jbosstools-jst as: > {code}mvn clean install -Dtern.repo.url=http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ -Dhttp://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/{code} > and installing latest versions for step (3). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-144) Gulp is not available in the Quick access [EBZ#492124]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-144?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-144: ----------------------------- Sprint: devex #114 May 2016 > Gulp is not available in the Quick access [EBZ#492124] > ------------------------------------------------------ > > Key: ERT-144 > URL: https://issues.jboss.org/browse/ERT-144 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > "Run as Gulp task" is not available via quick access. Basically, selection should be tracked and the following behavior is expected: > - IProject with gulpfile.js (launch default task from gulpfile.js) > - IFile gulpfile.js (default task should be run) > - ITask (run gulp task) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-145) Grunt is not available in the Quick access [EBZ#492125]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-145?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-145: ----------------------------- Sprint: devex #114 May 2016 > Grunt is not available in the Quick access [EBZ#492125] > ------------------------------------------------------- > > Key: ERT-145 > URL: https://issues.jboss.org/browse/ERT-145 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > "Run as Grunt task" is not available via quick access. Basically, selection should be tracked and the following behavior is expected: > - IProject with gruntfile.js (launch default task from gruntfile.js) > - IFile gruntfile.js (default task should be run) > - ITask (run grunt task) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-44) JSON Schema extension for JSON editor [EBZ#485701]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-44?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-44: ---------------------------- Sprint: devex #114 May 2016 > JSON Schema extension for JSON editor [EBZ#485701] > -------------------------------------------------- > > Key: ERT-44 > URL: https://issues.jboss.org/browse/ERT-44 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Max Rydahl Andersen > Labels: bzira, wst.json > > JSON editor should have a generic extension for mapping JSON schemas to files.The extension should allow 3rd parties to contribute a JSON schema and get code assist, validation etc. through JSON editor without introducing a new editor type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-173) Need to find a better solution for npm dependencies content assistant [EBZ#492192]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-173?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-173: ----------------------------- Sprint: (was: devex #114 May 2016) > Need to find a better solution for npm dependencies content assistant [EBZ#492192] > ---------------------------------------------------------------------------------- > > Key: ERT-173 > URL: https://issues.jboss.org/browse/ERT-173 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: bzira, wst.json > > In order to show content assist proposals for npm dependencies a 3rd party web service was used. It was a really problematic due to its unstable work, slowness and a tendency to change an URL for requests and formats of response. > I do believe, we should not provide any content assist for dependencies in case no search pattern is provided (typed in) by a user because of really huge memory requirements and network overload in such case: > - Native "npm search" command fails to list all the available packages on my environment after about 5 minutes of downloading packages > Given this, IMHO, we have not to show *all* available packages in content assistant, but show package list only if at least first letter (or a couple of beginning letters) of package name is typed in by a user. > Also the way to get the proposals itself is also a question: we cannot rely on 3rd party services as they are not enough stable and fast. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016