release in maven central

[stokpop]

Hi,

to help with our packaging of this library it would really help if it got released in maven central.

Is it possible for you to release to maven central?

Thanks.

[artemlos]

@stokpop Hi! We are working on adding it to the maven central repository. I will let you know once it is available. /Artem

[stokpop]

@artemlos Hi Artem, is there progress to report on this issue? Thanks.

[artemlos]

@stokpop Hi! Sorry, it took longer than expected. We will try to get it done by the end of next week.

[sergey-oplavin]

@artemlos Hi Artem, just wanted to ask if there is any update on the issue?
Adding cryptolens jar to maven/gradle project is not very convenient now, so it would be really nice to have it published into Maven Central (or to any other place).
We have recently published one of our public packages to Maven Central, so if you have any questions about the procedure - don't hesitate to ask. Thanks.

[artemlos]

@sergey-oplavin thanks for offering your help!

I think we got stuck on either creating the correct configuration. There is already a package registered on Sonatype (https://issues.sonatype.org/browse/OSSRH-61669), which I believe was the first step that was necessary.

I will look into it and get back where exactly we had issues. We use IntelliJ, so I will look for a tutorial and try it again.

[artemlos]

@sergey-oplavin Just wanted to check with you if you recognize the following authentication error when running mvn deloy? https://s01.oss.sonatype.org/content/repositories/snapshots/io/cryptolens/cryptolens/1.24-SNAPSHOT/cryptolens-1.24-20211117.134324-1.pom.asc

I will look into it more, but I just wanted to check in case you have seen this error before and know the possible cause.

[sergey-oplavin]

@artemlos Did you provide your username/password for sonatype server in settings.xml?

[artemlos]

@sergey-oplavin Yep, that was done. I followed the following tutorial: https://central.sonatype.org/publish/publish-maven/#

I will double check that the folder is correct, etc. It might be that IntelliJ does not find the file.

[sergey-oplavin]

@artemlos Just verified - if I don't have the following section in my ~/.m2/settings.xml file, it shows the same error on deploy.

<server>
	<id>ossrh</id>   
	<username>user</username>
	<password>pwd</password>
</server>

Where user and pwd are credentials for sonatype (https://s01.oss.sonatype.org/)

[artemlos]

@sergey-oplavin I have the configuration that you listed above, but it appears that when I authenticate on https://s01.oss.sonatype.org/, I get an authentication error:

I will look into how new credentials can be created for that page. I thought that I could just use the same as for Sonatype Jira.

[sbraconnier]

Hello,

We are evaluating the cryptolens software licensing system for our product, but came across this issue. It's been 4 years since the last issue update. Any news about this issue??

Note that the OSSRH service has reached end-of-life on june 25, 2025

You must now publish through the Central Publishing Portal:

https://central.sonatype.org/register/central-portal/

I personally own an open source project published in the maven central and can tell you that the new portal is easier to setup and use.

Thanks.

[artemlos]

@sbraconnier

Thank you for the feedback! I'm sorry for a late reply.

We are working to remove OSSRH dependency. In meantime, it's possible to use cryptolens-android.jar, a build that does not include it. It contains the same methods except for OSSRH dependency. We needed OSSRH to generate the machine code, however, it's possible to use other ways to identify a machine that do not rely on OSSRH .

Thank you for mentioning the new portal, we'll take a look and try to publish again.

Thanks!