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

[BEAM-3938] Add publish gradle task #5004

Closed
wants to merge 1 commit into from

Conversation

jbonofre
Copy link
Member

@jbonofre jbonofre commented Apr 3, 2018

It's a WIP. The purpose is to start the prepare the publish of the artifacts to Maven Repository using Gradle.


Follow this checklist to help us incorporate your contribution quickly and easily:

  • Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
  • Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
  • Write a pull request description that is detailed enough to understand:
    • What the pull request does
    • Why it does it
    • How it does it
    • Why this approach
  • Each commit in the pull request should have a meaningful subject line and body.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

@jbonofre jbonofre requested a review from lukecwik April 3, 2018 16:22
Copy link
Member

@lukecwik lukecwik left a comment

Choose a reason for hiding this comment

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

CC: @alanmyrvold Can you take a look at this since you have the most experience in attempting to publish artifacts.

*/

subprojects {
apply plugin: 'com.bmuschko.nexus'
Copy link
Member

Choose a reason for hiding this comment

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

We already have a maven-publish task defined here:

maven {

Is there a reason why you want to migrate to using the nexus plugin?

@jbonofre
Copy link
Member Author

jbonofre commented May 3, 2018

This PR is useless as publishing has been implemented. I'm testing the artifacts.

@jbonofre jbonofre closed this May 3, 2018
@jbonofre jbonofre deleted the GRADLE_RELEASE branch May 3, 2018 16:54
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

2 participants