[MGNLFORUM-104] Switch to jcr 2.0 as a requirement Created: 19/Aug/10 Updated: 02/Dec/13 Resolved: 19/Aug/10 |
|
| Status: | Closed |
| Project: | Forum (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.0 ? (rewrite) |
| Type: | Task | Priority: | Major |
| Reporter: | Fabrizio Giustina | Assignee: | Fabrizio Giustina |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
Since we need some changes in nodetypes and some improved query features, the new release of the forum module will switch to jcr 2.0 as a basic requirement. The nodetype registration tasks can now use plain jcr APIs. Unfortunately, we still have to depend on jackrabbit commons for parsing the nodetype xml files (thi means that it should work with any jcr 2.0 compliant repository but it still needs the jackrabbit jars in the classpath). |
| Comments |
| Comment by Fabrizio Giustina [ 19/Aug/10 ] |
|
done |
| Comment by Christoph Meier [ 02/Dec/13 ] |
|
closed, since it was resolved a long time ago |