> > Now, I like the repository idea. In fact, it's the primary reason I decided > > to use Merlin in one of my latest apps. However, there are other times when > > I don't really want to use a repository. In fact, sometimes I want to be > > able to deliver a single large jar file that includes everything I need. > > Can we dig into this a little further. In particular - I'll like to > known what the underlying (real) objective is: > > 1. a "sealed deliverable" (i.e. something that the client > cannot tinker with) ? > 2. simple installation without network access ? > 3. something else ?
Here it comes again. - I don't want X - Why? Whats the underlying (real) objective to not want X? -- hammett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
