On Monday 23 June 2003 11:43, Martin Cooper wrote:I had tried creating a second project in Gump. Use CVS to look at the previos versions of the jakarta-struts.xml file.
On Mon, 23 Jun 2003, James Mitchell wrote:
On Monday 23 June 2003 11:18, Christopher Lenz wrote:No, any Jakarta committer can fix it. The issue is one of figuring out how
Yes, that sounds like what I was vaguely remembering.I don't think the Gump builds have anything todo with the nightly builds of Struts. The Gump descriptors are in the jakarta-gump directory on cvs.apache.org, and every Apache committer has commit access to that directory.
http://jakarta.apache.org/gump/
So, at this point, noone can fix this but Craig?
to modify the Struts Gump descriptor to build struts-legacy first, and
then have the main build refer to that. Any committer can check in the
change, we just need to figure out what that change looks like. ;-)
Ok ok!! So I'm lazy ;) I finally got around to reading this: http://jakarta.apache.org/gump/faq.html
So, unless anyone else gets to it first, I'll try to fix this tonight.
From the GUMP output it appears that the struts-legacy project worked. I used that as a dependancy for the
'struts-core' project and that is where it couldn't find the struts-legacy.jar.
James,
Let me give it --one-- more shot tonight.
I believe what I need to do is not copy the struts-legacy.jar with the other jars at first but delay it's copying
until after it is built.
-Rob
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
