JCite Version History
JCite 1.13.0
Better
- Can now cite text without the additional surrounding
pre code
markup, or even without any post-processing.
Fixed
- Works with JDK 7 now. Sadly, you now have to specify the source search path separately to JCite using
-J-Djcitesourcepath=...
, and itSystem.exit
s on errors since it cannot use the proper error messager anymore.
JCite 1.12.0
Better
- Can now cite Java code without syntax highlighting.
JCite 1.11.0
Better
- Documented how to extend JCite. Refactored a lot to make this more straightforward.
JCite 1.10.3
Better
- Minor fixes and updates to documentation and build process.
JCite 1.10.2
Better
- Added
-pp/--project-path
option to command-line API. - Improved speed of Excel citing (caches loaded spreadsheets).
- Improved error reporting (by idlsoft).
Fixed
- NPE when logging exceptions.
- Handling of trailing whitespace (by idlsoft).
JCite 1.10.1
Better
- Error values like
#NUM!
are now cited more properly.
Fixed
- Now handles multiple similar options like
strip
correctly. Used to only honour the last one.
JCite 1.10.0
New
- You can now cite file paths and snippets out of plain text and XML/HTML files.
- Switched from Subversion (svn) to Mercurial (hg) for version control.
JCite 1.9.2
Better
- Ant task accepts newline string to use for tripwire database (
tripwireNewLine
).
Fixed
JCite 1.9.1
Better
- Escape HTML entities properly when citing Excel formulas and cell values.
- Updated JExcelAPI to 2.6.4.
- Fixed plain style example.
JCite 1.9
New
- Added support for tripwire databases.
- Added Ant task.
- Added the bash script
bin/jcite
to run JCite from the command line in Linux. - You can specify multiple input paths/patterns. Simply repeat the
-i
switch.
Better
- Errors in citations are now reported with proper file and line information. JCite no longer aborts after the first error, either. Failed citation instructions are left in the file as-is.
- JCite reports the input spec its processing and final statistics unless in quiet mode.
- Using
-o file
no longer fails because no parent folder was specified forfile
(see bug #1708328). - The JavaDoc taglet no longer defaults to verbose mode.
JCite 1.8
New
- Can now format inline blocks (rather than citing them from sources). See the samples page for details.
- Added option to cite Excel formulas only (rather than citing current value + formula). See the Excel page for details.
Better
- The Java source code highlighter now inserts additional spaces in situations where a highlighted and an non-highlighted letter or digit would be adjacent. This works around an Eclipse code formatter quirk.
JCite 1.7
New
- Added option to cite entire class files.
Better
- Excel named ranges always listed in alphabetically ascending order.
JCite 1.6
New
- Split processing logic into central class JCite and multiple JCitelets.
- Added support for loading plugins as instances of
JCiteletProvider
usingsun.misc.Service
. - Added plugin for citing Excel sheets.
- Added citelet for citing plain text/HTML snippets.
Better
- Citation instructions embedded within
pre
andcode
tags now strip both of these tags. More precisely, the inner tag is always stripped and if the next outer tag is apre
tag (without anything intervening), then it is stripped too. - Switched documentation sources from a proprietary solution to Rextile.
JCite 1.5
New
- Recursive folder processing – you can let JCite process source files from entire folder hierarchies in one go.
JCite 1.4
New
- JavaDoc support – you can cite source code within doc comments with the
{
.jcite …}@ tag.
Better
- Inline markers like
/* tag */
are now also recognized as/*tag*/
. This makes source code with inline markers more compact. - The
/**/
tag is automatically recognized as a highlight marker, unless it has been overridden by one of thestrip
(formerlyuse
) oromit
instructions, as injc:temp.MyClass:---- marker; strip
. - JCite does not print its banner when the command-line option
-q
is present.
Changed
- The instruction
use <tag>
has been renamed tostrip <tag>
. - JCite no longer lists the citation markers processed, unless explicitly told to do so using the
-v
command-line option.
Earlier Versions
... were used only by me. I did not keep a version history for them.