On Tue, Aug 30, 2005 at 01:59:52AM +0200, [EMAIL PROTECTED] wrote:
> Hei,
> 
> I have recognised that the evaluation of ${basedir} has changed from my
> Maven2 build on 23.august to the one I downloaded and built on 29.august.
> 
> Building with Maven2 of 23.august would give the value of the actual
> directory where the POM is situated also when this POM is deep down in a
> hierarchy of POMs. But now I see that ${basedir} evaluates to the
> directory of the highest POM that is run in the hierarchy.

I think this is a known bug.

> 
> A plugin configuration in the POM in directory
> "C:\work\nims\main\j2ee\incatel-nims\nims-webservice\nims-webclient-dto"
> is like this:
> 
>   <configuration>
>     <output>${basedir}/src/main/java</output>
>   </configuration>

The ${basedir} prefix should not be required here if the output parameter
is of type File as it should be. Maven should build the proper path for
you in the constructed File object.

[snip]

--
Trygve

Attachment: signature.asc
Description: Digital signature

Reply via email to