Gianugo Rabellino wrote:
Kevin Ross wrote:
I'm somewhere in between, I'd like to see both happen:
1. I have always wanted a standalone (from a binary distribution). This is the way new users will probably utilize the system, hence, I believe doing something like this is an absolute necessity.
+1. It's more than usability, it's a different feeling: something that stands on its own instead of being "just" a webapp.
2. I also want a .war (from a binary distribution). More advanced users, or those with current supporting architectures are likely to prefer this.
Which is supported and possibly even recommended under some setups. It might be seen then as a scalability spot.
I also think creating a binary w/Jetty should be a product of a build, not by having Jetty in the main trunk
Please tell me more on this. I'm not really getting it... do you mean that there might be a target that downloads Jetty somewhere, creates a bundle with Xindice and prepares a sort of distribution? If that's the case... well, I don't really see a difference between what you call "deployable" and "standalone". As of now, supporting Jetty is just a matter of writing a ridicolously simple configuration file and point it to the war, nothing else is needed. But maybe I'm not getting your point.
My point is, regardless of size, no extra jars should be forced down the throat of every user of Xindice. Maybe I don't understand, but as far as I can infer, you need to include the jetty jar and were suggestion it's inclusion in CVS. As far as including in the build, I do believe it would be just as easy to have this file in the ant build using the <get> task. Yes, it will point to a particular file via url, but what is the difference if we are just going to download the particular file and put it into CVS? The binary standalone distribution should include the jar, and be the result of the build. I don't see a problem including the config somewhere in CVS though.
I publish my own component build, and utilize it with a many build wrappers for different projects, calling <get> in the init target. It will only get the file if it is necessary, and works quite well.
-Kevin
Ciao,
