Release?

[fkleedorfer]

Just to let you know, it would be greatly appreciated if a new release was published!

Thank you so much!

[atextor]

Hi @fkleedorfer,

sorry for the late reply (just returned from vacation). I also saw your comment in the last merged PR. I'd love to do a release as soon as possible, but as you correctly noted, this implies switching the Maven Central deployment setup. In fact, this is already prepared as part of atextor/owl-cli#20 where I intend to merge the owl-cli and turtle-formatter projects (in order to speed up releases) and also do the switch to Maven (hence allow using the new central-maven-deploy-plugin). The only reason this is not done yet is that I'm short on time. I plan to have a look at that and do the corresponding release in the next week.

[fkleedorfer]

Just to let you know, if you got around to this, I am thinking about another PR to make ordering of blank nodes even more deterministic (it is still a problem).

[atextor]

Incidentally, I was able to pick up work on this some days ago and am nearing a point where owl-cli and turtle-formatter are merged into one project, which also updates to the new Maven deployment setup. This is taking (a lot) longer than anticipated, but I wanted to let you know that work is not completely stalled.

[fkleedorfer]

Hi, good to hear it! Does that mean you are discontinuing this artifact?

[atextor]

Technically yes, at some point. But nothing is lost. My plan is as follows:

• Create a working branch in the owl-cli project (done)
• Switch the project from Gradle to Maven and make it a multi-module project (done)
• Transfer the contents of turtle-formatter into a new submodule in the owl-cli project while keeping the original commits intact (as described in this article) (done)
• Update the project deployment setup from OSSRH to new Maven Central deployment scheme (done)
• Create a new Github organization to host the resulting project, to better reflect that it's not strictly a personal project any more: Cool RDF (done)
• Update the Maven coordinates and package names accordingly: owl-cli -> cool-rdf-cli, turtle-formatter -> cool-rdf-formatter (done)
• General clean up, and update dependency versions (in progress)
• Move the atextor/owl-cli Github project to cool-rdf/cool-rdf (todo)
• Update docs to reflect the merge etc. (todo)
• Move remaining open issues from turtle-formatter to cool-rdf (with a label to distinguish from other topics) (todo)
• Archive turtle-formatter (todo)
• Do a release for cool-rdf (todo)
• Pick up work on actual fixes and features (todo)
• Maybe: Send PR to spotless to update the Maven coordinates

At the end of this process, turtle-formatter lives on as one module in the cool-rdf project. Releases are going to be done for all components of the project at the same time, so new turtle formatting features are also automatically available in the CLI.

[fkleedorfer]

Things would be easier downstream if there were no breaking changes (maven artifact coordinates, package/class/method names). Making the spotless plugin was a bit of a finicky thing because it's all done via reflection. But of course, if keeping turtle-formatter as is and depending on it from your new project is not an option, there will be a way, somehow.

Given that there will be a formatter one way or another, I'll work on the blank node ordering and make a PR here