You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I have an outstanding pull request - it's nothing major, just a minor addition to allow loading XSDs from resources on the classpath (e.g. XSD files bundled as resources in JARs on the classpath).
But if you merge that pull request, would you consider bumping the version number of Ontmalizer and also releasing to Maven Central from now on? That would make it super-easy for us here to pick up the latest pull-request changes, while also making further updates much easier to consume (i.e. we'd just need to bump the dependency version in our project POMs (which of course point to Maven Central), and everything else would 'just work').
Cheers,
Pat.
The text was updated successfully, but these errors were encountered:
I just merged your updates. I further updated the source code a bit, including your modifications. In addition to InputStream reading support for XSDs, I added it for XMLs and also URL reading support for both. I updated the version to 1.0.1 as well.
I am looking into releasing to Maven Central, actually to Sonatype repo. Initial setup requires some manual steps, approvals and hence takes some time. I will let you know when it is completed.
Thank you for your continuous interest in ontmalizer. Cheers,
Hi Mustafa,
So I have an outstanding pull request - it's nothing major, just a minor addition to allow loading XSDs from resources on the classpath (e.g. XSD files bundled as resources in JARs on the classpath).
But if you merge that pull request, would you consider bumping the version number of Ontmalizer and also releasing to Maven Central from now on? That would make it super-easy for us here to pick up the latest pull-request changes, while also making further updates much easier to consume (i.e. we'd just need to bump the dependency version in our project POMs (which of course point to Maven Central), and everything else would 'just work').
Cheers,
Pat.
The text was updated successfully, but these errors were encountered: