I just see that the doc isn't up-to-date but you have a wtpversion=2.0
for newest versions of eclipse
For yur others projects you can have a look at the workspace property
which allow the plugin to read your current parameters.

On Sat, Apr 5, 2008 at 7:51 PM, Zemian Deng <[EMAIL PROTECTED]> wrote:
> 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
>



-- 
..........................................................
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]

Reply via email to