Hi Juan,
At 04:03 PM 8/8/2002 -0400, Juan J. Collas wrote:
>Andrus,
>
>The way it's presently done, a single-folder app can still depend on
>external frameworks and jars (you can have multiple framework subtasks, some
>with the embed="true" flag and some not).
>
>This way, it's up to the build.xml writer to determine the structure of the
>application, which resources are shared and which are embedded. If you have
>the notion of a WOStandAlone task, this capability is lost.
I am not suggesting to drop "embed*", just to make it "true" when omitted
in WOStandAlone. build.xml writer should be able to set it to "false" if
she needs to. This is just a nice shortcut and shows more clearly what the
task does.
This is like a normal OO design - when adding new functionality you can
keep pushing it in the base class, or you can create a specialized subclass
that "is" a superclass plus some more. In this case I am in favor of a
subclass, though I want it to be an open discussion. This is a clear case
of "specialized" build requirements.
>Also, you shouldn't need a WOWar task, since ant already supports building
>of war files (I'm not sure what syntactic sugar you'll need to embed the jsp
>support code).
Autogeneration of WO-specific "web.xml" could be a feature of such task.
I've looked at it in the past, but now I already forgot what is involved.
Andrus
This archive was generated by hypermail 2.0.0 : Thu Aug 08 2002 - 16:12:17 EDT