> -----Original Message-----
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
>
> On Mon, 2003-12-01 at 19:44, [EMAIL PROTECTED] wrote:
> > Alan,
> >
> > since I'm also involved in Maven, could you send me an email
detailing
> the
> > issues and I'll get things moving as well?
>
> We can probably take care of it on this list.
>
> The basic problem is property inheritance which there is a stop-gap
> solution for using Vincent's property hack outside any Jelly goal. I
> think the problem with the rc1 release is that Vincent introduced the
> Jelly tags that make this work after the rc1 release.
>
> I offered to put together a snapshot which included the required Jelly
> tags and a patch to the build that used Vincent's technique.
>
> There is a POM that is extended in the etc/ directory as well as a
> maven.xml file where Vincent's method could be employed.
>
> The top-level maven.xml could also use some work as it employs some
> creative methods that I've never seen to produce the biggest maven.xml
> file I've ever seen :-) The little bubba weighs in at a not so svelt
> 20k.
>
> So using Vincent's method for property inheritance and a general
cleanup
> of the top-level maven.xml would go a long way to fixing most of the
> problems.
Thanks Jason. What exactly is Vincent's method for property
inheritance? Will it fix the problem of maven.xdoc.version translating
to "${pom.currentVersion}"? See
http://www.toolazydogs.com/geronimo/index.html for an example; look at
the top left corner.
Regards,
Alan
Regards,
Alan
