-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to ignore certain files from the "version bump auto-release" process #77
Comments
@danielflower I would be happy to resource the development of this feature myself but I'll likely need some guidance from you. |
Yeah, this is a reasonable feature to have. How about something like a config option called
Could be expanded to be regex or in |
Yes, that's the easy part 😉Could you also give me a few hints where to integrate the checking against this configuration in the code. Which pieces need changing? |
this is also a problem with GIT submodules used, as GIT parent project stores hash of commit of each subproject. Commit in subproject have to be followed by commit in parent project. |
@danielflower I started looking into this and the current hypothesis is that I can work with path filters inside |
This includes refactoring those methods that accept a ton of mojo configuration parameters. There is now a single class that wraps all of those. Fixes danielflower#77
This includes refactoring those methods that accept a ton of mojo configuration parameters. There is now a single class that wraps all of those. Fixes danielflower#77
This includes refactoring those methods that accept a ton of mojo configuration parameters. There is now a single class that wraps all of those. Fixes danielflower#77
Hello, |
@talend-jphautin #94 does address this. |
That is a feature that I've been waiting for a few years now. Thanks to both of you for your work btw ! |
@Romain125 Sorry, we gave up waiting and moved on. |
It shouldn't be too complicated to take @marcelstoer changes into a new branch from master if of-course @marcelstoer agrees to take parts of the code as-is. |
@kobynet Feel free to do whatever you want with my code. |
Hi @danielflower, |
This commit realign Fixes danielflower#77
This kind of builds on top of #76. However, since it's likely a missing feature I report it separately.
Scenario
pom.xml
like.editorconfig
,.gitignore
and.gitlab-ci.yml
.Problem: a single change to any of those files will trigger the release of each module upon next invocation of the plugin as the root project changed.
I argue that this is undesirable in most cases. (How) can this behavior be turned off?
The text was updated successfully, but these errors were encountered: