That is easy, I am talking about all the others: org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning org.eclipse.jdt.core.compiler.problem.autoboxing=warning org.eclipse.jdt.core.compiler.problem.deprecation=warning org.eclipse.jdt.core.compiler.problem.deprecationInDeprecatedCode=disabled
and so on... On Wed, Mar 4, 2009 at 3:13 PM, Todd Thiessen <[email protected]> wrote: > maven-compiler-plugin > > <plugin> > <artifactId>maven-compiler-plugin</artifactId> > <configuration> > <source>1.5</source> > <target>1.5</target> > </configuration> > </plugin> > > --- > Todd Thiessen > > >> -----Original Message----- >> From: Daniele Dellafiore [mailto:[email protected]] >> Sent: Wednesday, March 04, 2009 9:10 AM >> To: Maven Users List >> Subject: [maven-eclipse-plugin] Define compiler options in POM >> >> Hi all. >> >> Hi have this issue: every time I run mvn eclipse:eclipse the >> .settings folder of the project is cleaned and I lose my >> project specific compiler settings. I would like to keep them >> or at least be able to define them in the POM. >> >> What solution do you suggest? I have not found any on the web... >> >> -- >> Daniele Dellafiore >> http://blog.ildella.net/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Daniele Dellafiore http://blog.ildella.net/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
