On 5 Dec 2003, at 05:54, Diego Bragato wrote:
Hi all,
After a long discussion with Oliver (thanks Oliver ...) we managed to arrive at the conclusion that the build.xml needs refurbishment in the release target.
This is heavily significant to everybody: developers users and community.
As my understanding we all use slide in a large quantity of flavors and fashions. And as long as there are various needs around, it needs a bit of discussion to you all.
What binary distributions you want to produce out of the release target in the build.xml ?
The actual old way of producing jakarta-slide.2.0.0.tar.gz is a tomcat deployed in a non exactly standard way with a lot of old code.
I agree. I dislike this myself.
There can be the need for a separate binary for the distribution of 1 the slide client (this would be useful to my personal project)
I already proposed the cration of a new module for that. Ah, btw, after you guys nominated me committer, I've been elected in the Jakarta PMC, so that makes things a little easier as I can influence the PMC directly now (that that's why I accepted the nomination).
2 out of the box build with tomcat 4.x (please propose me a version) ideal would be latest (this would be useful to my personal project)
3 out of the box build with jboss (project www.jbpm.org has one and it's really nice) (this would be useful to my personal project)
4 a binary build with the needed wars and stuff for being deployed in a generic app server (see for example jetspeed project) maybe a build.xml can be needed for doing the deployment
I think that #4 would solve #2 and #3. As for #3, this is not possible as the ASF has a policy not to distribute LGPL software.
5 a zip for the sources
Yes.
6 a zip with the webdav-test suite
Agreed. I would go as far as proposing another CVS module for the test entirely. So that would make three CVS module
jakarta-slide jakarta-slide-client jakarta-slide-tests
which would increase isolation and allow faster development.
There can be others (for example producing a ear file) but really there are various pieces of informations that you all have and that I need to get a precise direction in the work.
no need for j2ee stuff, slide is just a servlet, let's keep it that way.
The second task, after we have one or more decent (voted and approved) binary to distribute, is to have it available as nightly build on the apache web and share it to the community (we will have to make some marketing of slide) so that other people can start to use it and test it.
yes, this is general practice.
This way the slide project will be appreciated by other people for the real value it has, and I think this is the most important thing.
+1
-- Stefano.
smime.p7s
Description: S/MIME cryptographic signature
