here you go, single pom would do
<?xml version="1.0"?>
<project>
<modelVersion>4.0.0</modelVersion>
<!--
<parent>
<groupId>test</groupId>
<artifactId>parent</artifactId>
<version>1.0-SNAPSHOT</version>
</parent>
-->
<packaging>jar</packaging>
<groupId>test</groupId>
<artifactId>child</artifactId>
<version>1.0-SNAPSHOT</version>
<name>child</name>
<build>
<plugins>
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<id>echo</id>
<phase>generate-sources</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<tasks>
<echo>project.build.directory:${project.build.directory}
</echo>
</tasks>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>
On 3/28/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> If that is the case, that is certainly bad - but I know we've had that
> regression before, and I thought there were tests in to enforce it, so
> I'd like to see a test case...
>
> - Brett
>
> On 3/29/06, dan tran <[EMAIL PROTECTED]> wrote:
> > my maven-2.0.3 shows ${project.build.directory}=target. Instead of the
> > fullpath
> > this surely breaks the reactor build/test.
> >
> >
> > Does any one encounter the same problem?
> >
> > -D
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
