commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Murdoch" <adammurd...@apache.org>
Subject RE: [vfs] [gump] RE: gumpifying vfs
Date Wed, 23 Oct 2002 04:24:30 GMT


> -----Original Message-----
> From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> Sent: Wednesday, 23 October 2002 2:28 PM
> To: Jakarta Commons Developers List
> Cc: turbine-maven-dev@jakarta.apache.org
> Subject: [vfs] [gump] RE: gumpifying vfs
>
>
> "Adam Murdoch" <adammurdoch@apache.org> wrote on 23/10/2002 12:20:41 PM:
>
> > > Adam, doesn't vfs use Maven?
> > >
> > > If so, how about just generating the ant and gump files so we can
> smooth
> > > the process out of getting commons projects built by Gump.
> >
> > Ok, I've done this.  There were a couple of tiny issues:
> >
> > The vfs tests have a post goal action on test:test-resources, that sets
> up a
> > bunch of test data.  The generated build.xml doesn't invoke this action
> > (which is fair enough), so the tests fail.  Which causes the build to
> fail.
> >
> > Simplest solution might be to rearrange the dependencies in the
> generated
> > build.xml, so that the jar target depends on compile-tests, and dist
> depends
> > on test.  Rather than dist -> jar -> test -> compile-tests.
> Ok, but wouldn't that mean the tests wouldn't run when the jar is created?

Yes, it would.  That's why the options below are better.

> > Even better would be if the ant plugin knew that it shouldn't run the
> tests
> > if there are custom actions hanging off the test goals.  Or if it could
> > somehow invoke those actions.  Or provide some way for me to specify
> which
> > tests are runnable from the ant script, and which are not.
> Ok, I'll think about this one. It may be as easy as making a property for
> the ant plugin to allow exclusion of classes for testing.

Yep, that would work.

> > Also, with the generated gump.xml, it might be better if the from
> address in
> > the nag email is someone a little closer related to the project (like,
> say,
> > one of the developers), rather than the maven developers.
> Would the nag email from the project.xml do?

Doh!  I completely missed the nag email.  Yes, that would do nicely :)


Adam


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message