[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Classpathx-xml] Re: classpathx xml ...

From: Nic Ferrier
Subject: [Classpathx-xml] Re: classpathx xml ...
Date: Wed, 11 Jul 2001 21:03:15 +0100

>>> David Brownell <address@hidden> 11-Jul-01 7:05:00 PM >>>

   I think the only thing I have left to import is the call filter
   and servlet hooks for the XML pipeline stuff.  The call
   filter should compile anywhere as I recall, but the servlet
   needs build environment updates (which will complicate
   any source release substantially).

Don't undertand, can you elaborate?

Nic said:
     I am happy to knock up a basic page for jaxp 
     and to run javadoc on the classes.

Dave said:
   That'd be a help if you could do that much and put 
    it up on the site. There's a "make javadoc" target already.
    Doesn't include all the "transform" classes, though that'd 
    be easy enough.  And it might be good to get some 
    "package.html" files into the JAXP interfaces.

Ok. I'll put up a page over the weekend.

   I hope the javadoc doesn't have to go into CVS!  
   Do CVS updates to the site automagically get 
   published, or is that a manual step?

commiting to the webcvs causes an instant change on the webserver. So
yes, the javadoc will have to go in. It can always be imported. Leave
it to me, I'll handle it.

   Actually for the very first distribution I might be happier 
   saying "get the source from CVS".  I'd tag it so folk can 
   get that version.

We can release an ALPHA like that. But BETAs and RCs should be
packaged as a tar file.

   Sounds about right, I'm mostly unclear on the mechanics.
   If updates to CVS get automatically published, that's easy 
   -- except for the case of javadoc.

I don't understand why you think javadoc is a problem.

Anyway, I'll handle the details of the initial upload.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]