release from github

[adichad]

please make a release in the 2.x line from current github master, and publish artifacts to maven-central to reflect the changes done since migration to github.
we would like to use Mallet with Apache licensing, which was not part of the 2.0.8 release in 2016, but is so in the master branch.

[MarceloLaser]

I second this request. We currently use a local copy of Mallet in order to use the most recent version due to some new features which are required for our work. Having it up on maven-central would facilitate this greatly. Thank you all for the great work on Mallet!

[csavelief]

I created a Github Workflow that automatically build and deploy the master branch as a package on each commit.

@mimno Maybe you could publish the Package to GitHub Packages ? There is a doc here.

[mimno]

I'm happy to do this, but it would be great to get help with more specific directions! I got to this page for maven and I can't easily see what I need to do. Reading maven docs is just about my least favorite activity.

[csavelief]

@mimno reading the doc in detail, I discovered I did not need to setup a GITHUB_TOKEN because I had just enough access rights :-) It should be OK by now. Each commit will now trigger a new build/deploy to GitHub Packages cycle. Unfortunately, I was not able to execute the build using a more recent JDK due to this error :

Error:  Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.3:compile (default-compile) on project mallet: Compilation failure
Error:  /home/runner/work/Mallet/Mallet/src/cc/mallet/types/Metric.java:[17,8] cannot access java.lang.Object
Error:    bad class file: /modules/java.base/java/lang/Object.class
Error:      class file has wrong version 63.0, should be 53.0
Error:      Please remove or make sure it appears in the correct subdirectory of the classpath.