You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Kai Hackemesser <ka...@gmail.com> on 2009/09/28 05:50:54 UTC

Problems with latest m2eclipse

Hello,

I just updated my eclipse configuration today, and it is complaining now
about things that aren't absolutely understandable to me. The plugins
mentioned in the output below aren't defined by my project and should be use
whatever is default. The project has an extra m2 builder defined to cal
war:exploded after saving stuff in Eclipse. I have found after my update
that Eclipse has updated the Maven runtime to 3.0  snapshot, but I have
defined my own configuration for 2.0.10 that should be used. I haven't found
a way to configure m2 builder to use anything instead the default maven
config. How do I solve that issue?

[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for com.en[...]war:2.0.0-SNAPSHOT
[WARNING]
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-javadoc-plugin @ com.en[...]:2.0.0-SNAPSHOT
(C:\workspace\suite-4.0-SNAPSHOT\project\pom.xml)
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.codehaus.mojo:taglist-maven-plugin @ com.en[...]:2.0.0-SNAPSHOT
(C:\workspace\suite-4.0-SNAPSHOT\project\pom.xml)
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-jxr-plugin @ com.en[...]:2.0.0-SNAPSHOT
(C:\workspace\suite-4.0-SNAPSHOT\project\pom.xml)
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-surefire-report-plugin @
com.en[...]:2.0.0-SNAPSHOT (C:\workspace\suite-4.0-SNAPSHOT\project\pom.xml)
[WARNING] 'reporting.plugins.plugin.version' is missing for
org.apache.maven.plugins:maven-checkstyle-plugin @
com.en[...]:2.0.0-SNAPSHOT (C:\workspace\suite-4.0-SNAPSHOT\project\pom.xml)
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]

[INFO]
------------------------------------------------------------------------
[INFO] Building clariti 2.0.0-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-war-plugin:2.1-alpha-2:exploded (default-cli) @ project ---
[INFO] Exploding webapp
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 3.359s
[INFO] Finished at: Mon Sep 28 16:35:55 NZDT 2009
[INFO] Final Memory: 4M/8M
[INFO]
------------------------------------------------------------------------
[ERROR] modelEncoding : modelEncoding
---- Debugging information ----
message             : modelEncoding : modelEncoding
cause-exception     :
com.thoughtworks.xstream.mapper.CannotResolveClassException
cause-message       : modelEncoding : modelEncoding
class               : org.apache.maven.plugin.war.util.WebappStructure
required-type       : org.apache.maven.model.Dependency
path                :
/webapp-structure/dependenciesInfo/org.apache.maven.plugin.war.util.DependencyInfo/dependency/modelEncoding
line number         : 2039
-------------------------------

Re: Problems with latest m2eclipse

Posted by Kai Hackemesser <ka...@gmail.com>.
Just found it. the setting for the Maven runtime in the builder
configuration dialog was hidden because the configuration window was a
little too small. Looks like an eclipse issue.