|
|
| Re: Filtering setup file 'requirement' by Eclipse release (Neon/4.6) [message #1771093 is a reply to message #1770975] |
Mon, 21 August 2017 20:50   |
 John Ruud
Messages: 17
Registered: July 2009 |
Junior Member |
|
|
Thanks Ed, that sounds like a promising approach. However, I've never been able to get 'optional' to work, as optional features always appear to be ignored (regardless of greedyness). I must be doing something wrong somehow, unless this is a recent regression.
Trying again with Neon.3 and Oxygen, the following requirement appears to be completely ignored (there is nothing interesting logged to the Eclipse error log or to the setup.log):
<requirement
name="my.feature.group"
versionRange="[3.0.0,4.0.0)"
optional="true"/>
However, after making the requirement required, the feature will install just fine into Oxygen, and will fail under Mars (as expected, due to unfulfilled requirements).
<requirement
name="my.feature.group"
versionRange="[3.0.0,4.0.0)"/>
|
|
|
|
| Re: Filtering setup file 'requirement' by Eclipse release (Neon/4.6) [message #1771202 is a reply to message #1771109] |
Tue, 22 August 2017 21:01 |
John Ruud
Messages: 17
Registered: July 2009 |
Junior Member |
|
|
Yes, it seems unlikely that optional requirements would be broken in p2. I'm assuming that when you talk about greedy, it's in regard to the p2 configuration (p2.inf, or something similar), and not in the oomph setup file, where greedy=true is the default.
I can file an Oomph bug report for this, but would like to check if the following is supposed to work first. I added the following requirement only to an Eclipse Oxygen oomph setup file, for example to installation.setup:
<requirement
name="org.eclipse.cvs.feature.group"
versionRange="[1.4.0,2.0.0)"
optional="true"/>
However, the CVS plugin wasn't installed after restarting Eclipse, and there are no errors logged anywhere AFAIK. 'greedy="true"' should be the default for oomph requirements, while I tried explicitly adding that as well (to no avail).
On the other hand, the following non-optional requirement will install w/o problems:
<requirement
name="org.eclipse.cvs.feature.group"
versionRange="[1.4.0,2.0.0)"/>
Is there some p2 greedy setting that would need to be configured for the Eclipse (CVS plugin) update site as well, in order for the oomph 'optional' requirement to work? I chose the CVS plugin example because it's a common plugin hosted by Eclipse.
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05180 seconds
] 
Search
Help
Register
Login
Home
