Hallo, That is also my question, I am using the WTP 2.0 setting but I am not sure it does an effect or not???
In snapshot version of the plugin, the log statements are mentioning the which setting is in use but that had dissappered. And I have a remark on the second point also. In a workspace, if a project has a dependency to another project in the workspace, eclipse is not able to resolve this dependency until we configure it in J2EE dependency, I guess this can be automated or not.... T-Mobile Deutschland GmbH Aufsichtsrat: Hamid Akhavan (Vorsitzender) Geschäftsführung: Philipp Humm (Sprecher), Thomas Berlemann, Stefan Homeister, Dr. Peter Körner, Günther Ottendorfer, Dr. Raphael Kübler, Dr. Steffen Roehn Handelsregister: Amtsgericht Bonn, HRB 59 19 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr.: DE60800328 -----Ursprüngliche Nachricht----- Von: Zemian Deng [mailto:[EMAIL PROTECTED] Gesendet: Samstag, 5. April 2008 19:52 An: Maven Users List Betreff: Re: [ANN] Maven Eclipse Plugin 2.5.1 Released Hi eclipse plugin users, I have couple feedback to the plugin. I used mvn eclipse:m2eclipse -Dwptversion=1.5 for all my webapp dev. Is there any update for wptversion that I should be aware of? The old one works fine, but using number 1.5 always make it seems it's outdated. Can it be set something like -Dwptversion=latest instead? Also, when use command above, there are two things I always need to set before an webapp can be run: 1) Enable the j2EE Dependecies checkbox for M2REPO library set in the project properties. 2) Add server library(Tomcat) to the classpath of the project. Are there way to auto set these? Thanks, Zemian Deng On Sat, Apr 5, 2008 at 3:09 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > The Maven team is pleased to announce the release of the Maven Eclipse > Plugin, version 2.5.1 > > This plugin is used to generate Eclipse IDE files (*.classpath, > *.wtpmodules and the .settings folder) for use with a project. > > http://maven.apache.org/plugins/maven-eclipse-plugin/ > > You can run mvn -up to get the latest version of the plugin, or > specify the version in your project's plugin configuration: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-eclipse-plugin</artifactId> > <version>2.5.1</version> > </plugin> > > This release fixes several bugs. > > Release Notes - Maven 2.x Eclipse Plugin - Version 2.5.1 > > ** Bug > * [MECLIPSE-266] - plugin applies java facet to ear project > * [MECLIPSE-411] - manifest property usage is only for ogsi maifests > * [MECLIPSE-412] - Generation of jst.java Facet for EAR packaging > kills my RAD workspace > * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact id > and not the EclipseProjectName > > ** New Feature > * [MECLIPSE-405] - to-maven target should allow to strip qualifier > when creating artifacts from osgi bundles > > Enjoy, > > -The Maven team > .......................................................... > Arnaud HERITIER > .......................................................... > OCTO Technology - aheritier AT octo DOT com > www.octo.com | blog.octo.com > .......................................................... > ASF - aheritier AT apache DOT org > www.apache.org | maven.apache.org > ........................................................... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks, Zemian Deng --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
