>Add <echo>build.src.dir = ${build.src.dir}</echo> here so you can see
what >it is set to.
Ok here is the output when running the module build script
ejbdoclet:
[echo] src dir=C:\xendev\projects\xibms\securitystatus\build\src
[echo] force=false
[ejbdoclet] Deploy TEMPLATE URL:
jar:file:C:\xendev\projects\xibms\xdoclet-1.2\lib\xdoclet-apache-module-1.2.jar!/xdoclet/modules/apache/axis/ejb/resources/axis-deploy_wsdd.xdt
[ejbdoclet] Undeploy TEMPLATE URL:
jar:file:C:\xendev\projects\xibms\xdoclet-1.2\lib\xdoclet-apache-module-1.2.jar!/xdoclet/modules/apache/axis/ejb/resources/axis-undeploy_wsdd.xdt
[ejbdoclet] Generating Remote interface for
'com.xensia.ejb.impl.SecurityStatusBean'.
[ejbdoclet] Generating Local interface for
'com.xensia.ejb.impl.SecurityStatusBean'.
[ejbdoclet] Generating Home interface for
'com.xensia.ejb.impl.SecurityStatusBean'.
[ejbdoclet] Generating Value Object class:
'com.xensia.ejb.impl.SecurityStatusBean-->
com.xensia.ejb.interfaces.SecurityStatusBeanValue'.
[ejbdoclet] Generating Local Home interface for
'com.xensia.ejb.impl.SecurityStatusBean'.
[ejbdoclet] Generating PK class for 'com.xensia.ejb.impl.SecurityStatusBean'.
[ejbdoclet] Generating BMP class for
'com.xensia.ejb.impl.SecurityStatusBean'.
[ejbdoclet] Generating Util class for
'com.xensia.ejb.impl.SecurityStatusBean'.
[ejbdoclet] Generating EJB deployment descriptor (ejb-jar.xml).
[ejbdoclet] Generating jboss.xml.
When run a second time the generation does not occur. Here the the output
of the master build script:
ejbdoclet:
[echo] src dir=C:\xendev\projects\xibms\securitystatus\build\src
[echo] force=false
[ejbdoclet] Deploy TEMPLATE URL:
jar:file:C:\xendev\projects\xibms\xdoclet-1.2\lib\xdoclet-apache-module-1.2.jar!/xdoclet/modules/apache/axis/ejb/resources/axis-deploy_wsdd.xdt
[ejbdoclet] Undeploy TEMPLATE URL:
jar:file:C:\xendev\projects\xibms\xdoclet-1.2\lib\xdoclet-apache-module-1.2.jar!/xdoclet/modules/apache/axis/ejb/resources/axis-undeploy_wsdd.xdt
[ejbdoclet] Generating Remote interface for
'com.xensia.ejb.impl.SecurityStatusBean'.
[ejbdoclet] Generating Local interface for
'com.xensia.ejb.impl.SecurityStatusBean'.
[ejbdoclet] Generating Home interface for
'com.xensia.ejb.impl.SecurityStatusBean'.
[ejbdoclet] Generating Value Object class:
'com.xensia.ejb.impl.SecurityStatusBean-->
com.xensia.ejb.interfaces.SecurityStatusBeanValue'.
[ejbdoclet] Generating Local Home interface for
'com.xensia.ejb.impl.SecurityStatusBean'.
[ejbdoclet] Generating PK class for 'com.xensia.ejb.impl.SecurityStatusBean'.
[ejbdoclet] Generating BMP class for
'com.xensia.ejb.impl.SecurityStatusBean'.
[ejbdoclet] Generating Util class for
'com.xensia.ejb.impl.SecurityStatusBean'.
[ejbdoclet] Generating EJB deployment descriptor (ejb-jar.xml).
[ejbdoclet] Generating jboss.xml.
>>The I checked the master build file to ensure it was not changing the
>>destdir
>But where is build.src.dir being set? Master build? sub-builds? Keep in
>mind it is tricky to ensure properties are passed down through the
layers.
I have a shared_xml file that contains all the shared properties for the
project, this file is inlined in both the master and module build scripts.
So really build.src.dir is defined in both buils scripts. Incidentaly the
ejbdoclet task is inlined in the same way:
<?xml version="1.0"?>
<!DOCTYPE project [
<!ENTITY shared_properties SYSTEM "../share/xml/shared_properties.xml">
<!ENTITY ejbdoclet SYSTEM "./etc/ejbdoclet.xml">
]>
>The master build file calls the module builds using the ant task e.g:
> <!--
> dependants
> -->
> <target name="dependants"
> description=" - calls dependant modules build scripts">
> <antcall target="modules">
> <param name="target" value="export"/>
> </antcall>
> </target>
>>Since you're at Ant 1.6, I'd recommend you upgrade this to a <macrodef>
>>situation rather than using <antcall> - should speed things up.
Sounds good, will do.
><target name="modules"
> description="-executes the supplied task for all the modules.">
> <ant antfile="build.xml" target="${target}"
> dir="../common" inheritAll="false">
>inheritAll="false" - so where is build.src.dir being set? Do you expect
>its output to go to the master build relative location or the sub-build
>location?
I expect the output source files to be in the build dir of the sub-builds
e.g securitystatus/build/src and thats where they are.
Even if the build.src.dir was in a different location in the master build
than in the sub-build I would expect running it twice on the second run
the generation would not occur as long as xdoclet.force=false. However
running the master build always generates source code. I will try your
macrodef suggestion and also run this on redhat to see if it is a cygwin
issue.
Thanks,
Hoos
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
