#100 missing support for FORCE keyword in object types
open
nobody
None
5
2012-12-31
2012-12-31
Anonymous
No
Documentation is generated well for plsql object types until I add the FORCE keyword.
When I use the FORCE keyword, then pldoc writes this error message (see attachment errormsg.txt).
Try 1.3.4 or later (currently 1.3.6)
If you are using the Maven plugin, the synchronisation between sourceforge and the Maven central repository is low/stalled.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It was just nice timing - I had been neglecting PLDoc changes whilst trying to integrate PL/SQL into PMD. I pulled back some changes back into PLDoc, released the changes and others that had aggregated over the past few months - then checked the Bugs list.
So, a quick trip to the syntax documentation, a change, a unit test (THANKS FOR THE TEST CODE IN THE REPORT!), a regression test and another release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
error message
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
test case
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
I'm using pldoc version 1.3.3
Try 1.3.4 or later (currently 1.3.6)
If you are using the Maven plugin, the synchronisation between sourceforge and the Maven central repository is low/stalled.
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
It works well.
Thank you for a fast fix.
It was just nice timing - I had been neglecting PLDoc changes whilst trying to integrate PL/SQL into PMD. I pulled back some changes back into PLDoc, released the changes and others that had aggregated over the past few months - then checked the Bugs list.
So, a quick trip to the syntax documentation, a change, a unit test (THANKS FOR THE TEST CODE IN THE REPORT!), a regression test and another release.