Hi,

I have created an archetype variant which reads a property file (or
ask for values) which are used in the project generation.

What you are about is to call the same archetype with multiple
property sets (file or asked)
and check the result. which sound really like integration testing.

I don't have yet used the verifier plugin, but it seems it is what you
searching. IIRC it permits to call Maven with a specific argument line
and check the files after the execution.

You can find my current version of archetype in the scm repository (in
mojo/mojo-sandbox/maven-archetypeng)

Regards,

Raphaël

2007/4/20, andrew cooke <[EMAIL PROTECTED]>:
> Hi,
>
> It sounds like integration test for archetypes.
>
> If yep, i dunno anything like this for now.
>
> Can you please explain a bit more your use case.

We use an archetype to generate a project with Java classes containing
"gaps" that a user must complete to implement a library.  We do this using
maven's archetype mechanism and a plugin that we have developed, based on
one called "bobber" which no longer appears to exist.  This includes
prompting the user for values that are included in the generated code.

So the system can generate different files depending on various parameters
the user enters.  Currently it is untested - there is no automatic way of
generating the project for a certain set of parameters and comparing that
against a standard.

We want to extend this further.  We would like the archetype to configure
the project so that when maven site is generated we have certain standard
documentation present.  Again, we have no way of testing this.

Now I can write my own test framework, but this seems like a problem mojo
members must already have faced, so I wonder what test support already
exists.

Maybe it is more something that the Maven 2 project itself has to deal with?

Andrew


>
> There is currently some work on archetypes.
>
> Regards.
>
> 2007/4/19, andrew cooke <[EMAIL PROTECTED]>:
>> Hi,
>>
>> I want to test a plugin.  A coworker said I should look at how M2 does
>> CI
>> with plugins, but I have no idea how to do that.
>>
>> More detail - we are using archetypes to generate code and documentation
>> templates for users (this is for the Mule ESB - if the user wants to
>> write
>> a new transport they can first generate skeleton code and docs via the
>> archetype).  We are using our own plugin (an adapted bobber plugin) to
>> do
>> this, and the system is getting sufficiently complex that I'd like to
>> have
>> regression tests.  I'd like to be able to run the archetype for a
>> variety
>> of inputs and check the generated files against some standard
>> directories.
>>
>> Does that make sense?  Seems like you (Mojo, M2, or individual Mojo
>> members) may well be doing something similar, but is it publicly
>> visible?
>> If so, where?  I looked through the Mojo site thinking I might find
>> guidelines there, but found nothing - sorry if I've missed something.
>>
>> Thanks,
>> Andrew
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>



---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to