-
Notifications
You must be signed in to change notification settings - Fork 94
Releasing multi-module project #58
Comments
Not sure you're missing anything. I don't think plugin is set up well to handle multi-projects. Sounds like two separate issues so far:
|
Here is the full output:
|
Looks like a separate issue. Added it as #60. |
Ok cool, I subscribed #60 Regarding the releaseTask definition I am currently doing
Obviously not optimal. There might also be additional tasks you only want to execute once for the root project and after all submodules are build. For example your publishGhPages task should upload an aggregated JavaDoc from all submodules and not the JavaDoc from each submodule on its own. |
OK. Would it help if I added a shouldRunAfter ordering to everything in the list? That way they would typically be in the order they are listed. |
I'm going to close this for now. If you would like some changes to address the issues you've had with multi-project please reopen and let me know what your thoughts are. |
Hi,
can you give me an example on how to release a multi-module project with your grgit-release plugin?
If I apply the plugin to all my subprojects it tries to create the same version for each subproject which obviously fails in git.
If I apply the plugin to the root project only then
1.) releaseTask needs to reference subproject tasks which is annoying if you have quite some subprojects, e.g. releaseTask = [ ':proj1:clean', 'proj2:clean', 'proj1:build', 'proj2:build' ]
2.) the prepare task fails because no version has been inferred.
The build file of the root project is basically like:
I think I am missing something obvious.
Thanks in advance.
The text was updated successfully, but these errors were encountered: