BCEL.jar dependency issue

["Kuram, Harish" <ha...@capitalone.com>]

All,
  I found this blurb in the WHATSNEW file in the binary distribution of Ant
1.5.1
I didn't use the "dependency" to add new files but the <ejbjar> task
completed and the jar files looks OK. 
I am yet to do runtime testing of the jar file.

* <ejbjar> now allows control over which additional classes and interfaces
  are added to the generated EJB jars. A new attribute "dependency" can be
  defined which controls what classes are added. The addition of classes now
uses
  the Jakarta-BCEL library rather than reflection, meaning bean classes are
  no longer loaded into Ant's JVM. The default dependency analyzer is known
as
  the ancestor analyzer. It provides the same behaviour as the 1.4.1 version
of
  <ejbjar>. If the BCEL library is not present, a warning will be issued
stating
  the ancestor analyzer is not available. In this case <ejbjar> will
continue
  to function but will not add super classes to the jar.

harish
 
**************************************************************************
The information transmitted herewith is sensitive information intended only
for use by the individual or entity to which it is addressed. If the reader
of this message is not the intended recipient, you are hereby notified that
any review, retransmission, dissemination, distribution, copying or other
use of, or taking of any action in reliance upon this information is
strictly prohibited. If you have received this communication in error,
please contact the sender and delete the material from your computer.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: BCEL.jar dependency issue

[Conor MacNeill <co...@cortexebusiness.com.au>]

Kuram, Harish wrote:
> All,
>   I found this blurb in the WHATSNEW file in the binary distribution of Ant
> 1.5.1
> I didn't use the "dependency" to add new files but the <ejbjar> task
> completed and the jar files looks OK. 
> I am yet to do runtime testing of the jar file.
> 

It should be fine unless you have some inheritance, which is relatively 
rare. If you want to get rid of the warning, set the dependency attribute to 
"none"

Conor



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>