> >From: Stefano Mazzocchi <[EMAIL PROTECTED]>
> >My ideal solution?
> >
> >cvs checkout xml-cocoon2
> >./prepare.sh
> >./build.sh dist
> >
> >I personally don't care what "prepare.sh" does and I'd be ok in
> >requiring Ant to be installed on the machine in order for this to work.
I'm "working" on this using simply a cvs task or a simple http download.
> >Also, I'd be ok in centralizing the JAR repository and have to pass
> >*thru* the PMC in order to have jars placed in that repository (could be
> >a CVS module or anything else, I don't care, as long as prepare.sh can
> >get to it)
This is a problem now. I want to make this before POI goes public, but
ATTOTW I don't know where to get the jars. The bin or src dists are full of
documentation and other jars, so IMHO it's overkill to ge those just to
unpack them and get a file. Currently I'm getting them from the CVS modules
of projects that use it in their libs, but of course it's not a solution.
> >Ok, let's see, here is how prepare.sh could work:
> >
> > 1) post a request with the project name and version number, obtains a
> >list of jars and their location (depending on IP address, it could even
> >get a mirrored location)
Being this a script to download jars, it's easier just to specify them in
the ant task.
> > 2) depending on user parameters (./prepare.sh --get-core-libraries-only
> >--get-all-libraries etc...) it goes on the net and downloads the
> >libraries (checking into the repository if they are uptodate)
Each parameter could be a separate ant task.
An alternative is to distribute an ant installer for all Apache Java
projects like cygwin does.
I think it's even better.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
These are the days of miracle and wonder...
...so don't cry baby, don't cry...
Paul Simon
---------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
