Dunno, I don't use weblogic, so I haven't got the faintest idea about those
tasks.
Here is some sample output for you to decide:
<target name="verify">
<taskdef name="verify" classname="org.jboss.verifier.AntVerifier"/>
<verify file="d:/Projects/BeanSample/build/lib/interest.ear"/>
</target>
verify:
[verify] Verifying D:\Projects\BeanSample\build\lib\interest.ear
[verify] CDBean: Verified.
[verify] Verification of D:\Projects\BeanSample\build\lib\interest.ear
failed.
[verify] Bean : Interest
[verify] Section: 16.2
[verify] Warning: The Bean Provider must specify the fully-qualified name
of the enterprise bean's home interface in the home element.
----- Original Message -----
From: "Niels Verdonk" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 17, 2001 2:02 PM
Subject: RE: EJB-Verifier: Submit code under GNU Lesser General Public
License
> Along those lines, I've always thought what the ejbjar tasks for weblogic
> were doing in ANT.
>
> Niels
> On Tue, 17 Jul 2001, Maurice le Rutte <[EMAIL PROTECTED]> wrote:
>
> > I've coded an optional task 'verifier' that uses JBoss's verifier
> > tool to check if ejb jar files are specificiation compliant.
