| Unnecessary unpacking of platform fragments if not used [message #1835854] |
Tue, 15 December 2020 09:31  |
 Guido Schnepp
Messages: 15
Registered: March 2013 |
Junior Member |
|
|
Hi there,
I have a feeling not to be right here, but I have to start to ask somewhere...
I'm creating two products using Tycho 2.1.0 and tycho-p2-director-plugin. Both products are identical except the JustJ feature added to "ProductX" but left out on "ProductX.noJRE". It generates one repository and two product folders as desired. Repository contains the JustJ feature in features/ folder and a fragment plugin in plugins/ folder. So far so good, but...
Generated products have the JustJ feature copied to ProductX/features/ but not copied to ProductX.noJRE/features/, as desired. From here the problems begin:
- Both folders, ProductX/plugins and ProductX.noJRE/plugins, get an unpacked version of the fragment plugin (<unpack> is not set in JustJ feature so I assume a 'true' default setting). But why does *.noJRE get the fragment plugin at all, if the feature itself is not included? That's the more interesting question. Is it a problem of the p2-director-plugin to touch features even if they are not contained in the later build?
- Both ProductX.ini files now contain a -vm parameter pointing to the unpacked fragment plugin. While this is self-consistent, it doesn't make sense for the noJRE case, right? The ProductX.noJRE build doesn't contain the feature, so shouldn't contain the depending fragment and should not get the -vm option into its INI file. That's how it should look like!
Do you have an opinion on this? Is this a bug to be addressed with the p2-director-plugin or is it a JustJ configuration problem itself? Many thanks in advance.
Regards
Guido
[Updated on: Tue, 15 December 2020 09:31] Report message to a moderator |
|
|
|
|
Powered by
FUDForum. Page generated in 0.03975 seconds
] 
Search
Help
Register
Login
Home
