👋 Welcome back kcr! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

I pushed the following updates:

• Added a utility to print an incubator warning
• Updated the Incubator Modules JEP:
  • Change javafx.incubator to jfx.incubator
  • Say that a JEP is needed to finalize or drop an incubating feature
  • Clarify that a feature should not incubate indefinitely
• Updated the instructions to create a new incubator module. As part of this, I marked the changes in the JavaFX core (e.g., in build.gradle) with one of the following two comments:
  • //TODO: incubator dependency : Changes that will be needed in the core in support of incubator modules in general, which include the new utlity class and many of the changes in build.gradle; these changes will need go into mainline (via a separate enhancement) ahead of any specific incubator module
  • //TODO: incubator template : Identifies modifications needed in the core for a specific incubator module; these changes would be part of a PR for that specific incubator

Incubator warning works as expected:

WARNING: Using incubator modules: jfx.incubator.richtext

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

BTW, should we have a separate, real PR with changes only for enabling the functionality (.md file and build.gradle, the latter with sample module changes commented out - maybe with an easy to grep marker for anyone who wants to add a new incubator module)?

BTW, should we have a separate, real PR with changes only for enabling the functionality (.md file and build.gradle, the latter with sample module changes commented out - maybe with an easy to grep marker for anyone who wants to add a new incubator module)?

Yes, something along those lines is in the works.

I've already identified many of the changes that would be part of this separate Enhancement, and marked them with //TODO: incubator dependency -- see the above comment.

I'm not sure yet what the best way is to show where to add the logic for a new incubator module. At least having an easy-to-find "incubator modules go here" comment would be helpful and seems like a good idea. As you suggest, I could go farther than that and add commented-out build logic for the sample module...need to think about that one. I would not be in favor of including the sample module, though, so I'm leaning towards just adding the appropriate markers in build.gradle, but not any actual build logic for an incubator modules. Anyone doing an incubator module would need to grab the sample patch anyway.