Here is the draft interface to the proposed tool discussed in the previous
message. (This is written in POD since that will let me translate it
directly into a manual page if this looks like a good way to proceed.)
=head1 NAME
java-deploy-webapp - Deploy a Java web application to a web container
There seemed to be enough interest in my proposal for how to handle web
application packaging that it was worth writing it up as a somewhat more
formal proposal so that we could look over all of the implications. The
DEP system was designed for that, and includes the assumptions that
proposals can
On Tue Aug 24 18:07, Peter Collingbourne wrote:
> > I don't like either solution very much. Of the two, what I would prefer is:
> >
> > - version clojure itself
> > - have clojure be a metapackage depending on the current version
> > - things b-d on clojure and depend on clojureX.Y, with AOT co
Hi Matthew,
On Sun, Aug 22, 2010 at 10:02:04AM +0100, Matthew Johnson wrote:
> There's probably also a third: python has a version-dependent compiled format,
> which is created when you install the library (I think) and (presumably)
> rebuilt when you upgrade python. We could do something like tha
On Mon, Aug 23, 2010 at 03:19:47PM +0100, Peter Collingbourne wrote:
> If a library/app B needs AOT and depends on a library A which is not
> AOT compiled, what does the linkage look like from B to A? Is it a
> direct call? IOW, what happens if B is called using a gen-class'd
> class and calls A?
5 matches
Mail list logo
