Hi,
On 06/09/10 23:07, Benson Margulies wrote:
Glenn,
FBOFW, it's clear that a number of core contributors (including the PMC
chair!) in fop-land are exceedingly Maven-averse. It's not that rare of a
viewpoint in the FOSS community.
All that dependency stuff can be done by borrowing
I’ve been following this discussion with interest. Thanks to Benson,
Craig and Glen for demystifying Maven a bit.
I wanted to share my thoughts about that before going offline for 10
days, but it looks like it’s going to have to wait.
Vincent
Le 06/09/2010 15:17, Jeremias Maerki a écrit :
On Fri, Sep 10, 2010 at 3:51 AM, Vincent Hennebert vhenneb...@gmail.comwrote:
On 07/09/10 10:10, Craig Ringer wrote:
On 7/09/2010 4:40 PM, Jeremias Maerki wrote:
snip/
... then it'd look for local/somejar-2.2.jar within my local repository.
If I put the jar where it should be found, no
On 07/09/10 10:10, Craig Ringer wrote:
On 7/09/2010 4:40 PM, Jeremias Maerki wrote:
snip/
Anyway, I won't to stand in the way
if something is added to FOP that can help some users. [snip] just
because Maven
can't include a simple JAR that is not in a repository.
Not strictly true. One
ok; but is there any reason not to commit the patch to permit those who find
maven useful to use it? there are many features in FOP that cater to
specific interests, why not permit that with the build process as well?
regards,
glenn
On Tue, Sep 7, 2010 at 1:52 PM, Jeremias Maerki
Because I want to hear other opinions from the other committers first.
So far, none of the others responded. And I've stated in the past I
won't spend any more time on anything Maven-related, so I'm unlikely to
process the patch myself. I won't veto the addition but I certainly
won't spend any
By the way, I live in a third world country (Philippines) with highly
variable connectivity and usually get no more than 20-30kB/s for downloads.
Furthermore, I don't have an IT infrastructure or servers, but am using an
isolated Macbook Pro for my work. Yet, with all that, I have not had any
That's reasonable. I wasn't asking you to personally commit it. I would
commit it myself if I had the privileges, but am dependent on the good
graces of other committers at present. Perhaps someone will volunteer.
G.
On Tue, Sep 7, 2010 at 3:42 PM, Jeremias Maerki d...@jeremias-maerki.chwrote:
On 7/09/2010 1:52 PM, Jeremias Maerki wrote:
Well, Ivy has one fundamental problem in common with Maven that many regard
as a great feature: the repository. Numerous times, I couldn't get a Maven
build to complete successfully because some artifact was temporarily or
permanently unavailable.
On 07.09.2010 09:56:00 Craig Ringer wrote:
On 7/09/2010 1:52 PM, Jeremias Maerki wrote:
Well, Ivy has one fundamental problem in common with Maven that many regard
as a great feature: the repository. Numerous times, I couldn't get a Maven
build to complete successfully because some artifact
On 7/09/2010 4:40 PM, Jeremias Maerki wrote:
I guess we're in a religious dispute here, like PC vs. Mac. So we
can't expect to reach a consensus.
Well, certainly a discussion of preference. I know it gets religious for
some Java folks, but myself I don't mind too much so long as nobody
On Tue, Sep 7, 2010 at 4:40 PM, Jeremias Maerki d...@jeremias-maerki.chwrote:
Due to its inflexibility, projects are
almost forced to adopt it to keep everyone happy, just because Maven
can't include a simple JAR that is not in a repository.
Perhaps this has changed, because while I was
I want to inject one fact, and one collection of experience, but I'm still
not trying to talk anyone into anything.
Fact: the Apache Software Foundation maintains a comprehensive maven
infrastructure. There is a repository manager, there are standard parent
POMS. All projects that use Maven get
On 7/09/2010 7:22 PM, Benson Margulies wrote:
I've never seen a message to one of the mailing lists
complaining that connectivity issues were making people miserable. Why? You
need connectivity to update from svn. Then you need connectivity to run a
build.
... and to get any libraries or other
On Tue, Sep 07, 2010 at 03:44:37PM +0800, Glenn Adams wrote:
That's reasonable. I wasn't asking you to personally commit it. I would
commit it myself if I had the privileges, but am dependent on the good
graces of other committers at present. Perhaps someone will volunteer.
On Tue, Sep 7,
On Tue, Sep 07, 2010 at 08:47:16PM +0800, Craig Ringer wrote:
Meh. I'd like to see maven support in fop, but I'm not working with
fop's code much at all so it's hardly something I can claim any say
in. Maybe I should bash together an ant task to spit out Maven
artifacts after a build,
I'd generally encourage the use of the ant-to-maven wiring I supplied for
maven publication. Adding the ant maven tools to the standard build (or
using ivy?) would allow very quick consumption of FOP jars by Maven-built
applications, which I guess would be the goal here.
On Mon, Sep 6, 2010 at
Glenn,
FBOFW, it's clear that a number of core contributors (including the PMC
chair!) in fop-land are exceedingly Maven-averse. It's not that rare of a
viewpoint in the FOSS community.
All that dependency stuff can be done by borrowing maven dependencies in
ant, either via the maven ant tools
Craig,
Thanks for the additional pointers. This was my first time to use maven to
be honest. Since it is an Apache tool, I thought that perhaps using it would
help me integrate better with common Apache tools.
I did had to struggle a bit with some of the configuration ... *and* consult
the
Well, Ivy has one fundamental problem in common with Maven that many regard
as a great feature: the repository. Numerous times, I couldn't get a Maven
build to complete successfully because some artifact was temporarily or
permanently unavailable. Introducing an external repository immediately
20 matches
Mail list logo
