-
Notifications
You must be signed in to change notification settings - Fork 202
Allow to provide additional fragment filename mappings #1382
Comments
Should be the default disk-based or classpath based? Not sure about the best usage for default. If disk-based, which would be the best default folder location for a Maven plugin? |
Maybe we could allow both:
|
Ok then for now just classpath in Now checking how to make to read custom ones from Maven |
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions! |
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions! |
Description
Currently, the mapping from filename suffixes to resource kinds is predefined within the plugin (now via an internal configuration implemented for #1372).
To be more future proof for new kinds it would be nice to allow the user to specify additional mappings.
This could be done in several ways:
suffix=kind
properties. Maybe with a sensible default for the filename which, when it exists, is automatically picked up (like the fragments)The text was updated successfully, but these errors were encountered: