Skip to content

Document Main-Class in the Application Client FAQ #61 - #151

Open
AzazelSensei wants to merge 3 commits into
apache:masterfrom
AzazelSensei:docs-61-main-class-faq
Open

Document Main-Class in the Application Client FAQ #61#151
AzazelSensei wants to merge 3 commits into
apache:masterfrom
AzazelSensei:docs-61-main-class-faq

Conversation

@AzazelSensei

Copy link
Copy Markdown

The FAQ only showed how to set Class-Path. Application Client jars also need Main-Class.

I added that to the FAQ (same Archiver config as the Class-Path example) and a one-line pointer on the usage page.

  • Addresses just one issue
  • Unit tests (docs only)
  • mvn verify / ITs not needed for site markdown
  • I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

Fixes #61

The Java EE spec requires an Application Client jar to declare
Main-Class. The FAQ only covered Class-Path.

apache#61
@slachiewicz

Copy link
Copy Markdown
Member

can we move all content from faq to usage and drop this single faq file?

@slachiewicz slachiewicz added the documentation Improvements or additions to documentation label Aug 28, 2026
Comment thread src/site/markdown/usage.md.vm Outdated
No default Main-Class unless archive.manifest.mainClass or a custom manifest sets one.
@AzazelSensei

Copy link
Copy Markdown
Author

Moved the FAQ content onto the usage page and dropped the FAQ file. There is no default Main-Class unless you set archive.manifest.mainClass or provide a custom manifest.

Comment thread src/site/markdown/usage.md.vm Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[MACR-3] Maven site should have an example of adding Main Class

4 participants