Line feeds [Action Required]
by Randall Hauch
We're wrapping up our final few issues targeted for the 0.4 release,
and one of those (DNA-277) was to fix all of the line terminators in
our files to be just LF. If we don't use the same line terminators,
performing diffs in some tools (including Git) consider the whole file
to be changed. This is something that quite a few other JBoss
projects do, and it simply helps portability across our different
development platforms and tools. Most of the time, we probably won't
even notice the difference.
We changed the Eclipse preferences back in January but were waiting
until the end of a release cycle to change the files. (Please make
sure you're using these preferences and are using Unix-style line
endings.) There actually weren't too many files that needed to be
fixed. But there were some, and I just committed the corrections.
In addition to the Eclipse preferences, we can each modify our
~/.subversion/config file to make the SVN command-line tool ensure
each uploaded file has the proper line endings. There is now a
README_COMMITTERS.txt file under 'trunk/' that describes to make this
change. I'm not sure if the Eclipse Team plugin for SVN automatically
reads these settings, but you can go into Eclipse preferences (under
Team->SVN->Properties Configuration) and import your config file.
Thanks for your cooperation. Best regards,
Randall
14 years, 11 months
JCR TCK unit test status
by Randall Hauch
As mentioned several weeks ago, we've been making tremendous strides
with our JCR implementation. I've attached a screenshot of our TCK
unit test statistics (from last night's run on Hudson). We haven't
even implemented the optional features yet, but we're doing very well
with the Level 1 (90% pass) and Level 2 tests (88% pass).
Note: these results are not from the official TCK, but are merely unit
tests from the Jackrabbit project that reportedly make up part of the
TCK.
Best regards,
Randall
14 years, 11 months
Release plan for the 0.4 release
by Randall Hauch
It's again that time when we need to look at the list of open JIRA
issues that are targeted to be finished before the 0.4 release and
determine whether to finish them or to push them to the next release.
The goal is to release on or before next Thursday, April 30.
The plan is to finish these issues before the release:
http://jira.jboss.org/jira/browse/DNA-282
http://jira.jboss.org/jira/browse/DNA-374
http://jira.jboss.org/jira/browse/DNA-175
http://jira.jboss.org/jira/browse/DNA-58
http://jira.jboss.org/jira/browse/DNA-46
http://jira.jboss.org/jira/browse/DNA-375
http://jira.jboss.org/jira/browse/DNA-376
http://jira.jboss.org/jira/browse/DNA-73
http://jira.jboss.org/jira/browse/DNA-194
http://jira.jboss.org/jira/browse/DNA-343
http://jira.jboss.org/jira/browse/DNA-385
http://jira.jboss.org/jira/browse/DNA-335
http://jira.jboss.org/jira/browse/DNA-366
http://jira.jboss.org/jira/browse/DNA-277
That means that unless there is feedback or additional progress, these
issues will be pushed to the next release:
http://jira.jboss.org/jira/browse/DNA-78 (ESB sequencer)
http://jira.jboss.org/jira/browse/DNA-239 (SVN connector)
http://jira.jboss.org/jira/browse/DNA-240 (SVN connector)
http://jira.jboss.org/jira/browse/DNA-36 (SVN connector)
http://jira.jboss.org/jira/browse/DNA-37 (DB Schema connector)
As always, the latest is in JIRA (https://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hi...
).
This release is not the short release we had intended. We've enhanced
and matured the connector framework, added some great connectors (file
system and JPA/relational), improved other connectors (in-memory,
federation), and improved the whole Graph API. But we've spent the
most time in dramatically enhancing our JCR implementation, and we
have added (among other things) update capability, node type
management, constraints, import/export, and workspace clone. In fact,
we've been using the TCK unit tests (from the Jackrabbit project), and
are actually not that far from JCR Level 1 and Level 2 compliance.
(You can check our nightly progress at )
We won't quite get to Level 1 and 2 compliance by the 0.4 release, but
we think the next short release (or two very short releases) will
provide the last features (search, query, events) required to make DNA
a full-fledged JCR implementation and our "1.0" release.
Best regards,
Randall
15 years
