Dear Gumpmeisters,
The following 13 notifys should have been sent
*** G U M P
[EMAIL PROTECTED]: Module xdoclet success, but with warnings.
[EMAIL PROTECTED]: Module wsdl4j success, but with warnings.
[EMAIL PROTECTED]: Module
Hi all, Brett in particular,
if I understand it correctly, Maven wouldn't see a plugin if we only
add it to the CLASSPATH and add jar overrides for it. So a plugin,
like the xdoclet-plugin needed by Struts Taglib needs to get installed
manually.
Is this correct?
Stefan
On Mon, 4 Apr 2005, Brett Porter [EMAIL PROTECTED] wrote:
They should really be declaring a plugin dependency,
I guess they don't do because the XDoclet page[1] doesn't explain how to
do that
You should put it in ~/.maven/plugins
Done.
The only version I found at ibiblio is 1.2.1 while
Adam R. B. Jack wrote:
Dear Sir/Madam,
I was taking a quick look into why this build [1] for XSDLIB [2] started
failing on Apache Gump [3]. (It is a project with a lot of dependees, see
[4]) It seems that this class (amongst, perhaps others) is not being built,
or not being placed on the
I keep receiving the attached nag from Gump. I am not able to determine the
problem from the
information given. I have verified that the project (Dumbster
http://brutus.apache.org/gump/public/dumbster/) builds and tests fine when
checked out from CVS on
various machines other than my own.
So
So why does Gump think there is a problem here ?
It is something to do with the tests failing. Does Dumpster open some ports
and try to connect to it? [Or, is it all in memory?]
http://brutus.apache.org/gump/public/dumbster/dumbster/gump_work/build_dumbster_dumbster.html
test:
[junit]
On Apr 5, 2005 12:06 AM, Jason Kitchen [EMAIL PROTECTED] wrote:
I keep receiving the attached nag from Gump. I am not able to determine the
problem from the
information given. I have verified that the project (Dumbster
http://brutus.apache.org/gump/public/dumbster/) builds and tests fine when
