Eclipse Maven Error Plugin execution not covered by lifecycle configuration: -


i using eclipse juno maven 3.0.5 on windows 7. project on windows xp , have moved windows 7 64 bit machine.

i have copied eclipse spring 3, hibernate 4 , jsf 2.0 project , when try compile getting following error

plugin execution not covered lifecycle configuration:  org.bsc.maven:maven-processor-plugin:2.0.6:process (execution: process, phase:  generate-sources)

i tried mentioned in this thread adding following in eclipse.ini file, didn't solve issue.

-vm c:\program files\java\jdk1.7.0_21\jre\bin\server\jvm.dll

tried building maven install , clean, problem still persists.

how can resolve issue? highly appreciable.

thanks

maven snippet

<plugins>              <plugin>                 <groupid>org.apache.maven.plugins</groupid>                 <artifactid>maven-compiler-plugin</artifactid>                               <configuration>                     <source>1.6</source>                     <target>1.6</target>                     <compilerargument>-proc:none</compilerargument>                 </configuration>             </plugin>             <plugin>                 <groupid>org.bsc.maven</groupid>                 <artifactid>maven-processor-plugin</artifactid>                 <version>2.0.6</version>                 <executions>                     <execution>                         <id>process</id>                         <goals>                             <goal>process</goal>                         </goals>                         <phase>generate-sources</phase>                         <configuration>                             <!-- source output directory -->                             <outputdirectory>target/metamodel</outputdirectory>                         </configuration>                     </execution>                 </executions>             </plugin>         </plugins>

newer versions of m2e complain if maven plugin not provide m2e lifecycle mapping. newer plugins provider such mapping via file meta-inf/m2e/lifecycle-mapping-metadata.xml in jar. if file not present, eclipse complains.

it possible quite down these complaints adding lifecycle mapping older plugins pom. in given example, mapping done inside profile automatically activated when build running in eclipse (m2e.version property set) , not active when regular maven build done.

<profiles>   <profile>     <id>m2e</id>     <activation>       <property>         <name>m2e.version</name>       </property>     </activation>     <build>       <pluginmanagement>         <plugins>           <plugin>             <groupid>org.eclipse.m2e</groupid>             <artifactid>lifecycle-mapping</artifactid>             <version>1.0.0</version>             <configuration>               <lifecyclemappingmetadata>                 <pluginexecutions>                   <pluginexecution>                     <pluginexecutionfilter>                       <groupid>org.bsc.maven</groupid>                       <artifactid>maven-processor-plugin</artifactid>                       <versionrange>[2.0.6,)</versionrange>                       <goals>                         <goal>process</goal>                       </goals>                     </pluginexecutionfilter>                     <action>                       <ignore />                     </action>                   </pluginexecution>                 </pluginexecutions>               </lifecyclemappingmetadata>             </configuration>           </plugin>                  </plugins>       </pluginmanagement>     </build>   </profile>

the example above disables plugin in eclipse builds. possible enable specifying <execute /> action .

mind settings under pluginexecutionfilter must match plugin , goals of plugin wish map. multiple pluginexecution elements can specified map different plugins.


Comments

Post a Comment

Popular posts from this blog

linux - xterm copying to CLIPBOARD using copy-selection causes automatic updating of CLIPBOARD upon mouse selection -

i've tried various ways coerce xterm (versions 285 , 292) copy selection clipboard clipboard whenever press ctrl-shift-c. promising way far has been, in ~/.xresources, put this: xterm*vt100.translations: #override \ ctrl shift <keypress> c: copy-selection(clipboard) \n\ ctrl shift <keypress> v: insert-selection(clipboard) ctrl-shift-v works perfectly, copying has nuance... if restart xterm, highlighting text puts things in primary clipboard; expected, proper, default behavior. if hit ctrl-shift-c, copies current selection clipboard clipboard. the bug, however, if highlight text after first time pressed ctrl-shift-c, you'll see highlighting copies both primary and clipboard. cannot figure out how stop xterm updating clipboard upon selection... , doesn't make sense me in first place. i said, @ specific point in time, copy selection clipboard... yet starts updating automatically upon selection after doing once... anyone have workaround...
Read more

c++ - qgraphicsview horizontal scrolling always has a vertical delta -

Image
i've subclassed qgraphicsview custom canvas used in cad application. i've reimplemented qgraphicsview::wheelevent check keyboard modifiers control key and, if control key pressed, zoom. i'm trying implement horizontal scroll when user holds shift , uses wheel. the problem i'm having horizontal scrolling always scrolls 0.279. not huge problem, hugely annoying , points else being wrong. so, here questions: is right way implement horizontal scrolling? if not, is? how eliminate delta of 0.279? thanks in advance. code , sample output below void myview::zoom(int delta) { double factor = pow(1.2, delta/abs(delta)); this->scale(factor, factor); } void myview::scrollhorizontal(int level) { qpointf center = maptoscene(viewport()->rect().center()); qdebug() << "center: " << center.x() << ", " << center.y(); centeron(qpointf(center.x() - level, center.y())); } void myview::wheelevent(qwheeleve...
Read more