Here is another line of thought... I have to assume these test packages
do not really change often. So why not check them into svn?
On Tue, 2010-01-26 at 10:09 -0300, Hardy Ferentschik wrote:
As you already say the forking is needed for the packaged tests. The
only
solution I can think about
is to split these tests out. Effectively we would have two sets of tests
then. All the "normal" unit
tests (even though Steve would probably say that our unit tests are really
integration tests as well ;-))
and then the packaged tests which would be "integration" tests.
There are several ways of achieving this. We could configure multiple
surefire executions or use the
failsafe-maven-plugin. The former I approach I used before. The latter I
haven't tried.
There is more information about this here:
http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing
Create a Jira issue and assign it to me if you like.
--Hardy
On Tue, 26 Jan 2010 09:55:40 -0300, Emmanuel Bernard
<emmanuel(a)hibernate.org> wrote:
> Hi Maven gurus,
> Is there a way to make mvn test runs faster for entitymanager?
> It seems that the vm is forked for every test. While I understand the
> need for the "packaging" tests, most tests don't require such forking
> and could be executed much faster.
>
> I don't know if that's possible but that would be nice.
>
> Emmanuel
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev --
Steve Ebersole <steve(a)hibernate.org>
Hibernate.org