duh! Yes, its there:
-- snipped --
<buildOutputDirectory>build</buildOutputDirectory>
-- snipped --
I am not sure I understand why you need to do a 'mvn test-compile' if
the output dir was set to default?
I will revert my commit.
Cheers,
Rahul
Olivier Lamy wrote:
Have you looked at the continuum parent pom ?
Personnaly, I don't like to use ${project.build.outputDirectory} in
the buildOutputDirectory for the eclipse.
Because after a clean I can't work until I do again mvn test-compile.
That's why I have forced to build since very long time in the continuum pom.
2008/4/8, [EMAIL PROTECTED]<[EMAIL PROTECTED]>:
Author: rinku
Date: Tue Apr 8 00:31:20 2008
New Revision: 645781
URL: http://svn.apache.org/viewvc?rev=645781&view=rev
Log:
o baselined version for maven-eclipse-plugin.
o Added configuration for maven-eclipse-plugin. (Recent release apparently
defaults output directory 'build' in absence of any specified).
Modified:
continuum/trunk/pom.xml
Modified: continuum/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/continuum/trunk/pom.xml?rev=645781&r1=645780&r2=645781&view=diff
==============================================================================
--- continuum/trunk/pom.xml (original)
+++ continuum/trunk/pom.xml Tue Apr 8 00:31:20 2008
@@ -150,6 +150,14 @@
</archive>
</configuration>
</plugin>
+<plugin>
+<groupId>org.apache.maven.plugins</groupId>
+<artifactId>maven-eclipse-plugin</artifactId>
+<version>2.5.1</version>
+<configuration>
+<buildOutputDirectory>${project.build.outputDirectory}</buildOutputDirectory>
+</configuration>
+</plugin>
</plugins>
</build>
<modules>
