Following onto my email from last week regarding the outstanding issues for the API 2.1.0 release, I wanted to send a similar email about the various JCR related bundles. Here the story is more complex and I think we need to push some of these issues into a later release.
Issues which appear to resolved: SLING-1566 - adding ResourceResolver.isLive() - as I mentioned, this looks like it can be marked as Resolved (Felix?) SLING-1132 - wrong bundle version Doc Required: SLING-1519 - URL mapping for paths containing "-" Issues for which patches are available: SLING-1548 - move bundle event handling to Loader SLING-1463 - use OSGi events instead of JCR events for MapEntries SLING-1198 - Allow mapping nodes to internet domains with template parameters Issues I think we can move out of the next release cycle: SLING-1455 - Impossible to refer to same-name-siblings when doing internal redirect to another protocol SLING-1421 - Resorce Resolver Mapping - Better Support for Multiple Domain/Protocol Mapping SLING-1391 - Make JcrModifiablePropertyMap write changes directly SLING-1332 - Support multi-value sling:alias resolution here's the JIRA query: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310710&fixfor=12314772&fixfor=12314758&fixfor=12314415&fixfor=12314472&fixfor=12314286&fixfor=12314773&fixfor=12314769&fixfor=12314442&fixfor=12314774&fixfor=12313431&fixfor=12314768&fixfor=12314564&resolution=-1&sorter/field=issuekey&sorter/order=DESC Also worth looking at is this query: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310710&component=12311946&fixfor=-1&resolution=-1&sorter/field=issuekey&sorter/order=DESC This is the issues marked with the JCR component but no Fix Version. Justin
