I will give you an example to explain my problem:
When releasing, I want to commit each project’s api doc to a git repository but each of them to a different branch. So commiting one goes like this:
- Checkout branch named like the project. 2. Removed the “api” directory from the repository. 3. Recreate an empty “api” directory and copy the generated javadocs into this “api” folder. 4. Stage and commit the changes.
It would have been nice to do these in 4 different tasks but I could not do this safely because Gradle might decide that it first executes the “checkout” tasks of each project then proceeds which is of course not what I want. If this atomicity is not possible, what is the best way to solve this problem?
ps.: Minor issue in the forum: I came here from http://forums.gradle.org/gradle and my “one sentence question” was put into the “Post” field rather than the “Title”.