Release latest version on Central about libsvm HOT 33 CLOSED

Good morning,

3.23 is now available via Maven Central under the official groupID of the Dept. of Computer Science & Information Engineering of the National Taiwan University.

        <dependency>
            <groupId>tw.edu.ntu.csie</groupId>
            <artifactId>libsvm</artifactId>
            <version>3.23</version>
        </dependency>

I think, we can close the issue now.

Note, it will take some more time till all mirrors are in sync.

Best,
rzo1

from libsvm.

I have set up the project with all the required pom files here: https://github.com/datumbox/libsvm
Nevertheless I'm not sure if a pull request makes sense in this case. This is because @cjlin1 won't be able to publish under com.datumbox groupid. I think the proper way to go it to create his own groupid, sign up with sonatype and be able to publish on maven central repo.

At any case I agree that it would be way better if the author of the project actually produces one official release on maven repo, rather than me or anyone else produce "unofficial" releases.

from libsvm.

Good morning,

3.24 is now available via Maven Central under the official groupID of the Dept. of Computer Science & Information Engineering of the National Taiwan University.

        <dependency>
            <groupId>tw.edu.ntu.csie</groupId>
            <artifactId>libsvm</artifactId>
            <version>3.24</version>
        </dependency>

Note, it will take some more time till all mirrors are in sync.

Changelog as usual: https://www.csie.ntu.edu.tw/~cjlin/libsvm/log

Best,
rzo1

from libsvm.

Good morning,

3.25 is now available via Maven Central under the official groupID of the Dept. of Computer Science & Information Engineering of the National Taiwan University. It will take some time to sync as I jsut released the artifact on Sonatype.

        <dependency>
            <groupId>tw.edu.ntu.csie</groupId>
            <artifactId>libsvm</artifactId>
            <version>3.25</version>
        </dependency>

Best,
rzo1

from libsvm.

+1

from libsvm.

@davido @datumbox maybe you can work together for this: https://github.com/datumbox/libsvm

:)

from libsvm.

The Datumbox Machine Learning framework uses libsvm. Given that @cjlin1 does not publish the library on Maven, I always prepare a mavenized version as soon as a new release becomes public. Both version 3.21 and 3.22 are available on Maven: https://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22com.datumbox%22%20AND%20a%3A%22libsvm%22

from libsvm.

Nice! @datumbox any luck making @cjlin1 accept a pull request? :)

from libsvm.

Any updates here? Can you (@cjlin1) provide an official release version via Maven Central?

from libsvm.

We can do that if it's not too complicated. Can someone give me the instructions for doing that? Thanks

from libsvm.

Hey @cjlin1

thanks for your response.

We need to add some files to mavenize the libsvm project in order to publish to Maven Central (via Sonatype). I would propose, that we send you a PR with the related pom.xml, which is needed for that step.

