Skip to content
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.

Sign up for GitHub

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

Jump to bottom

support subprojects with different versions #116

Closed
wants to merge 1 commit into from
Closed

support subprojects with different versions #116

wants to merge 1 commit into from

Conversation

christierney
Copy link
Contributor

Generates release task list with fully-qualified task names, allowing
you to run the release task on a single subproject at a time. Expects
you to apply the plugin seperately to each subproject.

Note: this may mean that subprojects can have different VCS, but I
haven't tested that.

@christierney
support subprojects with different versions
c3c2049 
Generates `release` task list with fully-qualified task names, allowing
you to run the `release` task on a single subproject at a time. Expects
you to apply the plugin seperately to each subproject.

Note: this may mean that subprojects can have different VCS, but I
haven't tested that.
@danez
Copy link
Contributor

danez commented Jul 14, 2015

Thanks for your contribution. I haven't tested or checked with multi-project builds at all.

Is ./gradlew release still working with this PR? Because you write in the README ./gradlew :release

I will have a look at this soon.

@christierney
Copy link
Contributor Author

For a multiproject build, ./gradlew release would work but would release every subproject that included the plugin, which may or may not be what's intended. In that situation ./gradlew :release would be the way to release just the root project.

In non-multiproject builds ./gradlew release should work fine and the same way it does today.

@danez danez added this to the 2.2.0 milestone Jul 21, 2015
@danez danez mentioned this pull request Jul 28, 2015
Merged
@danez danez mentioned this pull request Aug 10, 2015
Closed
@danez danez modified the milestones: 2.3.0, 2.2.0 Sep 8, 2015
danez added a commit that referenced this pull request Sep 22, 2015
@danez
Use current projects name and not the rootProject name (needed for #116)
e94ec6d
@danez
Copy link
Contributor

danez commented Sep 22, 2015

closed via 86980c4
will be part of 2.3.0
I rebased it and tested it.
We need to document that you need to include the projectName in the tagName, as otherwise you might have tag collisions.

@danez danez closed this Sep 22, 2015
@danez danez mentioned this pull request Sep 22, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.3.0
Development

Successfully merging this pull request may close these issues.
2 participants
@christierney @danez