Congratulations and thanks very much.

-alan

On Mar 9, 2012 6:16 PM, "O&apos;Neil Delpratt" <oneil@saxonica.com> wrote:
Thanks very much to all those who gave helpful advice on Saxon-HE and maven. I managed to deploy Saxon-HE 9.4 to the central repository, which should now be available to maven users. Please see:

https://oss.sonatype.org/content/groups/public/net/sf/saxon/Saxon-HE/

As suggested in section 7c in the setup guide below, I used the ant script for the deploying. I also found the following useful when uploading the required files and releasing the project:

https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository

kind regards,
O'Neil





On 07/03/12 14:58, O'Neil Delpratt wrote:
RE: Creating a Saxon-HE Maven project and deploying it to the Maven Central Repository

Dear All,

We have had over the years user requests for making the open source Saxon product available via Maven and I have assigned the task to make it happen.

I am pretty new to Maven and have spent several hours trying to get Saxon-HE deployed to the Maven central repository and still not have had much success. I am hoping that someone on the mailing list has had better success with Maven, which can help or at least point me in the write direction with some useful advice.

First a question about requirements: is there a need to deploy in such a way that Saxon can be built from the Subversion source repository, or do we only need to deposit the JAR file?

I have read many guides, forum posts and the Maven website itself ( http://maven.apache.org), but it all seems overly complicated and difficult to find the right information. However I found a guide which was somewhat easier to follow:

https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

I have followed the general setup of creating a POM.xml file with the project configuration. If I can get some interest in this topic I will issue the POM.xml file.

Most of the documentation suggests maven needs to build from the source, which isn't easy given the complexity of the Saxon build. Therefore I included the ant plugin which allows us to build the product in an ant script wrapped in Maven.  I have reached the point where I need to deploy the product and it's not tying together the ant build and the compiled code.

It may turn out that I am doing totally the wrong thing. Any offers of help are welcome.

Kind regards,

--
O'Neil Delpratt
Software Developer, Saxonica Limited
Email: oneil@saxonica.com
Tel: +44 118 946 5894
Web: http://www.saxonica.com
Saxonica Community Site: http://dev.saxonica.com


------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/


_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/saxon-help 


--
O'Neil Delpratt
Software Developer, Saxonica Limited
Email: oneil@saxonica.com
Tel: +44 118 946 5894
Web: http://www.saxonica.com
Saxonica Community Site: http://dev.saxonica.com

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/saxon-help