On Fri, 3 Dec 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote:
It was. So I entered this fix.
Thanks
I've no idea if Stefan's original issue (what he went in to fix) was
resolved.
It was. The original code would ignore jvmargs that were nested
into ant or maven, it expected them to be
On Sun, 05 Dec 2004, Stefano Mazzocchi [EMAIL PROTECTED] wrote:
We never noticed that xerces dependeded on that library before
This is not really true. We once had a Gump build that broke because
Xerces-J required xml-resolver about two weeks ago. And on the next
build everything succeeded.
On Fri, 3 Dec 2004, Ian P. Springer [EMAIL PROTECTED] wrote:
I'm looking into fixing the wsdl4j and naming deps for Apollo, but
I'm unsure how the Gump / Maven combo works. Is it that the Gump
dep's name must match the Maven dep's artifactId?
No. I think Gump's id attribute on the jar
For example, one of our Maven deps has artifactId axis-wsdl4j, but
the wsdl4j Gump project's jar name is wsdl4j.
Then I really think your Maven dep is wrong since wsdl4j is not
produced by Axis and shouldn't be considered part of Axis IMHO.
It appears the correct ID is axis:axis-wsdl4j,
On Mon, 6 Dec 2004, Brett Porter [EMAIL PROTECTED] wrote:
For example, one of our Maven deps has artifactId axis-wsdl4j,
but the wsdl4j Gump project's jar name is wsdl4j.
Then I really think your Maven dep is wrong since wsdl4j is not
produced by Axis and shouldn't be considered part of
| For example, one of our Maven deps has artifactId
| axis-wsdl4j, but
| the wsdl4j Gump project's jar name is wsdl4j.
|
| Then I really think your Maven dep is wrong since wsdl4j is not
| produced by Axis and shouldn't be considered part of Axis IMHO.
|
| It appears the correct ID is
Folks,
I just saw the failure at
http://brutus.apache.org/gump/public/xml-xerces2/xml-xerces/gump_work/build_xml-xerces2_xml-xerces.html
i recreated the failure by hand on brutus and was able to come up with
a possible fix, which basically to drop
1) get a real OS*
2) alternatively, get Cygwin*
3)
cd F:\data\Python\gump-svn\python
svn up
sh ./gump test
should now sort-of work.
* I built a convenience thin shell wrapper. You could also just take a
look at what it does; its really straightforward
Adam Jack wrote:
Also, could somebody
Stefano,
I converted the docs I wrote a while back to html (trunk/src/xdocs).
Hope you find time to wire 'em into dynagump. Lemme know if I can do
anything there :-D
cheers,
- LSD
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
I've been working for a while to describe an improved architecture for
Gump and I have decided to go public with the discussion because I
want this to be a community effort.
- o -
First and foremost, I believe that gump is one of the most exiting
things happening
Leo Simons wrote:
Stefano,
I converted the docs I wrote a while back to html (trunk/src/xdocs).
Hope you find time to wire 'em into dynagump. Lemme know if I can do
anything there :-D
Nice! Will do! thanks mate!
--
Stefano.
-
To
Stefano Mazzocchi wrote:
Comments?
Not really. Most of it sounds obvious by now, actually :-D
More images related to this architecture are at:
http://svn.apache.org/repos/asf/gump/trunk/src/xdocs/gump.pdf
though I'm afraid some of the comments in the gump.ppt alongside there
didn't make
It just dawned on me I zapped it, but for the testing (HEAD) code-base not
the production one. I could update that, and I will. We gotta stop the spam.
Also, there is something weird going on inside Gump's states. There seems to
be an Unset state getting inserted, hence breaking the do not spam
We got a lot of this today:
internal-test:
[mkdir] Created dir:
/home/gump/workspaces2/public/workspace/jelly-tags/junit/target/test-reports
[junit] Running org.apache.commons.jelly.tags.junit.TestJUnit
[junit] Exception in thread main java.lang.NullPointerException
[junit] at
Adam,
I've been scratching my head to figure out what is going on with those
unit tests.
* Is it true that they *depend* on one another and need to execute in a
particular order? What is the nature of that dependency and how can we
remove it?
* How can I figure out what tests need what
On Tue, 7 Dec 2004, Dion Gillard [EMAIL PROTECTED] wrote:
Is there some change internal to gump or do we have to add xml-apis
to our dependencies?
Yes and yes 8-)
xerces no longer publishes xml-apis.jar so all builds that used their
xerces dependency to get access to DOM and friends will now
On Mon, 6 Dec 2004, Ian P. Springer [EMAIL PROTECTED] wrote:
| For example, one of our Maven deps has artifactId
| axis-wsdl4j, but
| the wsdl4j Gump project's jar name is wsdl4j.
|
| Then I really think your Maven dep is wrong since wsdl4j is not
| produced by Axis and shouldn't be
On Tue, 7 Dec 2004, Brett Porter [EMAIL PROTECTED] wrote:
There are probably 3 solutions:
1) change the gump IDs to match (project axis, id axis-wsdl4j?)
2) map the gump ID with an additional file as Stefan mentioned earlier
3) add the ability to map to a different gump ID in the project.xml
18 matches
Mail list logo
