Hi, Solution acquired. You keep "merlin-unit" in your Maven descriptors. I have created a new "merlin-unit" project in Gump, which inherits the Jar from avalon-merlin-unit.
Everyone happy :o) Niclas On Friday 15 October 2004 19:29, Eric Pugh wrote: > I see! This makes sense! Never thought about the impact on name changes > on consumers of your code.. At least not in the way Gump is a consumer. > 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 version > comes out. > > 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 "package" > that I depend on, which would be the merlin-unit-3.3.0.jar version? > > Alternatively, should Gump's record for avalon-merlin-unit be annotated > with all the prior names, so that at the end of the run it produces > avalon-merlin-unit-@@DATE@@.jar as well as merlin-unit-@@DATE@@.jar? > > Or lastly, > > Could we just make another project record and just copy everything it does > and change the last line to this: > > <project name="avalon-merlin-unit"> > <license name="central/system/license/LICENSE.TXT"/> > <ant basedir="runtime/merlin/unit"> > <!-- for magic --> > <property name="build.sysclasspath" value="last"/> > <property name="magic.home" reference="home" project="magic"/> > <property name="gump.signature" value="@@DATE@@"/> > > <SNIP/> > <!-- end for --> > <home nested="runtime/merlin/unit/target/deliverables"/> > <jar name="jars/merlin-unit-@@DATE@@.jar"/> > <nag to="[EMAIL PROTECTED]" > from="Magic Integration <[EMAIL PROTECTED]>"/> > </project> > > > Eric > > > -----Original Message----- > > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > > Sent: Friday, October 15, 2004 12:15 PM > > To: Gump code and data > > Subject: Re: Some progress on Fulcrum Component Builds! > > > > On Friday 15 October 2004 19:10, Eric Pugh wrote: > > > I am a little confused.. Why is the behavior of avalon-merlin-unit > > > special/more difficult then any other dependency? > > > > That is due to a name change. > > > > merlin-unit is needed in your Maven descriptor since that has > > been released > > before. > > avalon-merlin-unit is the new name, and that is the Gump > > descriptor generated. > > > > So, when you add <depend project="avalon-merlin-unit"/> you will > > not get the > > proper override for the Maven descriptor, and Maven will report that > > merlin-unit-x-x.jar can not be found. > > > > Cheers > > Niclas > > -- > > +------//-------------------+ > > / http://www.bali.ac / > > / http://niclas.hedhman.org / > > +------//-------------------+ > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- +------//-------------------+ / http://www.bali.ac / / http://niclas.hedhman.org / +------//-------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
