Comments (3)
If I specify the project, then it works:
content-provider "${project_loc:portfolio-product}/name.abuchen.portfolio.product";
Looks to me like the resolution is not done in the context of the project in which the launch configuration resides.
from lcdsl.
Hi,
Variables are the same as can be used with "normal" launch configurations, i.e. project_loc's documentation from the launch configuration dialog: "Returns the absolute file system path of a resource's project. The target resource is the selected resource when no argument is specified, or the resource identified by a workspace relative path.". Thus if no argument given, the current selection in the workspace is used (which is probably not what you want :)).
Right now there is no other way to get to the containing project's location. There is support for "project self" with the "project" keyword toplevel, but that is for something else... Right now, strings (which may contain substitutions) are not processed by LcDsl at all, they are just copied to Eclipse. It would need a dedicated syntax for LcDsl specific variables as opposed to string substitutions...
from lcdsl.
Thanks. The syntax project_loc:portfolio-product
works for me.
from lcdsl.
Related Issues (20)
- How to launch Plug-in Tests? HOT 16
- Cannot add two plugins with same id but different version HOT 10
- new feature: Link to products / features / plugins HOT 3
- Provide default ID for launch config
- new feature: Add required dependencies HOT 3
- Working Sets HOT 1
- Easy access to raw launch configuration file HOT 1
- Missing ignored plugins should not generate a warning
- Updating the Xtext Community Website HOT 3
- NPE with unknown launch types HOT 5
- Missing latest version of org.eclipse.debug.ui.launchview HOT 2
- Startlevels for workspacebundles HOT 6
- Test class not accepting all JUnit5 variants HOT 1
- Support launch type pure JUnit? HOT 1
- Application `[No Application] - Headless Mode` unsupported. - Should be default HOT 1
- regression: CI build hangs at "loading target platform" HOT 3
- Validation for test class is too strict
- Compile error due to using API 11, but 1.8 on classpath HOT 1
- Introduction of variables in lcdsl
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lcdsl.