On 28.11.13 9:06 , Jukka Zitting wrote:
Please vote on releasing this package as Apache Jackrabbit 2.6.5.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.
[x] +1 Release this package as Apache Jackrabbit 2.6.5
Note that
Konrad Windszus created JCR-3701:
Summary: Empty p tag in javadoc of UserManagerImpl leads to
missing note in HTML output
Key: JCR-3701
URL: https://issues.apache.org/jira/browse/JCR-3701
Project:
[
https://issues.apache.org/jira/browse/JCR-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCR-3701:
-
Description:
There is an empty paragraph in the javadoc for the field PARAM_DEFAULT_DEPTH
Hi,
This question has already come up on OAK-190 [1]: how should we proceed
wrt. the upcoming JCR 2.1 specification [2]?
JSR-333 is Proposed Final Draft, which means that it is waiting on the
completion of the RI and TCK. However, it seem Oak 1.0 will arrive
sooner than the final JSR-333
Hi,
I don't think we should have concrete classes in the
org.apache.jackrabbit.oak.api package, unless they are needed in the
API interfaces itself (like the final Type class or the
*exceptions).
In this sense, I'd like to move the AbstractPropertyState elsewhere. I
created [0] for that.
Hi,
what is exactly the distinction between SPI and non-SPI classes? i.e.
classes below oajo.spi.* and those outside?
is the SPI meant to be the PI for plugins and extensibility?
If so, the SPI should contain all those classes that are:
1. public (in the osgi sense)
2. used to implement/extends
