On 8/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> On 13 Aug 07, at 12:13 AM 13 Aug 07, Shane Isbell wrote:
>
> >
> >
> > From my perspective, I am growing more conscious of the growing divide
> > between Maven and NMaven and am trying to make sure that I do not
> > duplicate
> > something that already exists or vice versa. That is why I want to
> > bring
> > this proposal up for discussion. One of the key questions in this
> > discussion
> > is: do we need a common solution? If I am the only one encountering
> > this
> > problem, and there is no anticipation - from those doing C/C++ or
> > other
> > language support - of this problem occurring in their respective build
> > environments, then everyone going there own way makes sense. I do
> > not want
> > to abstract a problem that does not exist in a general sense.
> >
>
> I don't believe for a second that we can't come up with a super to
> deal with grabbing and laying down some files somewhere which is
> basically what this all amounts to. If we're not using the same

Exactly! It's not a lot more complicated that. We just need to know:
1) where do I install/copy the artifact? 2) which class knows how to
install it? and maybe 3) where do I get that class?

> mechanisms i.e. you're using a different resolver, not using POMs
> locally and doing whatever else differently then it's not really
> Maven. I don't think it's going to be that hard to make something
> that works for Java, C/++, and .net.
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder and PMC Chair, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to