Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 15086 invoked from network); 21 Jul 2002 10:27:56 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 21 Jul 2002 10:27:56 -0000 Received: (qmail 16758 invoked by uid 97); 21 Jul 2002 10:28:13 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 16686 invoked by uid 97); 21 Jul 2002 10:28:13 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 16603 invoked by uid 98); 21 Jul 2002 10:28:12 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3D3A8DA0.5000507@cortexebusiness.com.au> Date: Sun, 21 Jul 2002 20:32:00 +1000 From: Conor MacNeill User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513 X-Accept-Language: en-us, en-au MIME-Version: 1.0 To: Ant Users List Subject: Re: ejbjar: unable to load dependency analyzer References: <0A1FCA1AEC85D311A3E10008C7E6DD640EFAB986@dolphin.gartner.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Bridges,Edward wrote: > indeed, i confirmed that the AncestorAnalyzer class is in fact there: > > c:\>jar tvf c:\ant-1.5\lib\optional.jar > . > . > 3224 Tue Jul 09 11:12:34 EDT 2002 org/apache/tools/ant/util/depend/bcel/AncestorAnalyzer.class > . > . > > i tried both the binary distro and compiling it myself, and i tried using all > three of dependency="[none|super|full]" as the attributes for the ejbjar task. > > thanks! > --e-- > Edward, Let me just explain what is going on and let's see where we go from there. Firstly, the 1.4.1 behaviour was to add the super classes of all bean classes into the generated jar. This was a minimal attempt to ensure that dependent classes were included in the jar. This feature was implemented using reflection which required the classes to be loaded into Ant's VM. This was undesirable for a few reasons especially the need to get the classpaths right. In Ant 1.5, the mechanism was changed to use BCEL. This has two benefits - the bean classes are no longer loaded into the Ant VM and a fuller dependency analysis was possible. The dependency attribute was introduced to give more control over this feature. I think the behaviour of the various options are covered in the documentation. The default value, "super" is there for backward compatability. The contents of any jars generated should be the same between 1.4 and 1.5 with this option. This option *requires* BCEL. The version of BCEL required is 5.0. Later versions should work if BCEL maintains backward compatibility. You say you have tried "none". This should always work since it performs no dependency analysis at all. You should get no warnings. Is this the case? If you have the BCEL jar and the other options do not work - i.e. they give a warning, can you check the integrity of the BCEL jar (jar tvf bcel.jar should do it). Conor -- To unsubscribe, e-mail: For additional commands, e-mail: