[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cross-project-issues-dev] [orbit-dev] [eclipse.org-planning-council] Neon.3 Update Problems
- From: Ed Willink <ed@xxxxxxxxxxxxx>
- Date: Fri, 31 Mar 2017 08:29:34 +0100
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
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.
On 30/03/2017 21:20, Carsten Reckord wrote:
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  that would have certainly helped with the httpclient 4.3 and 4.5 bundle version mix that we had in Oxygen.
I think there is also another thing to consider. IMHO projects should
hard-pinning specific 3rd party versions in the feature.xml
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
This email has been checked for viruses by Avast antivirus software.