On Thursday 07 October 2004 21:37, Stefano Mazzocchi wrote:
> The problem with maven is that I don't know how we can "inject" the
> gump-generated dependency jars into maven.
Brett Porter (Maven expert) is normally around to answer questions on how
Maven operates.
> Does anybody have an idea? w
> -Original Message-
> From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]
> But the *most* serious concern is that we seem to have no way to build
> with Maven and, due to excalibur, this is holding up basically 15
> percent of our projects (including, yes, you guessed right, cocoon).
Stephen,
thanks much for your input. Some comments below.
But the *most* serious concern is that we seem to have no way to build
with Maven and, due to excalibur, this is holding up basically 15
percent of our projects (including, yes, you guessed right, cocoon).
Fast track solution could be to
> 3) the maven integration is poor and hacky
How much do you actually know about this integration? I don't know that it
is poor, and I believe it is not hacky. Where are you getting your
information?
> But the *most* serious concern is that we seem to have no way to build
> with Maven and, due
> -Original Message-
> From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]
> But the *most* serious concern is that we seem to have no way to build
> with Maven and, due to excalibur, this is holding up basically 15
> percent of our projects (including, yes, you guessed right, cocoon).
F
Adam R. B. Jack wrote:
So what is the problem?
Problem is
http://brutus.apache.org/gump/public/excalibur/
maven integration might not be hacky (true, I had no idea we were
injectin stuff in, so I take that back) but it does not work at all.
Now, tell me, is this just a matter of fixing the excali
Disclaimer: it has been weeks/months since I last looked into all this.
Stefano Mazzocchi wrote:
But the *most* serious concern is that we seem to have no way to build
with Maven and, due to excalibur, this is holding up basically 15
percent of our projects (including, yes, you guessed right, coc
> I will assert that maven is the root problem (no offense intended to the
> maven people, I'm rather happy with maven recently otherwise). Maven is
No offense taken :) However, I don't think Maven itself is the problem
- as Adam has said, building works fine until we get to conflicting
dependency