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.

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

Mark SourceDirectorySet.outputDir as Incubating #2360

Closed
oehme opened this issue Jun 28, 2017 · 6 comments
Closed

Mark SourceDirectorySet.outputDir as Incubating #2360

oehme opened this issue Jun 28, 2017 · 6 comments
Assignees
Milestone

Comments

@oehme
Copy link
Contributor

oehme commented Jun 28, 2017

This API is new in 4.0, but wasn't marked @Incubating. This is even worse since this API is definitely wrong, so we want to change it. We should mark it incubating for 4.0.1, so no one starts depending on it.

@oehme oehme added this to the 4.0.1 milestone Jun 28, 2017
@big-guy
Copy link
Member

big-guy commented Jun 28, 2017

I don't think we should deprecate an existing API without providing another stable API (if we think we should support the use case) to move to. That was the thinking for not making SourceDirectorySet.outputDir incubating (right or wrong).

@big-guy big-guy changed the title Mark SourceDirectorySet.classesDir as Incubating Mark SourceDirectorySet.outputDir as Incubating Jun 28, 2017
@oehme
Copy link
Contributor Author

oehme commented Jun 28, 2017

Alternatively we should fix the design, but that might be a tall order for a hotfix release. As discussed with @wolfs, this should go on SourceSetOutput, just like the methods for resource directories.

@jjohannes
Copy link
Contributor

@wolfs @oehme can one of you make the change, reflecting what you two discussed, to the hotfix branch: https://github.com/gradle/gradle/commits/release_4.0.1 (or prepare a PR based on the branch). Thanks!

@oehme
Copy link
Contributor Author

oehme commented Jul 4, 2017

I've marked it as incubating and changed the deprecation message to point to a non-incubating API (telling users to change the corresponding compile tasks's output dir).

@jjohannes
Copy link
Contributor

Thanks @oehme!

Any remaining concerns @big-guy @wolfs?

Otherwise I assume this is good to go.

@wolfs
Copy link
Member

wolfs commented Jul 6, 2017

Good to go from my side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants