|
If you were logged in you would be able to see more operations.
|
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
Happens on Windows and Linux. JDK 6u5.
|
|
Issue Links:
|
Duplicate
|
|
|
|
This issue is duplicated by:
|
|
IDEA-18033
Test Output path only uses module var...
|
|
|
|
|
|
| Build: |
7,757
|
| Fixed in build: |
7,903
|
| Severity: |
High
|
|
Starting with IDEA 7.0.3, this problem has appeared: When creating a shared run/debug configuration that has a VM_PARAMETERS value like "-Djava.library.path=/path/to/project/dir/lib" (needed for picking up native libs when using JNI), the value that is stored in the .ipr is the verbatim absolute path instead of the expected parametrized path, i.e., "-Djava.library.path=$PROJECT_DIR$/lib". This still worked correctly in IDEA 7.0.2. Without the parametrization, the .ipr can no longer be shared among developers without local edits.
|
|
Description
|
Starting with IDEA 7.0.3, this problem has appeared: When creating a shared run/debug configuration that has a VM_PARAMETERS value like "-Djava.library.path=/path/to/project/dir/lib" (needed for picking up native libs when using JNI), the value that is stored in the .ipr is the verbatim absolute path instead of the expected parametrized path, i.e., "-Djava.library.path=$PROJECT_DIR$/lib". This still worked correctly in IDEA 7.0.2. Without the parametrization, the .ipr can no longer be shared among developers without local edits. |
Show » |
|
Bug
Normal
IDEA 7.0.3 no longer uses $PROJECT_DIR$ in .ipr for paths in VM_PARAMETERS in run/debug configuration