On Monday 24 March 2003 18:14, Stefano Mazzocchi wrote: > Niclas Hedhman wrote: > > BUT, a cocoon-sample.war would be great for "Introduction". I.e. Download > > that, drop it in your servlet container, and you have Cocoon's samples > > running. I'm sure "build process" scares away some users instinctively, > > especially the "life-without-a-compiler-windows-inflicted-mindset" > > (potential cocoon) users. > > If we then have a page describing how to build the "samples", it would > > again lower the "perceived complexity" a bit, allowing the "newcomer" to > > build it to ease confidence. Call it "microstep learning", as it is the > > best way... > > Hmmm, I was thinking about adding build profiles the other day.. > something like: > > ./build.sh --profile=[profile] webapp > > that will override the build properties from > > [profile].properties > > that include several different configuration properties that drive stuff > like > > - inclusion/exclusion of stuff from the webapp > - development/production version (debug on/off, security low/high) > > and stuff like that. > > What do you think?
GREAT... The concern I have is not so much "the build is difficult to use", but more of "Ohh, I have to build it, never mind then..." reaction, which will deter a significant amount of "interested parties". I just like to see the "low entry" remain, preferably as someone suggested, with the Jetty bundle. Niclas
