eclipse-cbi/targetplatform-dsl

TPD validator seems to use workspace relative paths for includes

Opened this issue · 0 comments

In the following folder structure, where "projectFolder" is imported to the workspace and "anyFolder" is there on disk, but not visible in Eclipse:

root
projectFolder1
tpd1
anyFolder
projectFolder2
tpd2

If you include tpd1 from tpd2:

  1. The validation in the editor tells you that ../projectFolder/tpd1 is correct and ../../projectFolder1/tpd1 shows a failure
  2. When running the .target creation, it only works with ../../projectFolder1/tpd1 (which was marked as wrong in the editor)

I guess that the editor uses a workspaces-based resolvement of includes, while the generations uses a file system based.