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

enforce-linkage-checker #6396

Open
elharo opened this issue Oct 1, 2019 · 2 comments
Open

enforce-linkage-checker #6396

elharo opened this issue Oct 1, 2019 · 2 comments
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. semver: patch A minor bug fix or small change. type: process A process-related concern. May include testing, release, or the like.

Comments

@elharo
Copy link
Contributor

elharo commented Oct 1, 2019

Set up the enforce-linkage-checker rule in pom.xml

https://github.com/GoogleCloudPlatform/cloud-opensource-java/tree/master/enforcer-rules

@elharo elharo added type: process A process-related concern. May include testing, release, or the like. priority: p2 Moderately-important priority. Fix may not be included in next release. semver: patch A minor bug fix or small change. labels Oct 1, 2019
@athakor
Copy link
Contributor

athakor commented Nov 18, 2019

@elharo do you want to add enforcer-rules in each client pom.xml?

@athakor athakor added the needs more info This issue needs more information from the customer to proceed. label Nov 18, 2019
@elharo
Copy link
Contributor Author

elharo commented Nov 18, 2019

We want linkage checks enforced across the projects. If that can be done ina single pom.xml file, that's good. If not, we can put it in the individual pom.xml's.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. semver: patch A minor bug fix or small change. type: process A process-related concern. May include testing, release, or the like.
Projects
None yet
Development

No branches or pull requests

2 participants