Yes, that was the breakdown I was looking for. Your thread w/ Rod seems to be needing a similar solution. Rod and I can try to work together to tackle this if you really think it's about a day's effort -- of course I realize that's a day for you given your familiarity w/ the M2 codebase.
Can you point us in the right direction? We will be glad to follow your pin-point instructions to make the changes. Seriously, the more details you can provide the less time it will take us to get oriented since I'm not familiar with the Maven codebase at all. Looking forward to helping if we can. Thanks, Derek On 8/4/05, Brett Porter <[EMAIL PROTECTED]> wrote: > On 8/5/05, Derek Lane <[EMAIL PROTECTED]> wrote: > > So what I hear you saying now, is that I won't be able to use M2 until > > the compiler forking > > feature is added. Bummer. > > Sorry to say it does appear that way, if you are to use it out of the box. > > > I was really hoping to avoid converting this codebase to M1, only to > > have to conver the > > build again to M2 soon thereafter. Please tell me if I've missed what > > you are saying and > > let me know what options I have for resolving this with the current > > alpha-3 M2 release. > > The following options are available: > - wait until the compiler plugin has this feature (I would say some > time this month) > - implement the feature in the compiler plugin and contribute it back > (I'd estimate this is less than a day's work) > - use the ant run plugin to compile the sources using an the Ant javac > task (see the FAQ on the website) > > Hope this helps. > > - Brett > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
