Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add support for different documentation dir

Open
#110 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java

Research direction

Start by locating the codegen handling for outputDirectory and the generated asciidoc files, then compare the option used by vertx-docgen. Done means codegen accepts a configurable documentation output location, using the same option where possible, while generated classes and resources retain their existing locations.

Written by the indexing model from the issue text.

Description

right now everything generated by verty-codegen goes into:

outputDirectory\generated ~ generated classes
outputDirectory\resources ~ generated resources 
outputDirectory\ascidoc ~ generated asciidoc

It would be great if you could support changing the location of the generated asciidoc, vertx-docgen supports this so it's kind of annoying that you can't specify the location of the generated asciidoc files for codegen. maybe even respond to the same option, so they both can be used in combination

Dominant language
Java
Stars
111
Forks
88
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-vertx/vertx-codegen

All issues in eclipse-vertx/vertx-codegen

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.