You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have a particular use-case where (because our CI pipeline is using this plugin indiscriminately across all our Java projects) we need the ability to override the plugin configuration defaults via maven command-line even when the project being built does not reference this plugin. Right now gitFlowConfig cannot be specified via command-line. #263 attempts this, but since it's doing it in constructor, pom files override the configuration, which isn't how it should work with Maven -- command-line overrides pom, not the other way around.
The text was updated successfully, but these errors were encountered:
I guess it becomes against convention if a <configuration>...</configuration> block is provided in the pom. I'd argue that isn't the case in our use-case, but I see your point.
How do you feel about something like this instead:
that allows me to pass -DgitFlowConfig=productionBranch=FOO,origin=BAR via command-line.
This has the advantage of doing it The Maven Way -- via the set(..) method. If pom has a configuration block for the plugin, that takes precedence as expected.
Have a particular use-case where (because our CI pipeline is using this plugin indiscriminately across all our Java projects) we need the ability to override the plugin configuration defaults via maven command-line even when the project being built does not reference this plugin. Right now
gitFlowConfig
cannot be specified via command-line. #263 attempts this, but since it's doing it in constructor, pom files override the configuration, which isn't how it should work with Maven -- command-line overrides pom, not the other way around.The text was updated successfully, but these errors were encountered: