I'll defintely take a look at the project site.

No i do not mean the system classpath.  The way my project is layed out in
CVS is pretty typical.  From the top-level directory I have:

build
   / scripts
   / lib
       / weblogic
       / xdoclet
       / java2html
   / com
      / ...
   / deploy

All the xdoclet jars go into the build/lib/xdoclet directory.  I then set up
a classpath ref in the ant script:

        <path id="classpath.xdoclet">
            <fileset dir="${dir.lib}/xdoclet">
                <include name="*"/>
            </fileset>
            <!-- Include weblogic jars for the ejbdoclet weblogic subtask
-->
            <fileset dir="${dir.lib}/weblogic">
                <include name="*"/>
            </fileset>
        </path>


I then prepare the task using that classpath ref:

        <taskdef name="ejbdoclet"
                classname="xdoclet.modules.ejb.EjbDocletTask"
                classpathref="classpath.xdoclet" />

        <ejbdoclet destdir="${dir.src}"
                excludedtags="@version,@author"
                force="false"
                ejbspec="2.0"
                verbose="true">
            <fileset dir="${dir.src}">
                <include
name="com/vignette/it/apps/server/services/beans/*.java"/>
            </fileset>

            <packageSubstitution packages="services.beans"
substituteWith="services.client" />
            <packageSubstitution packages="services.interfaces"
substituteWith="services.client" />

            <remoteinterface pattern="{0}Remote" />
            <localinterface pattern="{0}Local" />
            <homeinterface pattern="{0}RemoteHome" />
            <localhomeinterface pattern="{0}LocalHome" />

            <utilobject cacheHomes="true" />

            <deploymentdescriptor destdir="${dir.meta}"/>

            <weblogic version="6.1" destdir="${dir.meta}"/>

        </ejbdoclet>


This worked using an xdoclet binary version (1.2b2).  I have only had these
problems with my locally built version.




-----Original Message-----
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 01, 2003 8:38 AM
To: [EMAIL PROTECTED]
Subject: Re: [Xdoclet-user] build fails


On Tuesday, April 1, 2003, at 08:51  AM, Ebersole, Steven wrote:
> I don't think I need the maven plugin, as I do not use Maven.  So I 
> tried
> what I think you are suggesting by taking all the jars generated during
> build into the xdoclet/target directory and placing them into my build
> classpath.  But my ant script fails with the below output.

I don't use Maven either and get the build failure for XDoclet builds 
also, and then just use the JAR files built.

I would not recommend you just put XDoclet JAR's in your classpath (do 
you mean system CLASSPATH here?).  Take a look at my JavaDevWithAnt 
project for examples of using XDoclet and where I put the JAR files and 
used pointers to them in the build file.

        http://www.ehatchersolutions.com/JavaDevWithAnt

Erik



-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to