ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Reilly <peter.kitt.rei...@gmail.com>
Subject Re: Gertting "Reference <ejb.classpath> not found" while using Ant 1.8 RC1
Date Thu, 28 Jan 2010 15:43:03 GMT
This happens when an id is defined in a target that is not run,
for example:

<project default="abc">
   <target name="abc">
       <... use id x here >
   </target>

   <target name="not_run">
     <fileset id="x" ...>
   </target>
</project>

The warning in 1.7.x was that x was not defined, so ant would read the
full build file and find a random x id and use that one. This causes a
lot of problems ... and the ant code to do this was difficult to maintain.
So on ant 1.7 the big dirty warning message was placed in - and many
years later (the "future" in  the warning message), the hacking code
in ant has been removed.


Peter

On Thu, Jan 28, 2010 at 2:57 PM, Suman N <Suman.N@curamsoftware.com> wrote:
> Hi,
>
> When using Ant 1.7, I get the following warning.
>
> Warning: Reference ejb.classpath has not been set at runtime, but was found during
> build file parsing, attempting to resolve. Future versions of Ant may support
>  referencing ids defined in non-executed targets.
>
> I understand that I am doing something wrong here. I am new to Ant and I don’t understand
what a non-executed target is.
> Can you please suggest what should be done to rectify the issue, while using 1.8RC1?
>
> Thanks,
> Suman.N
> -----Original Message-----
> From: Peter Reilly [mailto:peter.kitt.reilly@gmail.com]
> Sent: 28 January 2010 15:27
> To: Ant Developers List
> Subject: Re: Gertting "Reference <ejb.classpath> not found" while using Ant 1.8
RC1
>
> When using ant 1.7, did you see a warning about references?
>
> Peter
>
> On Thu, Jan 28, 2010 at 9:12 AM, Suman N <Suman.N@curamsoftware.com> wrote:
>> Hi,
>>
>>
>>
>> We are testing the compatibility of our build scripts with Ant 1.8 RC1 and
>> we encounter the following error when referring a path refid in our script.
>>
>>
>>
>>
>>
>> D:\CC\suman.n_TI_MAIN_3\TIVOB\build_scripts\test.xml:579: The following
>> error occurred while executing this line:
>>
>> D:\CC\suman.n_TI_MAIN_3\TIVOB\build_scripts\test.xml:632: The following
>> error occurred while executing this line:
>>
>> D:\CC\suman.n_TI_MAIN_3\TIVOB\build_scripts\test.xml:672: The following
>> error occurred while executing this line:
>>
>> D:\CC\suman.n_TI_MAIN_3\TIVOB\build_scripts\test.xml:703: Reference
>> ejb.classpath not found.
>>
>>
>>
>> We are defining a path element in the ‘wlstest’ target (Line 573 in attached
>> test.xml)
>>
>>
>>
>>
>>
>>
>>
>> <target name="wlstest"
>>
>>           description="Runs in-container tests against WLS and produces
a
>> report.">
>>
>>
>>
>>     <antcall target="clean" inheritAll="false"/>
>>
>>
>>
>>     <path id="ejb.classpath">
>>
>>       <pathelement location="${WLS_HOME}/lib/weblogic.jar"/>
>>
>>     </path>
>>
>>
>>
>>     <!-- 36877: Must set inheritall to true here, or the test failure
>> override
>>
>>          does not get propagated and clover fails before producing a report.
>> -->
>>
>>     <antcall target="wlstest.without.clean" inheritAll="true"/>
>>
>>
>>
>>   </target>
>>
>>
>>
>>
>>
>> We refer to this “path” in another part of the build script: (line 719 in
>> the attached test.xml file)
>>
>>
>>
>>       <classpath>
>>
>>         <path refid="junit.common.classpath"/>
>>
>>         <path refid="ejb.classpath"/>
>>
>>         <path refid="zos.ejb.classpath"/>
>>
>>         <path refid="nas.ejb.classpath"/>
>>
>>         <pathelement path="${jar.wsdl4j}"/>
>>
>>         <!-- stubs of the beans -->
>>
>>         <pathelement path="${dir.test.lib}/stubs.jar"/>
>>
>>       </classpath>
>>
>>
>>
>> The build script basically tests all the tests which depend on the
>> application server (Oracle weblogic in this case).
>>
>> This error does not occur when using Ant 1.7.0 version.
>>
>> Can  you please let me know what has changed in Ant 1.8 RC1 that is causing
>> the issue. Please let me know the workaround or fix for this?
>>
>>
>>
>> Cheers,
>>
>> Suman.N
>>
>> The information in this email is confidential and may be legally privileged.
>> It is intended solely for the addressee. Access to this email by anyone else
>> is unauthorized. If you are not the intended recipient, any disclosure,
>> copying, distribution or any action taken or omitted to be taken in reliance
>> on it, is prohibited and may be unlawful. If you are not the intended
>> addressee please contact the sender and dispose of this e-mail. Thank you.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@ant.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
>
> The information in this email is confidential and may be legally privileged.
> It is intended solely for the addressee. Access to this email by anyone else
> is unauthorized. If you are not the intended recipient, any disclosure,
> copying, distribution or any action taken or omitted to be taken in reliance
> on it, is prohibited and may be unlawful. If you are not the intended
> addressee please contact the sender and dispose of this e-mail. Thank you.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>

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


Mime
View raw message