[jboss-as7-dev] Aquillan module in AS 7 final ?

Max Rydahl Andersen max.andersen at redhat.com
Mon Jun 20 07:28:48 EDT 2011


> >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.

For JBT M2 you would have to add it manually since we limited the automatic class path inclusion to public javax api.

> 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.

Yes, this is my problem - that there will be discrepancies by default which aren't good.
> 
> I by no means am try ing to dis cour age any one from writ ing 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.

True. We've got plans to allow user to configured what parts of the modules in AS7 they will include on projects - but as you say its a challenge to get the "easy setup, short toerm" to work well with "a bit more options but stable long term" solutions.

right now i'm leaning towards the "long term" option but if we can find a better balance in how the two are setup/configured that would be great.

/max

> 
> regards
> Francesco
> 
> 2011/6/19 Max Andersen <manderse at 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.
> 
> 
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

/max
http://about.me/maxandersen






More information about the jboss-as7-dev mailing list