W3C home > Mailing lists > Public > xproc-dev@w3.org > April 2015

Re: How many repos?

From: Ari Nordström <Ari.Nordstrom@condesign.se>
Date: Tue, 07 Apr 2015 09:55:02 +0200
Message-Id: <5523A976020000730001DD12@grpw.condesign.se>
To: "Norman Walsh" <ndw@nwalsh.com>,"XProc Dev" <xproc-dev@w3.org>
Hi Norm,
Sounds reasonable to me. I do include Calabash in an authoring
environment for a client and a smaller footprint would be nice and
appreciated. They don't use FO so in that case there's a lot to be
gained. Most of the other places where I use Calabash do use FO, but
including an extra classpath doesn't sound too bothersome.
What I do wonder about is the XProc/Calabash module for eXist. It is
built using the whole kit and an older version at that, and perhaps
someone who knows more can explain if this would affect anything.
All the best,

Ari Nordström
Senior Consultant 
Condesign Operations Support AB
Phone +46 31 744 17 91
Mobile +46 736 000 333
Email ari.nordstrom@condesign.se 
>>> Norman Walsh <ndw@nwalsh.com> 2015-04-07 03:06 >>>
Hello world,

The modulization work I did recently makes it pretty easy to bundle
XML Calabash extension steps in separate repositories. Just put all
the relevant jar files on the classpath and you're done. It'll all
"just work".

I've separated some steps out into separate repositories already:

* The MarkLogic XCC steps
* The RDF steps
* The DiTAA step (to resolve a weird build issue that I later
  discovered was caused by PlantUML including an older version
  of the DiTAA classes)

Those are all extension steps and I'm tempted to break out a few more:

* cx:metadata-extractor
* cx:send-email
* cx:plantuml

Those are candidates mostly because they each have further
dependencies so removing them makes the XML Calabash release smaller.
They're also probably not widely used.

More controversially, perhaps, I'm tempted to break FO processing out
into a separate repository. FOP in particular has a lot of
dependencies; moving it into a separate repo would reduce the size of
the XML Calabash distribution by almost 25%. I'd probably move CSS
processing out as well, just for parity.

Practically speaking, this would mean that if you didn't also download
the FO jars, you couldn't do FO processing with XML Calabash. (The
p:xsl-formatter step would fail with a class-not-found exception.)

One could go all the way to the absurd and bundle every step
separately, but that'd clearly be overkill.

I'd be intersted to hear with users and developers (especially
developers that bundle XML Calabash into other products) think about
the "multiple repos" question.

                                        Be seeing you,

Norman Walsh
Lead Engineer
MarkLogic Corporation
Phone: +1 512 761 6676

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information.  If you have
received it in error, please notify the sender immediately and delete
the original.  Any other use of the email by you is prohibited.
Condesign AB, 556255-8313, säte Göteborg; Condesign Automation AB,
556271-3676, säte Göteborg; Condesign Engineering AB, 556469-2092 säte
Göteborg; Condesign Infocom AB, 556453-7172, säte Ljungby; Condesign
InfoProductions AB, 556385-4255, säte Linköping; Condesign Operations
Support AB, 556307-1231, säte Göteborg.
Received on Tuesday, 7 April 2015 07:56:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:17:23 UTC