My comments were merely about setting up a repository of quick fix examples, I wasn't proposing Maven goals etc.
However as with most people using jelly, I suspect the first thing done is go through all the tag sub projects, build their jars
and throw them all in one directory. A Maven goal which did that would be good.
Maybe also including in the release the all important get everything script
E.g.
"CLASSPATH=
for file in c:/jars/*.jar
do
#echo $file
CLASSPATH=$CLASSPATH\;$file
#echo $CLASSPATH
done
CLASSPATH=$CLASSPATH\;.
#echo $CLASSPATH
java -cp $CLASSPATH org.apache.commons.jelly.Jelly $*
"
About startup with cvs or source distribution... what have you been proposing here ? There has been an amount of questions related to this in there and I have the real impression there should be an effort in the direction of large maven goal that can generate/copy jars needed for any jelly file...
Paul
Andy Paul wrote:
Bill,
I'm afraid the attachment didn't seem to transfer ok.
Thanks for everyone's interest, I know there's lots of stuff in test cases, mailing lists etc, what I aim to do is start up an easy access area of information to get started without the need to do all that leg work i.e. a new jelly user quick start.
Being a new-ish jelly user I'm making notes of the things that trip me up and/or I discover. It's all out that but it sure would be nice for a new user to get a cookbook /crib sheet to speed them along their way, I'll put forward a few snippets for feedback in the next day or so.
Andy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
