This is expected to work in Kepler, so what you see is either a bug or
misconfiguration.
Make sure the plugin is not ignored inside eclipse workspace. The
easiest is to right-click->Properties->Maven->Lifecycle_Mapping.
build-helper-maven-plugin entry mapping column should say "execute" or
"configurator" if the project is configured properly.
--
Regards,
Igor
On 11/27/2013, 16:01, Jarkko Rantavuori wrote:
Hi,
I have configuration
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<executions>
<execution>
<id>add-test-sources</id>
<phase>generate-test-sources</phase>
<goals>
<goal>add-test-source</goal>
</goals>
<configuration>
<sources>
<source>${project.build.directory}/generated-sources/castor</source>
</sources>
</configuration>
</execution>
</executions>
</plugin>
and I'm not able to get it activated in Eclipse Kepler. I've tried the
same steps it used to work with Juno, I've tried adding the plugin
execution filters as well as having connector installed for the plugin,
and I've tried testing instructions at
http://stackoverflow.com/questions/12685683/m2e-connector-buildhelper-not-compatible-with-eclipse-juno-sr1-m2e-1-2,
but nothing seems to work. Has anyone got that working with Kepler?
_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users
