Add an option to avoid doing anything regarding settings.xml

[leemeador]

Description:
I can currently:

• create a settings xml in a folder of my choice
• leave a settings xml in the default folder
• overwrite a setting.xml in the default folder

I would like to:

• do nothing whatsoever with any settings.xml

I propose changing the input "settings-path" so the value "NONE" (or some other magic value) will cause nothing to be done regarding creationg or writing to a settings.xml file.

Justification:
Since I want to create my own settings.xml OR leave use a settings.xml the dev team puts in the repo, I would like this action to take no action regarding settings.xml.

I have been simulating this by adding the input "settings-file: dummy" so it will be created in some place it will be ignored.

Are you willing to submit a PR?

maybe

[leemeador]

I find that it is particularly unintuitive that the default settings regarding settings.xml is to create it and overwrite whatever the user has in their repo.

[priyagupta108]

Hi @leemeador 👋 , Thank you for your report!
To clarify, the action already supports the overwrite-settings: false input. When this is set, setup-java will not overwrite an existing settings.xml file.
This option allows you to use and preserve your own settings.xml, ensuring that setup-java neither modifies nor creates a new one if it already exists.

Let us know if you have any further questions or if this doesn’t fully address your use case.

[priyagupta108]

@leemeador 👋,
Just following up to see if you had a chance to review my previous comment. Did the overwrite-settings: false input work for you? Please let us know if you have any questions or updates.
Thanks!

[priyagupta108]

@leemeador 👋
Just checking in to see if the overwrite-settings: false input helped. Let us know if you're still running into any issues or if everything is working as expected.