maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoffrey De Smet <>
Subject Re: Maven and Fedora
Date Thu, 07 Dec 2006 09:11:40 GMT
User vote (non-binding, on first sight):

+1 for an RPM (because as a non-maven-developer I like it that there can 
only be one maven version installed). I am tired of telling people how 
to install maven and setting their JAVA_HOME etc.

+1 for writing/stabilizing an RPM plugin that builds maven2's RPM (and 
also RPM's for my maven2ized projects :)

-1 for maintaining the RPM's in a separate project instead of a cleanly 
configured RPM-plugin on the maven build

-1 for factoring the maven2 directory - unless system links can solve 
this problem.

With kind regards,
Geoffrey De Smet

Stephane Nicoll wrote, On 2006-12-07 9:12 AM:
> On 12/7/06, Jason van Zyl <> wrote:
>> Define nice? If it's an installation that is different then something
>> standard that users typically get then it is a not a good thing. I
>> can just see the threads now:
>> "I put my global stuff in the /etc/maven/settings.xml and blah blah
>> blah"
>> "In /etc/maven/settings, mine is in $MAVEN_HOME/conf/settings.xml"
>> "I don't have a $MAVEN_HOME/conf"
>> "What version are you using?"
>> "I'm just using what came with Redhat/BSD/Solaris"
>> So instead of having our standard platform neutral single directory
>> structure, we have each distro doing whatever they want. If it was a
>> package that dropped stuff into the standard way we are doing things
>> great. If not then I'm am so strongly -1 to any such work I can't be
>> emphatic enough. It will fracture out user base completely. I frankly
>> don't care about distros, I care about our users and their experience
>> and their ability to communicate with other users regardless of what
>> platform they are on. Having different setups because Redhat/Solaris/
>> BSD feel like doing things different is not a good thing.
> I am +1 on this one and I think it would really break the
> standardization that Maven uses but on the other hand, those RPMs have
> always done this for every product (anyone using jpackage?)
> The next step I see is rpm foo needs maven for some reasons and users
> *have* to install it the with the RPM. This would really be the mess.
> That said, I guess they know what they are doing and they certainly
> know better  users' needs than us.
> Cheers,
> St├ęphane

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message