|-Doomph.p2.pool argument [message #1801098]
||Sun, 13 January 2019 21:19
| Mario Jauvin
Registered: October 2015
I read the Oomph authoring page, the corresponding bugzilla and looked at the code and do not understand the purpose of the option. Here is what I have noticed:|
If I start with the value set to @none the ability to select/change the bundle pool disappears from both the simple and advanced mode UI.
If I set the option to a path containing a bundle pool, the oomph.p2.pool system property will be overwritten to the value of the defaults.info file there fore ignoring the passed value.
Here are my questions:
- Is there any change in how oomph works when @none is specified (except for the UI difference), i.e. will the bundle pool specified in defaults.info be used and added to when required as usual?
- What is the purpose of setting the value to a file path corresponding to a bundle pool?
As usual, thanks for the replies.
[Updated on: Sun, 13 January 2019 21:21]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01771 seconds