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

update build to be more modern #12

Merged
merged 3 commits into from
Feb 4, 2019
Merged

update build to be more modern #12

merged 3 commits into from
Feb 4, 2019

Conversation

lbergelson
Copy link
Member

as part of preparing to release a new version with fixes I updated the gradle build

* updating class file location due to gradle changes
* moving from maven -> maven-publish plugin
* make build.gradle more modern and cleaner
* fix artifactory link to new broad artifactory
* using gradle properties for artifactory password instead of
environment variables
updating gatk-native-library version to 1.0.0
@lbergelson
Copy link
Member Author

@samuelklee In order to fix the log issue I've updated the gradle build. Could you do a review?

@coveralls
Copy link

Coverage Status

Coverage increased (+0.03%) to 70.18% when pulling 9a4159b on lb_update_gradle into 9f9762c on master.

Copy link
Contributor

@droazen droazen left a comment

Choose a reason for hiding this comment

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

One question, otherwise looks good 👍

maven {
credentials {
username = isRelease ? project.findProperty("sonatypeUsername") : project.findProperty("artifactoryUsername")
password = isRelease ? project.findProperty("sonatypePassword") : project.findProperty("artifactoryPassword")
Copy link
Contributor

Choose a reason for hiding this comment

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

what will happen if you don't set either of these? can we get a nice error message?

Copy link
Member Author

Choose a reason for hiding this comment

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

if it's not set and you don't try to publish, no problem
if it's not set and you do try to publish, you get a not very helpful error. I haven't come up with a good way to throw a more useful exception because of the way that configuration / execution works.

I want to be able to run something at the time the task is configured but only if the task is in the execution graph but I'm not sure how to do it...

@samuelklee
Copy link

Thanks, @lbergelson! I'm probably not qualified to do a review, so glad @droazen has it covered.

@lbergelson lbergelson merged commit 371e9db into master Feb 4, 2019
@lbergelson lbergelson deleted the lb_update_gradle branch February 4, 2019 23:11
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.

None yet

4 participants