[MAGNOLIA-555] Extract AbstractProvider from Jackrabbit ProviderImpl, new Jeceira Provider Created: 22/Sep/05 Updated: 10/Jan/14 Resolved: 10/Jan/14 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 2.1 Final |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Trivial |
| Reporter: | Andreas Brenk | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Revision 1476: /magnolia/trunk |
||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
To ease the creation of new Repository Providers I refactored the existing Jackrabbit ProviderImpl and pulled up an abstract AbstractProvider. As a first new Provider I created a Jeceira (http://www.jeceira.com/) ProviderImpl (based on http://wiki.aparzev.com/confluence/display/JCR/Magnolia) Also, a new jeceira dependency has to be appended to build/test dependencies in project.xml: <dependency> Also I'd like to propose to move the Jackrabbit implementation from info.magnolia.jackrabbit to info.magnolia.repository.jackrabbit some time in the future. |
| Comments |
| Comment by Andreas Brenk [ 22/Sep/05 ] |
|
Here's the new code / patch. |
| Comment by Philipp Bracher [ 17/May/06 ] |
|
Is this something we do in 3.0? |
| Comment by Magnolia International [ 10/Jan/14 ] |
|
While this is possibly still a concern, the real fix will be to extract ProviderImpl out of core, anyway. |