On Oct 16, 2012, at 2:05 PM, Matthew Piggott <[email protected]> wrote: > The tests expect to be run inside an Eclipse instance. For examples you > could look at the tests in m2e source, or one of the connectors in m2e-extras > ( https://github.com/sonatype/m2eclipse-extras/ ).
Yeah, the problem is that those are all based off of the m2e-connector approach (http://wiki.eclipse.org/M2E/Extension_Development), not the new BuildContext approach (http://wiki.eclipse.org/M2E_compatible_maven_plugins). I already have a working m2e-connector approach based off the m2eclipse-extras examples. I was just hoping to migrate to the BuildContext approach because then there's only the Maven plugin to maintain, not both a Maven plugin and an Eclipse plugin. Steve On Oct 15, 2012, at 4:52 PM, Steven Bethard <[email protected]> wrote: > I've been updating a code-generation plugin to use BuildContext as suggested > in the instructions here: > > http://wiki.eclipse.org/M2E_compatible_maven_plugins > > Is there an example anywhere of testing a Maven plugin like this? > > In particular, I'm wondering how to migrate tests written in the m2e > connector style (where you subclass > org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase and use Tycho to > configure dependencies) to the normal Maven style (where tests go in > src/test/java and Maven configures the dependencies). Has anyone done this? > > Steve _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
