forgot to tell that when I tried to import my projects into a new
workspace I got this errors:
No marketplace entries found to handle
jacoco-maven-plugin:0.7.1.201405082137:prepare-agent in Eclipse.
Please see Help for more information.
No marketplace entries found to handle maven-antrun-plugin:1.7:run
in Eclipse. Please see Help for more information.
one more indication that the new version is not accepting versionRange
properly
On 16-08-2014 16:43, Cristiano Gavião wrote:
Igor,
after have installed 1.6 my configured lifecycle mapping (in parent
corporate pom) stopped to work.
Now I'm getting these errors:
Multiple annotations found at this line:
- Plugin execution not covered by lifecycle configuration:
org.jacoco:jacoco-maven-plugin:
0.7.1.201405082137:prepare-agent (execution:
prepare-ut-agent, phase: process-test-classes)
- Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-antrun-
plugin:1.7:run (execution: delete-osgi-inf, phase: validate)
seems that this new version is not accepting versionRange properly.
below is part of my corporate pom:
<pluginManagement>
<plugins>
<plugin>
<groupId>org.eclipse.m2e</groupId>
<artifactId>lifecycle-mapping</artifactId>
<version>1.0.0</version>
<configuration>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<versionRange>[1.0,)</versionRange>
<goals>
<goal>run</goal>
</goals>
</pluginExecutionFilter>
<action>
<execute>
<runOnIncremental>false</runOnIncremental>
<runOnConfiguration>true</runOnConfiguration>
</execute>
</action>
</pluginExecution>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
<versionRange>[0.6,)
</versionRange>
<goals>
<goal>prepare-agent</goal>
</goals>
</pluginExecutionFilter>
<action>
<!-- m2e doesn't know
what to do with jacoco, let's ignore it
or annoying error
markers appear see
http://wiki.eclipse.org/M2E_plugin_execution_not_covered -->
<ignore />
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
</configuration>
</plugin>
</plugins>
</pluginManagement>
after removing and reinstalled 1.5 everything went ok again...
cheers,
Cristiano
On 15-08-2014 12:35, Igor Fedorenko wrote:
I just pushed some interesting m2e changes to master and I would like to
ask some help testing them. The new version is already available from
m2e snapshots repository [1]
Couple of notable changes
The biggest change is reworked caching of maven plugins and build
extensions referenced by workspace projects [2]. This should provide
much better behaviour for projects that use snapshot versions of plugins
and build extensions and should also result in smaller memory footprint
for long-lived m2e instances.
m2e embedded maven runtime was updated to version 3.2.3.
The full list of changes in m2e 1.6 so far is in bugzilla [3]
[1]
http://repository.takari.io:8081/nexus/content/sites/m2e.extras/m2e/1.6.0/N/LATEST/
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=441257
[3]
https://bugs.eclipse.org/bugs/buglist.cgi?list_id=9852428&product=m2e&query_format=advanced&resolution=FIXED&target_milestone=1.6.0%2FMars%20M1
--
Regards,
Igor
_______________________________________________
m2e-users mailing list
[email protected]
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users
