Layering is an interesting concept I hadn't considered. The new plugin does support layering so it seems possible. Hrm...
-----Original Message----- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 10:25 AM To: Maven Developers List Subject: Re: Core IT archetypes I think it'd be helpful to have single-module, multi-module, remote- repository (on the filesystem), and settings aspects covered, personally. The only trick is that two or more of these will almost certainly overlap, so it'd be nice to be able to apply one archetype over another to sort of build up the test scenario...I don't know how easy that would be, to setup those archetypes, however... -john On Jul 18, 2007, at 10:16 PM, Brian E. Fox wrote: > Hello, > > I'm just starting to look at creating core-it archetypes with the new > archetypeng plugin. While I'm reviewing the various existing tests, > I'm > curious what types of IT tests the group thinks are valuable, or which > tests might be good representations. > > > > One question to answer is do we need a single module archetype and a > multimodule archetype? I don't have a strong opinion either way > although > I am leaning towards one multi module archetype. It's usually > easier to > slim down an archetype than scale one up. I also think that the > multimodule tests are more representative of what should be done. (ie > install something, then run another build for the test) > > > > Besides single / multi-module tests, are there other categories that > should be considered? (ones that deal with repos, local settings, > other?) > > > > --Brian > --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
