-
-
Notifications
You must be signed in to change notification settings - Fork 182
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
Release-start and release-finish doesn't check for SNAPSHOT dependencies on submodules #28
Comments
Currently it doesn't check for snapshots in modules. But it probably should. Let's see if getting projects from |
Hi, Is there any plans for including this change into a release? My company are currently evaluating various maven gitflow release plugins and really like that this is still being actively developed. This change would be a great help for us as we have a lot of multi-module maven projects in our codebase. Thanks, Lewis |
@Yeggstry Sure. It is good time to release. :) I'll try to do it in a next few days. |
@nickstolwijk @Yeggstry 1.4.0 is released. Enjoy. |
Thanks a lot :) |
Hello, the check does not seem to detect if the parent project dependency is a snapshot version. Is this by design? Example, a project's pom.xml which contains:
^ Does not fail Thank you. |
I'm trying out the gitflow-maven-plugin and I'm encountering the following:
I have a project setup with a aggregator pom in the root, a configuration pom in configuration/ and various modules for the functionality, which all have the configuration pom as parent. In the configuration pom all the dependencies are under build/dependencies instead of build/dependencyManagement. This is because the dependencies of the configuration pom are added to the Tycho targetplatform.
If I run mvn gitflow:release-start on the aggregator pom, I see the logging "INFO : Checking for SNAPSHOT versions in dependencies.", but it finishes without seeing the SNAPSHOT-dependencies of the configuration pom. I believe this is because it checks only the dependencies of the aggregator project and not of the other projects in the tag.
Is this by design or should the check for snapshot stage also check the projects under the tag for SNAPSHOTS? (And the modules under the modules tag can have sub-modules, so it should be recursive if that is the case)
The text was updated successfully, but these errors were encountered: