Ant build file problem

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Ant build file problem

Rodriguez, Adrian
We are currently using Ofbiz as a component in our project.  Part of our
build process involoves checking out ofbiz (local copy on SVN) and
building it.  Our main build file has an "integration" target that
CruiseControl runs.  The integration target uses an "ant" task to call
the ofbiz build file.  However, there are errors that come up.  

For example,  Our "clean" target will first call the clean target in the
ofbiz build file.  Here is the output:

BUILD FAILED
E:\dev\someproject\build.xml:63: The following error occurred while
executing this line
E:\dev\someproject\ofbiz\build.xml:78: The following error occurred
while executing this line
E:\dev\someproject\ofbiz\hot-deploy\somecomponent\build.xml:61: The
following error occurred while executing this line:
e:\dev\someproject\build.xml:63: Basedir E:\dev\someproject\ofbiz\ofbiz
does not exist

The same sort of errors happen when we call run-tests from our build
file.

I'm not sure why it's trying to say that the basedir is
e:\dev\someproject\ofbiz\ofbiz when I clearly state that the basedir is
e:\dev\someproject\ofbiz.

<ant dir="e:\dev\someproject\ofbiz" target="clean" inheritAll="false" />

Has anyone run into this?  Any help would be great.

thanx =)

<adrian />


Reply | Threaded
Open this post in threaded view
|

Re: Ant build file problem

cjhowe
As OFBiz OOTB doesn't require much (any) Ant knowledge at all, I'm not
sure how great an answer you're going to get on this. I'm not sure
there's a whole lot ant expertise among the general community.  I could
certainly be wrong on that.  There seem to be some JUnit people popping
up, they may be able to shed some light on the subject.

With my limited knowledge, I guess it begs the simple question...

What happens when you change:
<ant dir="e:\dev\someproject\ofbiz" target="clean" inheritAll="false"/>

to:

<ant dir="e:\dev\someproject" target="clean" inheritAll="false"/>

If that fails, I would guess then there is something in Ofbiz build
that is declaring an additional ofbiz.  If it runs, then your custom
build file is declaring the extra ofbiz.  Sound about right?

--- "Rodriguez, Adrian" <[hidden email]> wrote:

> We are currently using Ofbiz as a component in our project.  Part of
> our
> build process involoves checking out ofbiz (local copy on SVN) and
> building it.  Our main build file has an "integration" target that
> CruiseControl runs.  The integration target uses an "ant" task to
> call
> the ofbiz build file.  However, there are errors that come up.  
>
> For example,  Our "clean" target will first call the clean target in
> the
> ofbiz build file.  Here is the output:
>
> BUILD FAILED
> E:\dev\someproject\build.xml:63: The following error occurred while
> executing this line
> E:\dev\someproject\ofbiz\build.xml:78: The following error occurred
> while executing this line
> E:\dev\someproject\ofbiz\hot-deploy\somecomponent\build.xml:61: The
> following error occurred while executing this line:
> e:\dev\someproject\build.xml:63: Basedir
> E:\dev\someproject\ofbiz\ofbiz
> does not exist
>
> The same sort of errors happen when we call run-tests from our build
> file.
>
> I'm not sure why it's trying to say that the basedir is
> e:\dev\someproject\ofbiz\ofbiz when I clearly state that the basedir
> is
> e:\dev\someproject\ofbiz.
>
> <ant dir="e:\dev\someproject\ofbiz" target="clean" inheritAll="false"
> />
>
> Has anyone run into this?  Any help would be great.
>
> thanx =)
>
> <adrian />
>
>
>