Le 13 juin 05, � 14:10, Brett Porter a �crit :
I'm highly confused :)
Sorry was answering to the mail of the 11th.
I thought we were in agreeance of distributing it as an app, with a
std set of taglibs, which is the RC that is prepared for review. Can
you check that out and comment on that?
Yup... underway.
My first comments on the binary:
- packaging is simple and straightforward, that's good!
- last line of the sh script should have "$@" around instead of $* I
believe
(otherwise you don't allow spaces in parameters, should I commit
this?)
- do we not want to include an "endorsed" directory since it would
allow to circumvent the shipped parser and a possibly too old version
of xalan??
- I would resign to take in account an existing CLASSPATH variable in
the script ... it tends to add unpredictability. People can still hack
the script if they wish.
- the README is for the source... we need to have one for the binary,
or?
It should include:
- which taglibs are included (not sure of the list, looks like xml is
not for example)
- which examples can be run
--> about this, I feel we should include examples, or maybe examples
with URLs ??
- how to download (and install) more taglibs (if possible)
--> about this, I fear forehead will not support this... why not use
shell
script to define the classpath using a command that takes all jars
in the
lib directory ? (or let it be with extensibility and refer to the
source for it,
not very nice)
... just to catch up quickly on talk exchanges about the documentation
inclusion: I think we should include the produced web-site in both the
source and binary distribution since it cannot be built with either of
them.
Sorry for the late replies.
paul
Paul Libbrecht wrote:
| How would joe-blo do when unpacking:
| - trying out examples ?
| They're all indicated with maven... better distribute the source
right away or repack...
I didn't understand this, sorry - there is a source distro up there
already...
| - starting to embed right away in an existing application ? There
was probably a download earlier...
Again, not sure what you are aiming for here.
| - 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.
the JavaApp plugin could just as easily produce this fat jar - not
sure what you are going to do with JNLP though. This all sounds way
beyond what is needed for the current release.
| - a (large) set of jars and some sh and bat scripts to use and run.
| I can help on the sh scripts.
Already done.
| Possibly, that could be modular, e.g., using a build.xml that
downloads.
Not sure what you are getting at here either, sorry.
|
| PS: there's this "install" target which I, honestly, never used...
maybe someone can report usefulness there ?
its dist + copy, nothing exciting I could see
| PPS: download volume of releases is cheap, it's mirrorred as opposed
to ibiblio for example!
Ibiblio is mirrored too, but not as widely. (Just a European and
Australian mirror).
Anyway, the general impression seems to be it is ready. Can you please
review RC4 and vote based on that for now?
Thanks,
Brett
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCrXepOb5RoQhMkRMRApaFAKDERx8ISYv+Tnako8k6dQprxNeu9wCgnEzD
1GW1tOZL7p50DD+XAZZOJqw=
=RBpm
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
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]