Skip to content

Conversation

@byteit101
Copy link

A start for javadoc for #13534

Copy link
Contributor

@joakime joakime left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a fan of this change in the javadoc.

If you want to document this, do it in the documentation around the jetty-home and/or jetty-start documentation.

* Configure the Environment specific Deploy settings.
*
* @param name the name of the environment.
* @param name the name of the environment. This is usually one of "core", "static",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These names only exist if you are using jetty standalone.
They come into existence due to the configuration you are using.
The names themselves actually exist in the ${jetty.home}/modules/*.mod files.

On Jetty Embedded (an super common use case) the environment names do not exist.
So documenting them as existing in the javadoc isn't correct.

@sbordet
Copy link
Contributor

sbordet commented Oct 31, 2025

@byteit101 we acknowledge there is missing documentation about this way of using Jetty.

The matter should have a more comprehensive documentation about environments and deployment than just javadocs, so we're going to expand the documentation about this for 12.1.x, and I'll take care of it.

Stay tuned for the updates, and your review will be appreciated.

Thanks for raising this issue and PR.

@sbordet
Copy link
Contributor

sbordet commented Oct 31, 2025

@byteit101 I'm closing this PR, which is now superseded by #13946.

I'd appreciate your review of the new documentation added in the new PR.
Thanks!

@sbordet sbordet closed this Oct 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants