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

Choose the correct groupId for proguard #36

Merged
merged 1 commit into from
Jul 31, 2020
Merged

Choose the correct groupId for proguard #36

merged 1 commit into from
Jul 31, 2020

Conversation

squadgazzz
Copy link
Contributor

GroupId for Proguard 7.0.0 has been updated to com.guardsquare
https://bintray.com/guardsquare/proguard/com.guardsquare%3Aproguard-base/7.0.0

@lightbend-cla-validator

At least one pull request committer is not linked to a user. See https://help.github.com/en/articles/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user

1 similar comment
@lightbend-cla-validator

At least one pull request committer is not linked to a user. See https://help.github.com/en/articles/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user

Copy link
Member

@pvlugter pvlugter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks.

private def groupId(proguardVersionStr: String): String =
"^(\\d+)\\.".r
.findFirstMatchIn(proguardVersionStr)
.map(_.group(1).toInt) match {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think sbt has some built-in version parsing now, although maybe not available for sbt 0.13 if this plugin is still cross-compiled.

@pvlugter pvlugter merged commit 622e8f5 into sbt:master Jul 31, 2020
@pvlugter
Copy link
Member

Version 0.4.0 released with these changes

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

Successfully merging this pull request may close these issues.

3 participants