Nick Chalko wrote:
And why not: DISPLAY the damn license and require the user to type
"I do understand the terms of this licence" and click somewhere
( that may also cover the requirements of some of the packages ).
Or even better, if it's a GPL license Ruper should require the user
to type "I understand that all the software I ship that is bundled with
this jar will have to be GPLed". ( and if he types something wrong, he'll have to type the whole thing again :-).Adding dependencies should not
be easy.
We certainly need a way to indicate to the user that that a jar is
a build-time dependency, a runtime required dependency or an optional
runtime dependency.
Actually there are several usecases here to describe.
But this is why we need a new project to hash all this out.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
