Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Message-ID: <013901c44818$f51c3ce0$3d37a8c0@bbarkerxp>
From: "Bill Barker" <wbarker@wilshire.com>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
References: <9C5166762F311146951505C6790A9CF80229BA31@US-VS1.corp.mpi.com>
Subject: Re: Gump build failures
Date: Tue, 1 Jun 2004 13:42:29 -0700
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_1086122507-26546-125"

------------=_1086122507-26546-125
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Yup, it seems that the Struts team has changed things about a year ago so
that the admin doesn't work with it anymore.  For debugging this one, it is
probably enough to build Tomcat against a CVS co of struts.

In general, you can co gump to a machine with python installed and debug the
entire process.  However, I haven't had to do this for TC for a very long
time.  Mostly the changes to the TC descriptors have been pretty straight
forward (e.g. when beanutils split into two projects).

----- Original Message -----
From: "Shapira, Yoav" <Yoav.Shapira@mpi.com>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Sent: Tuesday, June 01, 2004 1:10 PM
Subject: Gump build failures


Hi,
Looking at http://gump.covalent.net/log/jakarta-tomcat-5.html, I see
Gump failed to build because of admin webapp compilation errors that
appear related to the Struts version used.

What is our process for debugging this?  Are we responsible to ensure
the Gump builds succeed?  Who owns the "build.properties" file and
similar configuration files to building on Gump?

Yoav Shapira
Millennium Research Informatics


This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential, proprietary
and/or privileged.  This e-mail is intended only for the individual(s) to
whom it is addressed, and may not be saved, copied, printed, disclosed or
used by anyone else.  If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the
sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


------------=_1086122507-26546-125
Content-Type: text/plain; name="disclaimer.txt"
Content-Disposition: inline; filename="disclaimer.txt"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.411 (Entity 5.404)


This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail.


------------=_1086122507-26546-125
Content-Type: text/plain; charset=us-ascii

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
------------=_1086122507-26546-125--