>> - is it worth making a special target for building a minimal > Cocoon >> containing a very minimal set of features? > > May be better documenting the process will help. It boils down to just > couple of steps: > 1. build clean > 2. rm all optional libs > 3. build -D....
Of course, improved documentation helps, and it's coming, but... 1. I don't think it's a good idea to have new users rm jars. Even if designated optional, as in the head-release, it takes time to figure out the features these jars provide. Also, some users will inevitably make mistakes (like deleting jars they may need later). It's just not intuitive to remove a feature by removing a jar. Most people would expect to make decisions like this in an interactive build session or config file. 2. This build experience makes an important first impression on those evaluating Cocoon. We should make it as simple as possible -- if that's what a user needs. I'm not implying that advanced users need this. 3. Building, even without optional jars, still leaves the sitemap overwhelming for new users. I think Konstantin is addressing that issue as well. Diana > > Vadim > > >> Regards, >> Konstantin Piroumian >> _________________________________________ >> Konstantin Piroumian >> Lead Developer >> ICQ#: 2297575 >> ( Work Tel#: +7 095 795 0520 * 1288 >> + More ways to contact me >> i See more about me >> _________________________________________ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
