gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <brett.por...@gmail.com>
Subject Re: excalibur-thread-impl failure in Gump
Date Tue, 21 Sep 2004 23:30:49 GMT
Short answer:
It has a problem in build.properties. There are two maven.jar.junit
properties, and the second points at ant-junit.jar, which I assume
does not declare junit.framework.TestCase.

More:
The generated file has some strange entries:
http://brutus.apache.org/gump/public/excalibur/excalibur-thread-impl/gump_file/build.properties.html:
eg maven.jar.=/usr/local/gump/public/workspace/excalibur/components/thread/impl/target/classes
and all the ant, magic, etc dependencies which aren't declared in project.xml.

I assume these are coming from the gump descriptor. This should be
changed in one of the following ways:
- gump generates build.properties only for project.xml dependency
entries (including anything in extended POMs), rather than everything
in the gump descriptor
- gump descriptor has a flag on dependencies for ones that should be
controlled in build.properties

Not understanding the need for the extra libs and not being familiar
with Avalon, I'm not sure what the best solution is here. I always
thought that the gump deps to Maven deps would be 1:1.

gump descriptor generated from maven project should be ok, as it only
lists project.xml dependencies.

Any additions to the Maven Gump plugin are welcome - just file them in
JIRA and I'll take a look.

(BTW, You don't need a junit dependency, as Maven adds it).

Cheers,
Brett

On Tue, 21 Sep 2004 15:27:29 +0200, Stefan Bodewig <bodewig@apache.org> wrote:
> On Tue, 21 Sep 2004, Stephen McConnell <mcconnell@apache.org> wrote:
> >> From: Stefan Bodewig [mailto:bodewig@apache.org]
> 
> >> db-grafolia[1] works as well.  But it doesn't even list a
> >> dependency on JUnit in the Gump descriptor.
> >
> > The listing in the gump descriptor is only going to effect the Gump
> > ordering - not the execution in Maven.
> 
> I understood that much 8-)
> 
> > The junit target in maven fires off a junit plugin which has the
> > junit stuff in its classpath - or at least is should.
> 
> Since we want this to be our version of JUnit and not some arbitrary
> other one, we should hope the plugin recognizes jar overrides and make
> Gump add junit to the project.properties.
> 
> I'll just throw in a dependency on JUnit and we'll see what's going to
> happen.
> 
> Stefan
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org


Mime
View raw message