Bugzilla – Full Text Bug Listing
| Summary: | Update to Spring 4.2.x | ||
|---|---|---|---|
| Product: | [RT] Gemini.Blueprint | Reporter: | Olaf Otto <olaf> |
| Component: | Core | Assignee: | Olaf Otto <olaf> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | infiniteuniverse, richardfearn |
| Version: | 2.0.0 RELEASE | ||
| Target Milestone: | 2.0.0.M04 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 393961 | ||
|
Description
Olaf Otto
I've analyzed the current situation (master branch). Migrating to Spring 4 has a number of side effects, all of which apparently where addressed concurrently: - Various POM changes, including transitive dependencies - A wider range of API change adaptations in core and extender - Replacement of obsolete classes removed from Spring 4, such as the TimerTaskExecutor - Re-write of the integration test as the deprecated Spring 3 test infrastructure is no longer present in Spring 4. The latter change - re-writing the integration tests - is the crux of the matter. Here, two changes - to the integration framework itself and the Spring version - happen in parallel. Resulting, it is almost impossible to diagnose whether integration test failures - of which there are, unfortunately, quite a few on the master branch - represent actual issues introduced by the usage of Spring 4 or whether they are rooted in changes to the integration test framework itself. This, I believe, accounts for the delay in shipping a 2.0.0 release for the current Spring 4 version. I have thus branched from rev. 5c50c38, at a point where the integration tests are not migrated and all integration tests passed. Subsequently, I have introduced Spring 4 in a step-by-step manner. Finally, instead of re-writing the integration testing framework, I have provided the legacy Spring test infrastructure as part of the integration testing framework. This way, The Spring version update and the re-write of the integration testing framework can be addressed separately. The corresponding changes are available at https://github.com/olaf-otto/gemini.blueprint/tree/488009-migrate-to-spring-4.2.4 - this is a version of gemini-blueprint with Spring 4.2.4 with passing integration tests (felix, knopflerfish, equinox). I will now create a pull request to the official gemini-blueprint project mirror at GitHub. Fixed for 2.0.0 (rev fc6f51d3f7477c3d4467541fa67687f565a6b4a2) *** Bug 484827 has been marked as a duplicate of this bug. *** *** Bug 439713 has been marked as a duplicate of this bug. *** Released - closing this bug. |