Java version 2.12 availability in central maven repository

[skarzhevskyy]

Hello
Thanks for the excellent library. Are there intention to place the latest version to central maven repository?

[jzhang2004]

Hi, Thanks for the suggestion. Since vtd-xml is open source.. there should not be any hindrance in placing it in whatever repository you see fit as long as it abides by the GPL rule...

Cheers,
Jimmy

On Tue 05/01/16 7:22 PM , Vlad Skarzhevskyy [email protected] wrote:

Hello
Thanks for the excellent library Are there intention to place the
latest version to central maven repository?

—
Reply to this email directly or view it on GitHub [1].

Links:

[1] #1

[sofiageo]

I've acquired credentials to deploy artifacts in the central maven repository for vtd-xml. However it is my first time doing so, so It might take a while. I will try to deploy the artifact tomorrow and update this issue.

[jzhang2004]

oh, thanks... I would have done it if I know how to...

[sofiageo]

It looks like it's ready.
http://search.maven.org/#artifactdetails|com.ximpleware|vtd-xml|2.12|jar
http://central.maven.org/maven2/com/ximpleware/vtd-xml/2.12/

The "problem" is that at the moment I will have to maintain the package and I don't know if I will be available to do it fast, or if I will even know about any updates that happened. So it would make sense if the author of the software would be able to do it. While I chose the manual way of bundling and creating the artifact, the process can be automated by a maven plugin. So if you decide to use maven for future versions, it could take some effort in the beginning but then you will be able to deploy it just by using one plugin command.

[skarzhevskyy]

Thanks,
I have seen it yestarday and switch my build to use it. Worked as expected.
On May 12, 2016 10:12 AM, "George Sofianos" [email protected]
wrote:

It looks like it's ready.
http://search.maven.org/#artifactdetails|com.ximpleware|vtd-xml|2.12|jar
http://central.maven.org/maven2/com/ximpleware/vtd-xml/2.12/

The "problem" is that at the moment I will have to maintain the package
and I don't know if I will be available to do it fast, or if I will even
know about any updates that happened. So it would make sense if the author
of the software would be able to do it. While I chose the manual way of
bundling and creating the artifact, the process can be automated by a maven
plugin. So if you decide to use maven for future versions, it could take
some effort in the beginning but then you will be able to deploy it just by
using one plugin command.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#1 (comment)

[jzhang2004]

Could you guys help move 2.13 into the maven as well when it comes out?

[sofiageo]

I can help with that. Is it already available?

[jzhang2004]

informally released yesterday only for java... should be final in a few days...

[sofiageo]

I have updated the package. You can find it here: http://search.maven.org/#artifactdetails|com.ximpleware|vtd-xml|2.13|jar

I haven't tested if it works yet. Also I noticed that the examples are missing compared to the previous version. If you need me to update again later just tell me in this issue.

[jzhang2004]

I have got request to upload 2.13_3 version to central maven for that particular unicode fixes. Could you help me do it? I would be glad to do it if you could give me the instruction.

[sofiageo]

Hi, I never realized there were any new releases. Should I create a maven package for the latest one - 2.13_4 ?

[sofiageo]

I have created a maven release with artifact Id: 2.13.4. It is already synced to maven central.
Since the javadoc was missing from the release, I have used the javadoc from version 2.13.

The steps to do a release are somewhat complex to write here, but I'm basically following this guide: http://central.sonatype.org/pages/ossrh-guide.html

I am using the manual staging bundling procedure since I think it is the most simple one. So to do one release (after the first project repository is setup by sonatype - which already is at this point), you have to do the following:

• Create a pom.xml with information about the project and the developer (it can be downloaded from maven central in case you don't have it)
• Follow the bundle requirements - http://central.sonatype.org/pages/requirements.html
• Follow the bundle creation guide - http://central.sonatype.org/pages/manual-staging-bundle-creation-and-deployment.html
• Verify the upload was OK and release.

To be honest I'm OK with helping on this since it's not a very difficult procedure, but you might be able to automate this using an ant or maven build in case you want to do it yourself.

[jzhang2004]

Thanks I will try to upload this next time .. hope it isn't too difficult