Re: [Maven-plugins-developer] [patch] project.xml inheritance

[Jorn A H. <Jo...@pe...>]

Hi,

Hmmm after doing some debugging it appears that The Real Reason for the 
unwanted behaviour is that the project.xml file for installed plugins is
read when Maven initialize. When the plugin initializes the relative lookup
will start from your current working dir/the ${basedir} 

Hence this bug will appear from the moment where you deploy a plugin 
having a relative <extend> path and try to use Maven afterwards :-(

I guess this means that using the extend mechanism isn't practical for 
plugin development until someone come up with a clever solution to 
this.

Thanks,
Jørn


----- Original Message ----- 
From: "Stéphane MOR" <ste...@ya...>
To: <mav...@li...>
Sent: Tuesday, September 10, 2002 4:15 AM
Subject: Re: [Maven-plugins-developer] [patch] project.xml inheritance


> Jorn A Hansen wrote:
> 
> Good idea !
> 
> Though, it appears that right now, the Reactor doesn't take extended 
> projects into account...
> With the reactor, "../project.xml" is considered to be from the current 
> dir, ie from the top
> dir.
> 
> If you set it to "${basedir}/../project.xml", it is not transformed and 
> throws an error.
> 
> I'll have a look at all that, and apply the patch as soon as I can 
> generate the site with it.
> 
> Thanks,
> Stéphane
> 
> >Hi,
> >
> >This patch uses the <extend> inheritance mechanism which allows for easier maintenance of the Wiki and RPM project descriptors.
> >
> >The following elements are now inherited from the site POM:
> >  organization
> >  gumpRepositoryId
> >  issueTrackingUrl
> >  mailingLists
> >  build
> >
> >Apart from that there is a minor fix for these elements:
> >- name
> >- package
> >
> >
> >Thanks,
> > Jørn
> >
>
Jørn A Hansen 

--
Perfection is achieved, not when there is nothing more to 
add, but when there is nothing left to take away.
                           - Antoine de Saint-Exupery