Folks,
ant elder wrote:
On Jan 10, 2008 11:13 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
<snip>
My earlier idea which seems to have got a little lost in the debate
was for the wwebapp to contain a minimal Tuscany bootstrapper that
pulls in the needed jars from wherever the full runtime is installed.
So webapps wouldn't contain the whole Tuscany runtime, but would use
jars from a runtime installed somewhere that the webapp bootstrapper
could find.
Is that very similar to what we had back in M2 with the way extensions and
dependencies got pulled in at runtime by Maven, or am misunderstanding what
you're suggesting?
...ant
PLEASE PLEASE PLEASE let's NOT do that.
That Maven go-get-the-dependencies-at-runtime approach was a total
nightmare. Keep it simple - allow the user to download everything they
need as a single "binary".
The only thing worth doing that would be "smart" is the idea of
installing the binary in a single location which could be shared by a
variety of runtimes. But for me, the important thing is to allow the
simple setup of a runtime so that it will run SCA
applications/contributions. Multiple copies is OK in the short run, if
that makes the user experience simple.
Yours, Mike.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
