Hi Max - thanks for the holiday reply :-)
Hmm...i'm interested how ? :) you mean because in jbt 3.3 M1 we
included
every single jar found under modules and thus it was >exposed on The
classpath ?
Well substantially yes. Having Arquillan modules bundled in the distribution
means you could set up your EE integration test from Eclipse in a matter of
minutes.
The reverse side of the medal, is that bypassing Maven, you would get a
discrepancy from the official distribution.
I'd be glad to hear what developers consider the major priority between
these two statements.
I by no means am trying to discourage anyone from writing unit tests,
however I've found the percentage of unit tests in EE applications to be
small, mostly because it was necessary to invest time (and money) in
learning and setting up a proper test environment; so IMHO, having an
integration test platform built-in could be a very good plus.
regards
Francesco
2011/6/19 Max Andersen <manderse(a)redhat.com>
> As a matter of fact, having Arquillan libraries built-in AS 7 makes
fairly attractive unit testing with Eclipse Indigo and JBoss Tools 3.3.1,
which already have AS 7
Hmm...i'm interested how ? :) you mean because in jbt 3.3 M1 we included
every single jar found under modules and thus it was exposed on The
classpath ?
We actually dont do that anymore in M2 since including everything is and
Will eventually cause more than a few classloader issues.
For now we just limit it to The javax module.
Until now i havent been fond of arquillian being bundled within as7 since
it creates yet another different way of configuring and setting up
classpaths for arquillian.
I.e. If we go back to include it for as7 server adapter in Jbt then those
projects that want to target multiple server testing would need to remove
it.