Importing jars and and absolute path issues
This issues bugs me for a long time.
When I import a jar into MPS project, the system stores absolute path to it. Even if the jar resides in the same folder as my poject.
Of course this causes issues, when project is used on different computer. My current solution is to define path variable pointing to the root of my project.
As number of projects grow, so does the number of variables. It's already messy, and will become even more over time.
The question is - how to setup my project correctly, avoiding path variables? Is there a "best practice" for this in MPS team?
When I import a jar into MPS project, the system stores absolute path to it. Even if the jar resides in the same folder as my poject.
Of course this causes issues, when project is used on different computer. My current solution is to define path variable pointing to the root of my project.
As number of projects grow, so does the number of variables. It's already messy, and will become even more over time.
The question is - how to setup my project correctly, avoiding path variables? Is there a "best practice" for this in MPS team?
1 comment
Sort by
Date
Votes
You have to put your *.jar file next to the *.mpl file of the importing module as described in these threads:
- Where to place external libraries
- Best practices for using Java libs
Please sign in to leave a comment.