java packaging questions

Hi All, I package some of the DocBook XML stuff and want to package some java xslt processing tools as well, but I'm not too clear on a few policy points. Any help/suggestions would be much appreciated. Here goes: 1. Package naming, libraries vs. programs, etc. I recently uploaded an xslt pro

another packaging question

Hi All, One more: 4. Some of the upstream docbook xml packages [1] come with jar files that extend saxon, xt, and xalan2 processing functionality. (Separately.) Should I package these as java "programs", and include wrapper scripts? Thanks again, Mark [1] The xsl stylesheets, an upc

Re: java packaging questions

* Mark Johnson |I have similar questions for other packages I'd like to upload. The |arbortext catalog classes (and related extensions) that provide |catalog support for saxon and XT are an example. I could package |the base classes as "lib-arbortext-java", the saxon extensions as

Re: java packaging questions

On Monday 25 June 2001 15:53, Mark Johnson wrote: > Hi All, > > I package some of the DocBook XML stuff and want to package some java > xslt processing tools as well, but I'm not too clear on a few policy > points. Any help/suggestions would be much appreciated. Here goes: > > 1. Package naming, li

Re: another packaging question

On Monday 25 June 2001 16:28, Mark Johnson wrote: > Hi All, > > One more: > > 4. Some of the upstream docbook xml packages [1] come with jar files that >extend saxon, xt, and xalan2 processing functionality. (Separately.) > >Should I package these as java "programs", and include wrapper >

Re: java packaging questions

What about saving it as a lib and creating a sim-link to it named /usr/bin/saxon also? :) - Original Message - From: "Mark Johnson" <[EMAIL PROTECTED]> To: Sent: Tuesday, June 26, 2001 1:53 AM Subject: java packaging questions > Hi All, > > I package some of the DocBook XML stuff and wa

java packaging questions

Hi All, I package some of the DocBook XML stuff and want to package some java xslt processing tools as well, but I'm not too clear on a few policy points. Any help/suggestions would be much appreciated. Here goes: 1. Package naming, libraries vs. programs, etc. I recently uploaded an xslt pr

another packaging question

Hi All, One more: 4. Some of the upstream docbook xml packages [1] come with jar files that extend saxon, xt, and xalan2 processing functionality. (Separately.) Should I package these as java "programs", and include wrapper scripts? Thanks again, Mark [1] The xsl stylesheets, an up

Re: java packaging questions

* Mark Johnson |I have similar questions for other packages I'd like to upload. The |arbortext catalog classes (and related extensions) that provide |catalog support for saxon and XT are an example. I could package |the base classes as "lib-arbortext-java", the saxon extensions a

Re: java packaging questions

On Monday 25 June 2001 15:53, Mark Johnson wrote: > Hi All, > > I package some of the DocBook XML stuff and want to package some java > xslt processing tools as well, but I'm not too clear on a few policy > points. Any help/suggestions would be much appreciated. Here goes: > > 1. Package naming, l

Re: another packaging question

On Monday 25 June 2001 16:28, Mark Johnson wrote: > Hi All, > > One more: > > 4. Some of the upstream docbook xml packages [1] come with jar files that >extend saxon, xt, and xalan2 processing functionality. (Separately.) > >Should I package these as java "programs", and include wrapper >

Re: java packaging questions

What about saving it as a lib and creating a sim-link to it named /usr/bin/saxon also? :) - Original Message - From: "Mark Johnson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 26, 2001 1:53 AM Subject: java packaging questions > Hi All, > > I package some of the DocB