In addition, some steps on Sonatype need to be conducted (see https://central.sonatype.org/pages/ossrh-guide.html):

1. Create a JIRA Account
2. Create a Ticket to claim the namespace / groupid tw.edu.ntu.csie.libsvm or tw.edu.ntu.csie or something else like com.github.cjlin1 / com.github.cjlin1.libsvm for the project.
3. After the ticket is processed, we are ready for deployment on Sonatype
4. You will need a GPG Key to sign the resulting JAR artifacts (we can explain this in the related PR)

@datumbox Do you the time to provide a related PR? If not, I can conduct this as well.

from libsvm.

@cjlin1 thanks for looking into it. It may help: Gerrit Code Review project has in depth documentation how to do it: [1].

[1] https://github.com/GerritCodeReview/gerrit/blob/master/Documentation/dev-release-deploy-config.txt

from libsvm.

from libsvm.

Thanks for the reply @cjlin1

If the Sonatype Repository for tw/edu/ntu/csie/libsvm already exists, it might be a problem. However, the guys from Sonatype can handle such a situation, because you can proof, that you are the original author of libsvm. Or they will ask some additonal question in the issue tracker,

An alternative would be to use com.github.cjlin1 / com.github.cjlin1.libsvm as the groupId, which is not yet taken.

from libsvm.

@rzo1 @cjlin1 I created this dummy PR based on my fork so that you can check easier the changes.

I closed it to avoid accidental merges as the PR should not be merged as is. The pom.xml file needs to be updated to reflect @cjlin1's project details, versions, keys etc. Please review the modifications (other than the obvious group ids, descriptions etc) and let me know if you see anything weird.

Publishing to Maven Central is quite straightforward but the first time is a bit more manual. As @rzo1 pointed out, the group id already exists so if you don't have the credentials you will need to regain access. I don't believe it would be hard to prove you are the owner and doing so will save you time from the initial manual release.

Happy to help you out with the details of setting it up. It's always best if the owner of the library releases official versions rather than relying on others maintaining forks. :)

from libsvm.

It's always best if the owner of the library releases official versions rather than relying on others maintaining forks. :)

+1.

from libsvm.

from libsvm.

On sonatype what's the way to send someone a message?

the way we communicate with the Sonatype guys is to leave a message on an issue and ask for the help. But to leave a message on an issue, and claim an account back, you need account first. May be create a second account and claim the first one is actually your account, and when it assigned to you, close the second account?

from libsvm.

On sonatype what's the way to send someone a message?

the way we communicate with the Sonatype guys is to leave a message on an issue and ask for the help. But to leave a message on an issue, and claim an account back, you need account first. May be create a second account and claim the first one is actually your account, and when it assigned to you, close the second account?

I agree with that. I would open an ticket... this is the fastest way to communicate with them.

from libsvm.

from libsvm.

It seems, that they have responded very quickly :) - https://issues.sonatype.org/browse/OSSRH-45008
Thank you very much for pushing this forward @cjlin1

from libsvm.

from libsvm.

Hey @cjlin1 ,

imho, that means, that they have granted your account cjlin1 the permissions to publish under tw.edu.ntu.csie (if I get the groupID in the first tickets correct).

I think, you can proceed with mavenizing the project now. Let us know, if you need some support on doing this.

from libsvm.

from libsvm.

Hey @cjlin1

the website is indeed down atm. I think, that it will be available again soon.

To answer some of your questions:

The svm.java is generated from the .m4 file in line 69ff and added to the resulting source file.

You should also consider to change

<java-version>11</java-version>

to

<java-version>8</java-version>

to maintain compatibility with older environments. I guess, that a lot of people still depend on Java 8.

Related to the process to publish a release artifact:

1. You need to get the current project mavenized by applying (most of, but not all) changes in the PR you mentioned.
2. You need to conduct the release via Maven. The files will then be uploaded via Maven to Sonatype into a "Staging"-Repository. Afterwards, some automatic checks will be conducted by Sonatype. If they pass, you can "promote" the artifact as a release (via the Web-UI of Sonatype).
3. .gitignore is not mandatory here, but Maven will generate some files, which shouldn't be pushed into a Git-Repository.

from libsvm.

from libsvm.

Hello @cjlin1 ,

Related to your questions above:

You need to

• (1) checkout libsvm from Github
• (2) apply the changes from above
• (3) push the changes to GitHub (so you do not have to repeat them for the next release again)
• (4) build it via Maven (this step requires a JDK + Maven on your local PC) with the activated Maven Profile release-sign-artifacts. This step will automatically upload the artifacts to the "Staging Repository" in Sonatype.
• (5) If the checks in the "Staging Repository" on Sonatype pass, you can promote the artifacts as a release. This step is conducted in the Web-UI of Sonatype.

Steps (1) to (4) need manual intervention on your local PC.

I can support with the steps mentioned above, if you like. For this purpose, I will send you a mail to your institutional mail address.

from libsvm.

@cjlin1 Apologies for the late response, it's been a busy week.

I think @rzo1 did an awesome job answering your questions but just to be safe I added a couple of comments on my original PR for all the things that need to change. I also turned on the "allow edits from maintainers" feature so that you can push your changes on the PR if you want.

from libsvm.

from libsvm.

Thanks!

from libsvm.

@rzo1 Thanks for the heads up. I tried updating the dependencies of Datumbox Framework and it seems that the mirrors are not in sync. Any change you could confirm that the release was indeed completed successfully? Typically syncing does not take so much long.

Thanks a lot in advance!

from libsvm.

Good catch! Sync should now be on the way!

from libsvm.

It works! :) Thanks for making it available.

from libsvm.