Release to maven central

rhoegg commented 3 weeks ago

This is a proposal to change the license and publish to maven central similar to the other Anypoint Cloud modules. I am proposing:

changing the LICENSE file to Apache 2.0
adding Mathias as a developer in the pom.xml
Updating the pom.xml with the release configurations needed for maven central release
Changing the groupId to cloud.anypoint
Releasing to maven central
Updating the README to offer users the option of using the maven central version, as well as forking and publishing to their own exchange

rhoegg commented 3 weeks ago

I will be happy to help do some of these steps, as I currently have the publisher rights to maven central cloud.anypoint groupId.

Thoughts @mtransier ?

mtransier commented 2 weeks ago

I like the idea. What I am not sure about is the license update, as I am not a lawyer ;-). Do you have experience with it?

What would be your proposal regarding the deploy script? If we change the groupId, we either have to update the deploy script or remove it completely. Anyhow, it does not provide too much value, a short guide in README could do the same - so we could remove the script.

We could also get rid of the two-level structure. This is something, I usually do for each project where I am using it.

anypointcloud / json-logger

Release to maven central #1