Release 1.5 missing from mvn-repo #52
Comments
Last time I tried it still worked for me, can you please elaborate on the steps to reproduce?
We considered that merge but decided otherwise. kind regards |
The latest release
Good to hear, any plans to publish the package in an official repo? |
My greatest problem with the maven release process is that I know no way how to find out which files have been released where. + I also don't know any developer tools, URLs or protocol descriptions to check that and I unsuccessfully tried a bit of sniffing to reverse engineer the protocol. + I frequently got mixed up in apparently errorneous directory listings. The reason why I asked for steps to reproduce is that the only way I know is actually using them in a pom file and invoke try running something like 1.5.0 is apparently not a branch but a tag. And I had hoped release:prepare/release perform would update the mvn repo. So I deleted the mustang-1.5.0 tag because otherwise the release would complain and did the following again, with the following output: Afterwards I did test it with a blank project, which worked but no longer does.
Since I dont know how, not at all, your help would be appreciated. |
|
After playing around with the release plugin I got it working on my fork. Setting up auth was a bit tricky since i have 2FA-Auth enabled. I had a problem that by default an older version of the I also updated the What works for me is:
|
|
@mksplg cool thanks I updated the site-maven-plugin but I do not find the maven-release-plugin in my pom, do i have to add it in order to specify the version to 2.5.3? |
|
Yes, I added it in my pom with in the plugins section. If not specified it uses some default version. You can check the version in use with |
|
thanks @mksplg , I released it as 1.5.1 and it looks as if the maven artifacts are there |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The latest release 1.5 is missing from the maven repository mvn-repo.
Is the answer in #1 still current regarding a merge with konik.io? Are there any plans otherwise to publish the packages maven central or jcenter?
The text was updated successfully, but these errors were encountered: