I want(ed) to do this because I want(ed) the generated docs to be readily available for viewing. As for getting myself in trouble ... you are most assuredly right! Risks aside, no matter what I tried, Maven wouldn't comply. So I came up with my own solution.
I stood up a Reposilite Maven repository on one of my VPSs. All my private libraries get deployed there. I created a service to periodically monitor the repository for any/all JavDoc JARs. The service then creates some directories in /var/www/html/.... to match the JARs. Then the service uses fuse-zip to mount each JAR to its respective directory. It then updates a template web page to have accurate links. Voila! This gives me an off-site location for my libraries, quick access to as-accurate-as-possible docs, and a convenient URL to access them. I could have added an entry in .gitignore so that the JavaDoc JAR would get pushed to GitHub but not all my projects are on GitHub. On Thursday, April 24, 2025 at 01:54:26 PM EDT, Michael Osipov <[email protected]> wrote: On 2025/04/22 21:47:03 w f wrote: > I'm trying to send my generated Java docs to a custom directory. Why do you need this? You are getting yourself in trouble because other tools expect a specific location for the Javadoc output. M --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
