Re: [jboss-as7-dev] Distribution of testing modules
Does it make sense to align this with the notions of profiles?
I like the idea of shipping a lean and mean which is what applications developer are used
too and look for, however new development paradigm will be relying on those modules.
Saying that I like the idea of isolating them in a different area.
I don't know what's the best option for our users, am interested to read feedbacks
on this.
Maybe Max and Andrew have thoughts on how we could provide those modules to the end users
(maven/Eclipse,...?) without fattening the distro.
--
Bruno Georges
On Mar 18, 2011, at 5:56, "David M. Lloyd" <david.lloyd(a)redhat.com>
wrote:
In our current modules distribution for AS7 we currently are
distributing:
- JUnit
- HTMLUnit
- JSFUnit
- Arquillian SureFire
- the AS7 Arquillian subsystem
- ShrinkWrap
- Various glue and support modules for the above
- Probably more test-oriented stuff I missed in my glance-over
The question is:
1. Do we really want to be distributing these test frameworks?
2. If so, should we put them in their own area somehow?
3. Also if so, should be recommend, as a policy, how and when these
modules should be used by end users?
4. If not, how can we exclude them from the final build?
--
- DML
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev