W3C home > Mailing lists > Public > xproc-dev@w3.org > July 2012

Re: Calabash/Calumet in Maven ? (was: [saxon] Saxon-HE on Maven)

From: Romain Deltour <rdeltour@gmail.com>
Date: Thu, 12 Jul 2012 10:07:24 +0200
Cc: Inigo Surguy <inigo.surguy@gmail.com>
Message-Id: <05D97BFD-CD47-4519-8540-5EFB86D7A601@gmail.com>
To: XProc Dev <xproc-dev@w3.org>
FYI we have uploaded a version of Calabash 1.0.3 for Saxon 9.4 to Maven Central under our own group ID:
http://search.maven.org/#artifactdetails|org.daisy.libs|com.xmlcalabash|1.0.3|jar

The version is built from the sources, the only difference is in the MANIFEST, where I tweaked a couple OSGi headers (which I have not contributed back to Norm's master branch yet).

The POM used to build the Maven release is pretty simple: we fetch the sources from GitHub, apply our custom patches, build it with an antrun call, and attach sources and javadocs for the "release" versions. Norm: if you want some assistance in doing the same for the official version, I can help. :)

Romain.


On 12 juil. 2012, at 03:37, Leif Warner wrote:

> You should be able to publish without maven, too, right?  Just upload a signed artifact (jar), and a pom.xml?  That could be done in an ant task, right?
> -Leif
> 
> On Tue, Mar 13, 2012 at 1:55 PM, Inigo Surguy <inigo.surguy@gmail.com> wrote:
> Pull request for putting Calabash in Maven Central:
> 
> https://github.com/ndw/xmlcalabash1/pull/34
> 
> Inigo
> 
> On Sun, Mar 11, 2012 at 8:25 AM, mozer <xmlizer@gmail.com> wrote:
> > Dear all
> >
> > Now that Saxon is in Maven, any chance to have Calabash and Calumet in Maven ?
> >
> > Xmlizer
> >
> >
> > ---------- Forwarded message ----------
> > From: O'Neil Delpratt <oneil@saxonica.com>
> > Date: Fri, Mar 9, 2012 at 6:14 PM
> > Subject: Re: [saxon] Saxon-HE on Maven
> > To: saxon-help@lists.sourceforge.net
> >
> >
> > 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
> >
> 
> 
Received on Thursday, 12 July 2012 08:08:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 12 July 2012 08:08:07 GMT