Eclipse Community Forums: ServerTools (WTP) » JSDT Extension: how to filter Project path dynamically?

Home » Language IDEs » ServerTools (WTP) » JSDT Extension: how to filter Project path dynamically?(Now to separate Javascript files and Libraries dynamically if one project contains both client side and server side javascripts )

Show: Today's Messages :: Show Polls :: Message Navigator

JSDT Extension: how to filter Project path dynamically? [message #1179843]

Sun, 10 November 2013 15:41

Pavel Sosin

Messages: 2
Registered: November 2013

Junior Member

In our environment JavaScript is used for both client side and server side development. To distinguish between client side and server-side JavaScript the new "server side" content types (file extension) are defined via JSDT extension point org.eclipse.wst.jsdt.core.jsSource. It caused the problem of cross content type visibility in code completion: variables and functions are visible regardless the file type. The same problem exists also for Libraries: content of Client side and Server side libraries is always visible when either client side or server side script is edited. Is it possible to separate visibility of JavaScript artifacts for CodeCompletionRobot according the Project Path using, for example, org.eclipse.wst.jsdt.core.sourcePathProvider extension point?

Report message to a moderator

Re: JSDT Extension: how to filter Project path dynamically? [message #1385887 is a reply to message #1179843]

Thu, 12 June 2014 05:44

Paul Verest

Messages: 36
Registered: March 2013

Member

up (could not answer before because of https://bugs.eclipse.org/bugs/show_bug.cgi?id=422039)

Report message to a moderator

Re: JSDT Extension: how to filter Project path dynamically? [message #1385888 is a reply to message #1385887]

Thu, 12 June 2014 05:50

Paul Verest

Messages: 36
Registered: March 2013

Member

up from IE

Report message to a moderator

Re: JSDT Extension: how to filter Project path dynamically? [message #1386746 is a reply to message #1385888]

Fri, 20 June 2014 04:33

Nitin Dahyabhai

Messages: 4435
Registered: July 2009

Senior Member

No, that's not what that extension point is for (it's internal, and meant to aid in defining source folders when the JS facet is installed). The entire project operates using a single Include Path. Project entries are meant to help compose larger applications or structure these kinds of divisions.

_
Nitin Dahyabhai
Eclipse Web Tools Platform

Report message to a moderator

Previous Topic:	The content type in preference page can't change the default encoding?
Next Topic:	HTML and XML Editor Formatting strategies

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 22:54:47 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter