On Thursday 21 February 2008 wrote Graham Leggett: > Martin Höller wrote: > > 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> > > What purpose does this serve?
I need a MANIFEST.MF for the classpath (it's a skinny war as it is part of an EAR) > > 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/... > > The way Eclipse deals with manifest files is they are considered part of > the source code, not a generated artifact. Yeah, that's why I want maven to generate it for eclipse as maven has all the information that belongs into the MANIFEST.MF > As a result, if you want to synchronise Eclipse with anything in maven, > you have to edit the existing files where Eclipse put them. Eclipse didn't and wouldn't put MANIFEST.MF anywhere if it didn't exist, so either I create it by hand (what is not what I want) or let maven create it for me, which the m-eclipse-p obviously is designed for. It's just the location of the file that isn't configurable and has IMHO a bad default. thanks for you answer anyway, - 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.
