To come back to the topic, it would be nice to ask oneself how one
intends a "normal user" of Jelly to unpack a distribution and start
using it.
I, as probably most, tried directly from source.
How would joe-blo do when unpacking:
- trying out examples ?
They're all indicated with maven... better distribute the source
right away or repack...
- starting to embed right away in an existing application ? There was
probably a download earlier...
- how about the "fat-jar" archive that can be produced with the
maven.xml... that's a run-out-of-the-box solution. Using JNLP or some
other mechanism could also help. Probably basing on forehead would
produce another such which would be cleaner since it would, itself,
contain jars.
- a (large) set of jars and some sh and bat scripts to use and run.
I can help on the sh scripts.
Possibly, that could be modular, e.g., using a build.xml that
downloads.
Thanks for comments.
paul
PS: there's this "install" target which I, honestly, never used...
maybe someone can report usefulness there ?
PPS: download volume of releases is cheap, it's mirrorred as opposed to
ibiblio for example!
Le 10 juin 05, � 22:26, Paul Libbrecht a �crit :
Careful, Ant's functionality is rich already as is so their
"third-party" imports is somewhat less necessary.
From your proposal, I understand that even ant.jar would not be
included...
paul
Le 10 juin 05, � 01:08, Brett Porter a �crit :
The other approach is to include all taglibs, but none of the
dependencies, and add instructions on how to find them - like what
Ant does.
I will try this, pulling in all the latest releases rather than
current trunk code - like Maven1 does with its plugins.
---------------------------------------------------------------------
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]
