Closed hsluoyz closed 3 years ago
The following project does not use "casbin" for groupId config.
Reserve current version jCasbin, and make further update in the Casbin may be a good idea.
@Zxilly what do you mean?
@hsluoyz Keep this version of jCasbin
for compatibility with other module, but no longer develop on this.
But create a new repository named casbin
,and make further contribution on that.
@Zxilly the github repo doesn't matter. The commits remain anyway. I'm talking abou the Maven central. We will freeze the new versions under jcasbin and release new versions with casbin.
@shy1st I don't know how Maven Central treats such a situation. Is Casbin a new package than jCasbin? If yes, then we are releasing new package.
In maven central, the groupid we set is always " org.casbin" , does not exist "org.jcasbin". please see https://mvnrepository.com/search?q=casbin.
@shy1st In the Java side (code, etc.), there should be only "casbin", there's no "jcasbin". "jcasbin" is only used in this repo name and also in Casbin official website.
@hsluoyz I think this is mainly reflected in the setting of groupid in POM files. In some projects, the groupid is set as org.jcasbin(eg:vertx-casbin), which is incorrect. This will cause an exception when published to the central repository(In fact, vertx-casbin has not published to the central repository).
@shy1st good, then fix those wrong group IDs.
trying to work on this
@shy1st , let me introduce @Kininaru , @Kininaru is our technical writer for Casbin docs & website. He also has some interest in languages like C++, Java, etc., so he will hang around our repos. Hope @Kininaru can be a help for you!
@Kininaru Welcome!
@Kininaru @hsluoyz I think all the project in jcasbin organization has renamed. Now we can close this issue.
Great!
We will rename to "casbin" for everywhere including the Maven package manager, except this GitHub repo name to differentiate with Go's Casbin.