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.
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).
I guess my vote is to not factor the functionality into a different subtask.
I've cc'd Reimer Mellin in, he may have different thoughts than me :-)
Thanks,
Juan
On 8/8/02 3:46 PM, "Andrus" <andru..bjectstyle.org> wrote:
> Another idea I have is that instead of plugging the new functionality into
> WOApplication task, we subclass it into a separate task. Something like
> "WOStandAlone" (I am open to name suggestions).
>
> This way "embed*" arguments can be set to "true" by default (when omitted),
> thus keeping configuration parameters to a minimum. Also this will open a
> way for the new deployment tasks, like war packaging ("WOWar" ?).
>
> Andrus
>
>
> At 09:41 AM 8/8/2002 -0700, Max Muller wrote:
>> Hi,
>> That is a very interesting idea. Once you have the patch in
>> place, please let me know. With a few tweaks to WOResourceManager we
>> could create a similar task option to build everything into a .war to
>> make servlet deployment easier.
>>
>> Regards,
>> Max
>
>
This archive was generated by hypermail 2.0.0 : Thu Aug 08 2002 - 16:04:02 EDT