I've just committed a change that uses asserts in the sources.
Users of IntelliJ have to manually change the language level of the
jackrabbit project to 1.4. It seems that the idea maven plugin does not
take the maven.compile.source=1.4 property into account when generating
a project file :-/
regards
marcel
Marcel Reutegger wrote:
hi all,
I'm currently working on an improvement regarding memory consumption in
jackrabbit (replace reference map for listener in item states with a
more light weight collection class). doing that, I would like to use the
java 1.4 assert facility to include preconditions that make sure a
listener is only registered once. that way I don't have to check every
time if a listener is already registered.
using 1.4 asserts would required the '-source 1.4' switch when compiling
jackrabbit. our maven project.properties already adds that switch. so,
there would be nothing to do on our side. but probably a comment in
documentation that talks about this.
per default asserts are disabled and will not impact performance.
when running the unit tests, asserts would then be enabled using the -ea
switch for the test run.
what's the general feeling about this?
regards
marcel
