Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 484827

Summary: Upgrade Gemini Blueprint To Support Sprint 4.2.x
Product: [RT] Gemini.Blueprint Reporter: infinite universe <infiniteuniverse>
Component: CoreAssignee: Project Inbox <gemini.blueprint-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: fwaibel, olaf, t.dewolf
Version: 2.0.0 RELEASE   
Target Milestone: 2.0.0.M04   
Hardware: PC   
OS: Mac OS X   
Whiteboard:
Bug Depends on:    
Bug Blocks: 393961    
Attachments:
Description Flags
Patch to support service mix spring release 4.2.2.RELEASE_1 none

Description infinite universe CLA 2015-12-22 21:52:35 EST
Created attachment 258859 [details]
Patch to support service mix spring release 4.2.2.RELEASE_1

Please upgrade gemini blueprint to support spring 4.2.x by removing dependency on removed deprecated APIs. Attached is a patch I created to support it locally. You may also want to consider decreasing the upper bound spring support to a minor version to allow more precise version selection when multiple version of spring are available in an environment, but the supplied patch does not do that.
Comment 1 Florian Waibel CLA 2015-12-23 05:35:27 EST
Thanks for you contribution. Did you already sign the Contributor License Agreement[1]? Just in case you are not familiar with this procedure there is a nice FAQ[2] available.

[1] https://eclipse.org/legal/CLA.php
[2] https://eclipse.org/legal/clafaq.php
Comment 2 infinite universe CLA 2015-12-23 09:34:28 EST
No I haven't signed the agreement yet, I need to get formal approval from my employer before I do that, I've submitted the paperwork there. Additionally my personal information is redacted from the patch I originally attached, will I need to supply one with my correct personal information for the CLA agreement?
Comment 3 Olaf Otto CLA 2016-04-28 07:39:26 EDT
Spring 4.2.x is now supported (see 488009)
Comment 4 Olaf Otto CLA 2016-04-28 07:39:58 EDT

*** This bug has been marked as a duplicate of bug 488009 ***