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

Figure out a manual way to upload JVM artifacts to some public repo #14

Closed
krzema12 opened this issue Jun 21, 2019 · 3 comments
Closed
Labels
enhancement New feature or request

Comments

@krzema12
Copy link
Owner

krzema12 commented Jun 21, 2019

It's a mitigation of not having #1 done.

@krzema12 krzema12 added the enhancement New feature or request label Jun 21, 2019
@krzema12 krzema12 added this to the Public beta for JVM milestone Jun 21, 2019
@krzema12
Copy link
Owner Author

For publishing the initial version, everything was done without using Gradle Bintray plugin:

  • call publishToMavenLocal Gradle target
  • go to ~/.m2/repository
  • zip (I tested only on this format, tar.gz doesn't work) the top-level directory found there
  • create a new version on Bintray
  • select an option to upload the files
  • upload the ZIP file there, selecting that it should explode the archive
  • publish the uploaded files

I don't yet know how to publish some next version. When I was doing it for 1.0.0 - > 0.1.0-beta, I got some messages that it's not possible to overwrite some files. That's why the Gradle Bintray plugin may be necessary to for it, because it has some option like overwrite.

@krzema12
Copy link
Owner Author

I managed to publish 0.2.0-beta version, but with one difference in the above list of steps. Before zipping, I had to rename all files maven-repo-local.xml to maven-repo.xml. Otherwise, Bintray was saying that the file already exists.

@krzema12
Copy link
Owner Author

No need - automatic publishing works.

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

No branches or pull requests

1 participant