Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Flexible Project Structure Concepts Document

Hi Micheal, 
I have a couple of questions regarding the builder behaviour with the
dependent modules.
(1) Does deployable module output for a module include its dependent
modules? Or to pack and deploy the module one has to follow its'
(2) If a module depends on two modules in two separate projects and
one of the projects have compile errors, how will the builder behave?
Is it going to be possible to warn user since no dependency check is

Over all this feels like a good solution, The deployable module
builder and having a ready deployable module output is a great idea. I
am looking forward to it. please let me know If I can be of any help.
Gorkem Ercan

On Fri, 4 Feb 2005 18:10:38 -0500, Michael Elder <mdelder@xxxxxxxxxx> wrote:
> Extended Team:
>         The following document provides an overview of the Flexible Project
> Support. We are targeting the completion of the first draft of the Flexible
> Project API for the M3 milestone. Most teams will not have enough time to
> react to the changes caused by this paradigm shift, but we should be in a
> position to bring them onto the new structure through the M4 cycle and
> update our design as necessary.
>       A more formal API and migration document will be delivered at the end
> of the M3 cycle in preparation for teams to migrate during the M4
> iteration.
> Thank you for your feedback.
> -------------------------------------------------------------------------
> Kind Regards,
> Michael D. Elder
> Rational Studio / J2EE Tools Development
> Ext: (919) 543-8356
> T/L:  441-8356
> mdelder@xxxxxxxxxx
> _______________________________________________
> wtp-dev mailing list
> wtp-dev@xxxxxxxxxxx

Back to the top