Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.9K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.4K Development
- 17 Developer Projects
- 139 Programming Languages
- 293.1K Development Tools
- 111 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 161 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 475 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
How to debug custom taglets?

I am attempting to write a custom taglet that emits a table of information about any javax.validation constraints in the enclosing class. I'm actually making progress on the implementation, to the point where I'm refining the information I get from the validator infrastructure.
However, what is really annoying is that the only way I can debug my implementation is by adding print statements. There appears to be no obvious way to get to a point where I can step through my code in a debugger.
I found the "ToolProvider.getSystemDocumentationTool()" call, which at lets me run javadoc from a test class, but that just forks a process. I suppose there is the "-J" command-line option. Is my only choice to pass the "-Xdebug" and related options through this, and then run a remote debugger to connect to that port? I tried passing "-J-Xdebug" as one of the parameters to the "run()" method, but that fails with "javadoc: error - invalid flag: -J-Xdebug".