Use semantic-release to automatically release new versions

[hsluoyz]

See how we did it for jCasbin: https://github.com/casbin/jcasbin/issues/76

[shy1st]

It will takes a little time, because this project is managed with gradle.

[hsluoyz]

@shy1st @fangzhengjin why don't we use Maven like jCasbin?

[fangzhengjin]

@shy1st @fangzhengjin why don't we use Maven like jCasbin?

Maven is not as flexible and easy to use as Gradle, i haven't used Maven for a long time.

[shy1st]

Next I think we should replace bintray to nexus when release new versions of casbin-spring-boot-starter.

[fangzhengjin]

Next I think we should replace bintray to nexus when release new versions of casbin-spring-boot-starter.

ok

[fangzhengjin]

@hsluoyz Please configure MAVEN_USERNAME and MAVEN_PASSWORD in encrypted secrets.

[hsluoyz]

@hsluoyz Please configure MAVEN_USERNAME and MAVEN_PASSWORD in encrypted secrets.

Then we should move to Maven Central. @shy1st plz configure.

[shy1st]

@fangzhengjin I have finished the configuration.

[hsluoyz]

@shy1st plz release v0.1.0 to try it

[shy1st]

@hsluoyz Maybe we still need to modify some configuration to move to Maven Central. I want to use maven to replace the gradle.

[fangzhengjin]

What is the reason for migrating a project from gradle to maven?

---Original--- From: "Hongyang @.> Date: Mon, Apr 5, 2021 17:00 PM To: @.>; Cc: "ZhengJin @.**@.>; Subject: Re: [jcasbin/casbin-spring-boot-starter] Use semantic-release to automatically release new versions (#37)

@hsluoyz Maybe we still need to modify some configuration to move to Maven Central. I want to use maven to replace the gradle.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[hsluoyz]

@fangzhengjin @shy1st I think here are two things:

1. Maven Central is the package registry. Bintray will be down. So we will migrate to Maven Central.
2. Maven is the package manager tool. Does we have to use Maven to upload to Maven Central? Or Gradle can also be used? Or can we support both?

[fangzhengjin]

Of course, many large projects are built using gradle, and gradle's use of dependency libraries is also the central repository of maven.  Gradle can do the same things as maven, but it is more powerful than maven and can do things that maven can't do.

---Original--- From: @.> Date: Mon, Apr 5, 2021 17:26 PM To: @.>; Cc: "ZhengJin @.**@.>; Subject: Re: [jcasbin/casbin-spring-boot-starter] Use semantic-release to automatically release new versions (#37)

@fangzhengjin @shy1st I think here are two things:

Maven Central is the package registry. Bintray will be down. So we will migrate to Maven Central.

Maven is the package manager tool. Does we have to use Maven to upload to Maven Central? Or Gradle can also be used? Or can we support both?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[hsluoyz]

@fangzhengjin thanks for explanation! Then I think we will use the Gradle + Maven Central combination.

[fangzhengjin]

I will deal with it when I have time.

---Original--- From: @.> Date: Mon, Apr 5, 2021 17:46 PM To: @.>; Cc: "ZhengJin @.**@.>; Subject: Re: [jcasbin/casbin-spring-boot-starter] Use semantic-release to automatically release new versions (#37)

@fangzhengjin thanks for explanation! Then I think we will use the Gradle + Maven Central combination.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[shy1st]

@hsluoyz @fangzhengjin I want to use maven for the reason that I had configured semantic-release of maven central.

[fangzhengjin]

@hsluoyz What do you think?

[hsluoyz]

@fangzhengjin if you can setup semantic-release on Gradle finally, I'm OK with both. Or we can keep both Gradle and Maven POM files in the repo. What do you think?