Thanx for the hint! It works, but to me it does not seem like a clean solution but rather like a workaround. For one thing my collegues would think that buildr needs hacks for such things, on the other hand I'd like to learn how to do this the "right" way :)
Do you have another suggestion? Or is it not as trivial as I think/hope? Thanx && cheers, Martin On Tue, 2009-07-07 at 14:47 -0700, Alex Boisvert wrote: > Given that repositories.local is global to a Buildr instance, I would > probably define a constant directly on the Eclipse module and use > monkey-patching to override it... only drawback here is that it would > generate a warning about overriding a constant. > > e.g. > module Buildr > module Eclipse > M2_REPO_VAR = 'M2_REPO' > end > end > > > alex > > > On Tue, Jul 7, 2009 at 2:18 PM, Martin Grotzke <[email protected] > > wrote: > > > On Tue, 2009-07-07 at 10:45 -0700, Alex Boisvert wrote: > > > It would be fairly trivial to add, yes. Do you want to take a shot at > > it? > > Yep, I'd like to have a look at it. Can you give me a hint where I can > > have a look to see s.th. similar (remember I'm a java user, new to > > ruby :))? > > > > What's the goal to have? S.th. like > > eclipse.using :repovar=>'MYPROJ_REPO'? > > > > Cheers, > > Martin > > > > > > > > > > alex > > > > > > > > > On Tue, Jul 7, 2009 at 10:27 AM, Martin Grotzke < > > > [email protected]> wrote: > > > > > > > Hi, > > > > > > > > we're changing the local repository (repositories.local) to "./lib". > > > > buildr eclipse generates the .classpath still using the M2_REPO > > > > variable. Is it possible to specify another variable name for this, so > > > > that we could use some "PROJ_REPO" variable? > > > > > > > > Thanx && cheers, > > > > Martin > > > > > > > > > >
signature.asc
Description: This is a digitally signed message part
