Archimedes/Eric,

I'd like to add a test case for this fix. The test case per se wouldn't be hard, but it would require a new project.xml (without a source), which would in turn require that we break the test cases structure into multi-project.

So, any better idea on how to test it?

– Felipe

to be honest, we need to make it a multiproject setup anyway for the tests.. there are too many different project.xml structures, our tests are becoming more and more intertwined.. For instance, if you have cactus plugin or not..

Feel free to break them up (see hibernate plugin for an example).

Eric

Is there any documentation on how to create non-java plugin test cases? I am still confused on how to write them.

It's mostly a matter of learning by example. If you look at maven-plugins/hibernate/src/test-plugin/ there is a good example of using multiproject to test a collection of seperate projects and testcases. Most of the plugins have testcases to look at in maven-plugins/[PLUGIN]/src/test-plugin.

Eric

Archimedes,

Basically, what you have to do in this case is setup a project that doesn't have the source defined, run the eclipse goal and then parse the generated .classpath/.project to see if it was generated correctly (and failing if it doesn't).

As Eric mentioned, the best way to understand how to achieve that is looking through other testcases. Also, you would need to create a new directory for this testcase, as it would require changing the current testcases POM.

– Felipe

I have applied the patch, and refactored the unit tests to use multiproject, so eclipse is now a good example! I also added some tests for this patch.

Okay, it is now part of 1.10