Interschema links are now generated using private synonyms where available.
There also have been minor fixes to the parser to support more reserved words which are also allowed PL/SQL names.
Before 3.0.0, only one source directory could be specified.
<configuration> <applicationTitle>project-name</applicationTitle> <sourceDirectory>src/sql</sourceDirectory> <includes>*.sql</includes> <reportOutputDirectory>target/site/apidocs</reportOutputDirectory> </configuration>
These changes are available in 1.5.4
PLDoc and the other projects now offer the ability to save database source code to the file system during processing.
This is especially useful when using CPD or maven-cpd-plugin with XML format output, as the application will automatically generate the corresponding HTML page, with links to the saved source code files.
Previous versions all exited on completion, meaning that they broke any Maven site generation.
Version 0.0.8 fixes this problem
There are new releases of PLDoc and downstream Maven projects.
I found some problems with identifying calls to standalone objects (PROCEDURE and FUNCTIONS); I also encountered problems running the 2 Maven plug-ins, possibly because they were dependent on different versions of PLDoc and PMD.
The response was to issue all 4 Maven projects with aligned core versions:-
PMD - 5.0.3
PLDoc - 1.3.11
If you do request plscope - PLScope identifier and call information is merged with PLDoc parse information.... read more
There is a new PLDoc release (and an associated maven-pldoc-plugin release - 2.19) that has 2 new features:-
CREATE [ OR REPLACE ] ... JAVA ...statements - Database Java may now have the same visibility that PL/SQL does.
Support is limited - it currently takes the
@headcom comment from the
CREATE ... JAVA statement. It does not pull the Javadoc from the Java source.... read more
Sometime after August of last year the legacy automated background process that synchronised PLDoc releases on Sourceforge to the Maven Central repository was turned off. Since then there have been several releases which did not appear in http://search.maven.org.
We have just got around to changing the projects to use the recommended approach to pushing releases to Maven Central: they now go via the Sonatype OSS repository. The backlog of invisible releases has been released manually and the Maven projects are currently being altered to deploy to the OSS Maven repository. ... read more
This experimental release contains code kindly submitted by Matthias Hendler. The code is not yet integrated into main branch and there may be yet some bugs and incosistencies in it. Nevertheless, I feel that the code should be released AS IS and as early as possible.
After long pause, a new release is out.
See change log for details.
Thanks to Christophe Grosjean, we have now Maven plugin for pldoc:
From now on, if you want to submit a feature request, do it under Bugs.
It is easier to maintain one list of problems/enhancements instead of two.
We introduce a possibility to download "unstable" versions of PLDoc:
Hope this will help those users who need the latest features and bug fixes but are reluctant to build it yourself from CVS.
There is a couple of feature requests under the PLDoc project
that maybe You can help to implement:
770952 GUI frontend for pldoc
769012 Ant target
pldoc home page is updated, to give some quick information for newcomers:
This release includes some bugfixes and enhancements.
Next release will hopefully address processing of functions, procedures and package bodies.
To facilitate free discussion on PLDoc, a mailing list is created.
Go to http://lists.sourceforge.net/lists/listinfo/pldoc-chat to subscribe.
Whatever you have to say is welcome.
This is kind of intermediate release: some issues I have tried to resolve are not yet 100% resolved.
But as it passed regression tests, I have decided to release what I have, according to "release early, release often" principle.
Includes some bug fixes as well as new functionality.
Some small but useful changes.
Unlike the first release, this is not more considered a demo. See release notes for the list of improvements.