-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump org.eclipse.equinox.p2.core to 2.12.0 #516
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking on dependencies of the new API, following bundles should enforce new version:
- org.eclipse.equinox.p2.metadata.repository
- org.eclipse.equinox.p2.ui.sdk.scheduler
I won't have time for further changes after my 13 hour day. If you feel they are necessary, you or someone else will need to make such changes. Sorry. |
You shouldn't push a PR after 8 hours day in the first place :-)
Yes, otherwise we may run into issues if people get "partial" p2 updates. I've updated your patch with required changes. |
@@ -74,7 +74,7 @@ Service-Component: | |||
Import-Package: org.bouncycastle.bcpg;version="1.65.0", | |||
org.bouncycastle.openpgp;version="1.65.0", | |||
org.eclipse.core.runtime;common=split;version="[3.5.0,4.0.0)", | |||
org.eclipse.equinox.p2.core;version="[2.8.0,2.9.0)";resolution:=optional, | |||
org.eclipse.equinox.p2.core;version="[2.12.0,2.13.0]";resolution:=optional, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
org.eclipse.equinox.p2.core;version="[2.12.0,2.13.0]"
???
Why do we import same package we provide? Is this something that can be provided by others???
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually the change uses wrong range, was meant to excluding 2.13 but is including.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we import same package we provide? Is this something that can be provided by others???
Importing exported packages is considered good OSGi practice by many:
https://felix.apache.org/documentation/tutorials-examples-and-presentations/apache-felix-osgi-faq.html#import-own-exports
I have not yet seen the necessity of that for Eclipse, but I have also not thought about it in great depth.
Interesting (and unrelated) error on Mac
Shouldn't be the problem caused by this PR. |
@@ -74,7 +74,7 @@ Service-Component: | |||
Import-Package: org.bouncycastle.bcpg;version="1.65.0", | |||
org.bouncycastle.openpgp;version="1.65.0", | |||
org.eclipse.core.runtime;common=split;version="[3.5.0,4.0.0)", | |||
org.eclipse.equinox.p2.core;version="[2.8.0,2.9.0)";resolution:=optional, | |||
org.eclipse.equinox.p2.core;version="[2.12.0,2.13.0]";resolution:=optional, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually the change uses wrong range, was meant to excluding 2.13 but is including.
Something is wrong with API tooling:
|
Fixes #514