Hi all,
I have started to introduce the maven-failsafe-plugin to our build.
Please see [1] for a very good and detailed explanation about the
working(s) of this plugin.
The main idea is to have a better and cleaner separation between
a) unit test
b) functional (integration) tests.
Right now, most of the modules don't have such a clean separation, and
as such, as part of executing
> mvn test
both *unit* and *integration* tests will be executed, increasing the
time of the built during development.
Once this new plugin has been introduced project-wide, and all the
integration tests have been 'marked' as such, the will be a clean
separation at the Maven level:
> mvn clean test
... will execute the unit tests only.
> mvn clean verify
.. will execute unit and integration tests.
So far, I have introduced the usage of the maven-failsafe-plugin to the
jpa-extensions-it module only, and configured it to use the *ITCase
suffix to establish integration tests. To showcase things, I have
renamed one of the existing functional tests (testing the support of the
JPA @NamedQuery annotation) so far.
Have a look at the project's POM as well, and I'd appreciate any
feedback or questions.
Regards
Werner
[1]:
http://maven.apache.org/plugins/maven-failsafe-plugin/index.html
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
