That worked, thanks Barry. One problem remains though. For filtering
purposed I defined two resources:
<resources>
<resource>
<directory>src/main/webapp</directory>
<filtering>true</filtering>
<targetPath>../filtered-webapp-resources</targetPath>
</resource>
<resource>
<directory>src/main/config</directory>
<filtering>true</filtering>
</resource>
</resources>
The eclipse plugins creates those two as source folders, which is ok.
It also creates output folders for these source folders, which I do
not want.
On 11/28/05, Barry Kaplan <[EMAIL PROTECTED]> wrote:
> Kees de Kooter wrote:
> > Is it possible to control which output folders the eclipse plugin puts
> > into the .classpath file? I tried setting the outputDirectory property
> > in the plugin configuration but that did not have any effect.
>
> I use this and it works:
>
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-eclipse-plugin</artifactId>
> <configuration>
> <outputDirectory>target-eclipse</outputDirectory>
> </configuration>
> </plugin>
> </pluginManagement>
> ...
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
