Return-Path: Mailing-List: contact gump-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list gump@jakarta.apache.org Received: (qmail 47177 invoked from network); 24 Apr 2003 13:13:03 -0000 Received: from main.gmane.org (80.91.224.249) by daedalus.apache.org with SMTP; 24 Apr 2003 13:13:03 -0000 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 198gVg-0007Kk-00 for ; Thu, 24 Apr 2003 15:11:32 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gump@jakarta.apache.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 198gVW-0007Ju-00 for ; Thu, 24 Apr 2003 15:11:22 +0200 From: Berin Loritsch Subject: Does Gump ignore the build script? Date: Thu, 24 Apr 2003 09:12:21 -0400 Lines: 16 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en Sender: news X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I edited Fortress's build script to not build the BCEL classes if that library doesn't exist. Unfortunately, the Fortress GUMP build didn't work because it tried to compile those classes. Is there something that was missed? I added the BCEL dependency, but that does pose a potential issue. I think the hardest thing to understanding Gump is that it doesn't uphold the assumptions that you may have about the build process. IOW, just because a build works on your local machine doesn't mean it will work in GUMP--and that is not strictly because another project changed their API. In fact it is more common that it is because the GUMP descriptor is not right. Is there a way to fix that?