local paths in run descriptors #315
Comments
I think you misunderstand the purpose of those paths being generated. They exist merely to document the result of the resolution, so that a downstream tool can use it to assemble a product out of the resolved resources. Using relative paths or an indirect protocol would defeat this purpose. Neither Bndtools nor bnd use this information again; we only look at the BSN and version. Therefore I don't believe there is any problem with sharing these files through a VCS. If you agree then please close the bug, otherwise comment further. Many thanks. |
I was under the impression that the user may edit the -runbundles section manually even though it is not recommended, because of the warning visible in the run descriptor editor:
The problem with sharing the file through a VCS is the following: suppose Joe creates a run descriptor, sets up the requirements and once everything's running well commits it to the repository. The file contains Here's my idea for improvement:
|
Okay I start to see the problem, but I don't think the suggested solution will work. Could I ask you to clarify:
Then we won't know which bundles to actually run. The -runrequirements list is not used at runtime.
I think perhaps a better fix would be to output the paths into a separate file under the |
Oh I see, this information needs to be written to the filesystem one way or the other, in order to persist the resolution results across workspace restarts. |
Before I get to the proposed solution, I'd like to state again what the original purpose of the
Is it possible that |
Thanks for your comments Marian. I don't think we could use paths relative to the configured OBRs, because when examining a path later we would not know which OBR is was relative to. As far as I can see, putting this information into a separate file under |
Fixed in commit 4ab500c Fix is as follows: on resolve, a file is created/updated with the name
For example:
|
-runbundles
section of the run descriptor containresolution=file:
entries that contain absolute paths specific to local workspace. This makes it impractical to share those files through a version control system.Maybe it would be possible to use relative paths, or use fake workspace: protocol to make the paths independent of local environment?
The text was updated successfully, but these errors were encountered: