Jason van Zyl wrote:
I just don't see the value in this for Maven users. Carl what value do
you see as a real benefit to Maven users who work on Redhat?
Jason.
My 2 cents.
I primarily use Linux to develop Java. Here are the steps I use when
installing RHEL 4.0 WS.
1. Install OS.
2. Get current Java version from Sun if I don't already have it.
3. Install java in /opt. Create a link /opt/java to the real java directory.
4. Install maven 1 (sorry, still on that one). Create a link /opt/maven
to the real maven directory.
5. edit /etc/profile.
a. Add definition for JAVA_HOME to /opt/java
b. Add definition for MAVEN_HOME to /opt/maven
c. export the definitions.
d. Add $JAVA_HOME/bin to the front of the path.
e. Add $MAVEN_HOME/bin to the end of the path.
I deliberately place java first in the path so I don't have to uninstall
the java that comes with Linux. If maven came installed in Linux I
would also add it to the front of the path as I would never trust what I
was getting.
In other words, I don't see a lot of value in packaging maven as an RPM
for the general public, although I certainly would have no problem with
Maven delivering an RPM in addition to the zip and gzipped tar that is
currently distributed.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
