On 19 Dec 06, at 5:52 AM 19 Dec 06, Steve Loughran wrote:
Jason van Zyl wrote:
Yah, I don't buy it. I don't know anyone who uses RPMs to do
anything with Java.
Nobody who works java does, but the goal is to let people who work
with OSS systems use Java apps the way they work with C++, Perl,
python, mono and ruby code --with one central management tool and
without caring what language they are writtien on.
I would have to be frank and say I'm not really interested in the
lowest common denominator. The mail from the complainer has no
qualification whatsoever. People have complained in the past about
everything from Make, Ant, and now Maven. What is ridiculous is that
the project itself, in this case JLine, moved to Maven because it's
easier for them and JPackage people are complaining because it's no
long easy for them.
Jason.
ps, from the jpackage mail list:
---------------
-------- Original Message --------
Subject: Re: [JPackage-discuss] Jline update
Date: Mon, 18 Dec 2006 06:13:04 -0500
From: David Walluck
Reply-To: Discussion about JPackage project <jpackage-
[EMAIL PROTECTED]>
To: Discussion about JPackage project <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alexander Kurtakov wrote:
> I'm trying to package the JRuby 0.9.2 release for jpackage. I
have already
> made a spec file for jvyaml which is a prerequisite for the JRuby
(attached to
> the mail). I've tried to update the Jline package but due to its
change of
> build process (from ant to maven) I've failed so can somebody
help me.
Someone just needs to create build.xml files for all these
maven-dependent packages. Either some generic build.xml, or a maven to
ant build.xml tool. I thought maven itself had the ability to do that,
but if it requires maven to not require maven, isn't that a bit
pointless?
I hate maven because it makes my life so much more difficult. You
think
as a package builder a tool that is supposed to build things would
make
your life easier. Not only doesn't it make it easier, but how many new
dependencies does it pull in? Probably more than 100 new packages are
required to build/install maven.
- --
Sincerely,
David Walluck
-----------------------------
Its not that the jpackage people want to use maven. its that
without that support anything that uses maven doensnt build any
more. When projects switch from Ant to maven, they drop off gump,
they drop out of jpackage. As far as the rest of the OSS community
is concerned, they drop off the network.
-Steve
---------------------------------------------------------------------
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]
