Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] [orbit-dev] [eclipse.org-planning-council] Neon.3 Update Problems

Hi

Yes, but I await a Wiki describing how to do this. And I suspect we need some ManifestBuilder enhancements to support it.

The 'uses' constraints is an untested solution. Until all SimRel bundles actually exploit them, we do not know how many platform bugs/enhancements are required to exploit them successfully.

    Regards

        Ed Willink


On 30/03/2017 21:20, Carsten Reckord wrote:
I think there is also another thing to consider. IMHO projects should
stop
hard-pinning specific 3rd party versions in the feature.xml
PS: While we're discussing best practices and rules - should we maybe start requiring projects on the train to have proper package uses constraints for all their bundles? Aside from [1] that would have certainly helped with the httpclient 4.3 and 4.5 bundle version mix that we had in Oxygen.
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



Back to the top