On Wednesday 20 February 2008 wrote Graham Leggett: > Martin Höller wrote: > > I just noticed that the maven-eclipse-plugin (2.5-SNAPHSOT) writes a > > MANIFEST.MF output to src/main/webapp/META-INF when mvn eclipse:eclipse > > is called for a web-application. > > > > Is this behaviour intentional? I wouldn't expect maven or any plugin to > > write something into src/main. > > Is your project marked as a pde project?
No, it's not, it's a WTP 2.0 project. My plugin configuration is as follows:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.5-SNAPSHOT</version>
<configuration>
<downloadSources>false</downloadSources>
<downloadJavadocs>false</downloadJavadocs>
<wtpversion>2.0</wtpversion>
<wtpmanifest>true</wtpmanifest>
</configuration>
</plugin>
> > If the MANIFEST.MF is needed by eclipse, couldn't it be written to
> > target/ and eclipse be configured to use that instead, just as it
> > happens for EARs?
>
> Not practically, no. Eclipse does not have a clear distinction between
> "source" directories and "target" directories, so you need to modify the
> files where they lie, which can be annoying, particularly for Eclipse
> plugin builds.
Well, this file is not created by eclipse but by the m-eclipse-p. And I
would say this plugin shouldn't write to src/main/...
What I want is already done for EARs: an application.xml is required for a
valid EAR, so m-eclipse-p creates one in target/eclipseEar/META-INF/ and
points eclipse to this file as the application descriptor.
I think this should also be possible for WARs, shouldn't it?
- martin
--
Martin Höller | [EMAIL PROTECTED]
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
signature.asc
Description: This is a digitally signed message part.
