Support #356
Maven app-assemble targets are installed in $prefix/opt
| Status: | Resolved | Start date: | 2014-12-19 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Johannes Wienke | % Done: | 0% | |
| Category: | build-generator | Spent time: | - | |
| Target version: | Toolkit 0.1 |
Description
Is there any reason for this? Because of this configuration, we need to softlink from
/opt/$component/bin/$target to $prefix/bin/$target...if we would like to have the $component/bin in the std. $PATH.
History
#1
Updated by Florian Lier over 9 years ago
- Subject changed from Maven app-assemble target are installed in $prefix/opt to Maven app-assemble targets are installed in $prefix/opt
#2
Updated by Johannes Wienke over 9 years ago
- Status changed from New to Rejected
This is on purpose! There are no real conventions for directory structures created with app assembler and something like a shared prefix concept does not exist there. Simply putting all things into a common prefix is therefore likely to end in troubles. E.g. appassembler scripts often destroyed the local maven repository in the prefix folder because for some software packages the appassembler jar location was configured to the same subdirectory.
#3
Updated by Florian Lier over 9 years ago
- Status changed from Rejected to Resolved
Okay, I see and now remember. So we probably need to fix this in every component using the app-assemble step.
1) use a post-build command which does the softlinking
2) create a job per distribution which creates all according softlinks
#4
Updated by Johannes Wienke over 9 years ago
Or just live with the situation since in most scenarios vdemo should be used anyway ;)
#5
Updated by Florian Lier over 9 years ago
At Bielefeld, yes, but not in the scope of "general" reproducibility.