Hi Dan, Right now we are taking a fresh look at NMaven to get it integrated with Maven; so provided that it works, there is nothing holding back using such a change from the NMaven side (can't speak about the implications to the Maven core and associated plugins). Anybody have any ideas on how this finalName change would affect the various Maven plugins? The standard maven plugins breaking has always been the biggest headache when dealing with this version issue, which is also one of the reasons for the separate repo with a repository format converter.
Shane On Nov 25, 2007 3:16 PM, dfabulich <[EMAIL PROTECTED]> wrote: > > > > Shane Isbell wrote: > > > > I think the idea of having a separate repository per language/platform > is > > a good one. > > I'm mildly opposed to this, because this is not a language specific > problem. > A small change to the default repository layout would fix this problem for > everyone: just use the <finalName> in the repository layout. IMO this is > the "right answer" for all languages, and should be the future of Maven. > > I wound up taking about a year long hiatus from Maven development, but if > I > get the thumbs-up, I'd happily code up the changes to the DRL in Maven > trunk > right now. The change is small, but it's to something important, so it > requires lots of consensus. > > -Dan > -- > View this message in context: > http://www.nabble.com/Technical-Decisions-Regarding-NMaven--tf4793894.html#a13941288 > Sent from the nmaven-dev mailing list archive at > Nabble.com<http://nabble.com/> > . > >
