|
»
»
« Return to Thread: Dissolving Apache NMaven From ASF Incubator
Re: Dissolving Apache NMaven From ASF Incubator
by James Carpenter
::
Rate this Message:
I'll go ahead and state the obvious. Many of us here really like the
idea of .NET support for maven, but very few of us are willing to
devote the time and resources required to really move the ball
forward. Although I am personally willing to contribute minor
enhancements here and there as my own needs arise, I'm not currently
motivated enough to take on a primary contributor role for NMaven.
Though I may disagree with some of Shane's early architectural
decisions which originally took NMaven away from the maven core, Shane
was actively developing NMaven while I largely sat on the sidelines.
Although their opinions seem to vary a bit, I believe the postings by
Shane and Brett collectively provide a fairly clear summary of why the
project has not gained the level of adoption we would all like.
The harsh reality here is that a few individuals and/or an appropriate
company or funder must step up to the plate or NMaven will die. If
anyone reading this is willing to devote the necessary time to the
project, please consider taking on a more active role. If any
potential funder is willing to commit the funding necessary to
maintain steady progress please indicate a willingness to do so or
otherwise take action to engage appropriate individuals. As with any
software project, good senior talent isn't cheap so any funding
probably needs to at least be in the 6 figure range (USD). Much of
this work will involve enhancements to the maven core, which will
probably be more daunting than a junior engineer can easily handle.
On Dec 1, 2008, at 6:26 PM, Caulene Tibbetts wrote:
> I agree, Christian. We are also a large enterprise using both Java
> and
> .NET, and using a Maven-based build process. The clear benefits of
> using
> NMaven are 1) use of the Archiva repository for binaries, 2)
> versioning
> capability, 3) reproducibility, and 4) consistent tooling throughout
> the
> enterprise. We have been working off the 0.14 branch, but would
> love to
> move over to the trunk as soon as the full functionality is available
> there.
>
> The VS interface has proven to be very valuable to us - it makes it
> easy to
> port an existing project over to NMaven, as well as enabling users
> to use
> NMaven for builds within the IDE. There are a few items which could
> still
> be cleaned up, but the main functionality is there.
>
> The key to increasing adoption of NMaven is letting the .NET world
> know
> about the functionality that is available - I've not been able to find
> *any*other product that addresses versioning, reproducibility, or has
> even a
> vague concept of a binary repository.
Sincerely,
James Carpenter
email: jcarpenter621@...
idea of .NET support for maven, but very few of us are willing to
devote the time and resources required to really move the ball
forward. Although I am personally willing to contribute minor
enhancements here and there as my own needs arise, I'm not currently
motivated enough to take on a primary contributor role for NMaven.
Though I may disagree with some of Shane's early architectural
decisions which originally took NMaven away from the maven core, Shane
was actively developing NMaven while I largely sat on the sidelines.
Although their opinions seem to vary a bit, I believe the postings by
Shane and Brett collectively provide a fairly clear summary of why the
project has not gained the level of adoption we would all like.
The harsh reality here is that a few individuals and/or an appropriate
company or funder must step up to the plate or NMaven will die. If
anyone reading this is willing to devote the necessary time to the
project, please consider taking on a more active role. If any
potential funder is willing to commit the funding necessary to
maintain steady progress please indicate a willingness to do so or
otherwise take action to engage appropriate individuals. As with any
software project, good senior talent isn't cheap so any funding
probably needs to at least be in the 6 figure range (USD). Much of
this work will involve enhancements to the maven core, which will
probably be more daunting than a junior engineer can easily handle.
On Dec 1, 2008, at 6:26 PM, Caulene Tibbetts wrote:
> I agree, Christian. We are also a large enterprise using both Java
> and
> .NET, and using a Maven-based build process. The clear benefits of
> using
> NMaven are 1) use of the Archiva repository for binaries, 2)
> versioning
> capability, 3) reproducibility, and 4) consistent tooling throughout
> the
> enterprise. We have been working off the 0.14 branch, but would
> love to
> move over to the trunk as soon as the full functionality is available
> there.
>
> The VS interface has proven to be very valuable to us - it makes it
> easy to
> port an existing project over to NMaven, as well as enabling users
> to use
> NMaven for builds within the IDE. There are a few items which could
> still
> be cleaned up, but the main functionality is there.
>
> The key to increasing adoption of NMaven is letting the .NET world
> know
> about the functionality that is available - I've not been able to find
> *any*other product that addresses versioning, reproducibility, or has
> even a
> vague concept of a binary repository.
Sincerely,
James Carpenter
email: jcarpenter621@...
« Return to Thread: Dissolving Apache NMaven From ASF Incubator
| Free embeddable forum powered by Nabble | Forum Help |
