This is a bit "dangerous".
1) a project will have a different model depending on that property. It will
ripple into needing to change other things like the final name of the built
artifact to ensure you don't end up with one thing sometimes being something
different
2) you can only do this trick once. There is no multiple inheritence.
This is a little bit of an unusual use case. It's understandable that you
often depend on a spec dependency (for which we don't yet have great
support) and an impl goes into the final bundle and the impl might change.
Changing the API too is what is unusual.
Anyway, in m1 the general approach to this is to have two projects that do
the different bundling and build whichever you want, sharing the common
code. I'm not sure if that's easily done when the api is changed though.
I replied in this fashion in another thread. I should also mention again
that environmental changes to project builds are supported in Maven 2.
- Brett
On 8/31/05, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>
> From: "Jay H. Hartley" <[EMAIL PROTECTED]>
>
> > 2) Create two different "parent" project files, and have the "extends"
> > parameter depend on a property:
> >
> > <project>
> > <extends>${jsf.project.file}</extends>
>
> That has promise! Thanks, I didn't know you could do that. :)
>
> If it's not painfully obvious by this point, this is an existing Ant build
> that I'm trying to reproduce with Maven.
>
> After several days of fighting with it, I'm going to retreat to the
> position
> of making the Maven build do something reasonably useful, and propose a
> reorganization to get the project into a format that Maven is happier to
> deal with.
>
> Thanks for putting up with all the questions. :)
>
> --
> Wendy Smoak
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
