gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen McConnell" <>
Subject RE: Some progress on Fulcrum Component Builds!
Date Fri, 15 Oct 2004 11:45:08 GMT

> -----Original Message-----
> From: Eric Pugh []
> Sent: 15 October 2004 13:30
> To: Gump code and data
> Subject: RE: Some progress on Fulcrum Component Builds!
> I see!   This makes sense!  Never thought about the impact on name
> on consumers of your code.

Actually - yes.  

There are 142 projects in avalon and a lot of time has gone in to
getting this into a managed and largely automated structure (including
centralized version management).  The convenience of the 3.3 release
packaging is important and is being dealt in a way that properly
addresses the clean classloader content prerequisite.  I.e. there are
compromises to take into consideration and providing that everyone
understands the implications of the compromises I think everyone will be
better off.

> At least not in the way Gump is a consumer.

Well - this is true.  We didn't spot this problem until Niclas added you
into the gump circle.  

> So, because I use a specific version of merlin-unit, I am fine in my
> project.  I can't change it to avalon-merlin-unit until the next
> comes out.

Correct.  This is the downside of the process of getting all of avalon
into a consistent shape.

> However, because of the name change, and Gump using the latest and
> greatest, my project doesn't know about the new version.


> So, in these types of situations, should I just somehow setup a
> that I depend on, which would be the merlin-unit-3.3.0.jar version?

Niclas has already put in place an additional gump descriptor that maps
the avalon-merlin-unit package to the merlin-unit name.

Cheers, Steve.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message