incubator-gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lewis John McGibbney (Commented) (JIRA)" <>
Subject [jira] [Commented] (GORA-42) version declared in both build.xml and build-common.xml
Date Fri, 25 Nov 2011 21:51:40 GMT


Lewis John McGibbney commented on GORA-42:

Ok so the problem here lies with the ${project.dir} property.

In build-common.xml it exists as 
<property name="project.dir" value="${basedir}/.."/>

In build.xml it exists as 
 <property name="project.dir" value="${basedir}"/>

and in each module's ivy/ivy.xml it is used in the following context.
<include file="${project.dir}/ivy/ivy-configurations.xml"/>

The subsequent effect is that Eclipse is extremely confused and states that no ivy file exists
in each location due to the fact that it's misinterpreting ${project.dir}. We need to change
one of the occurrences. There are several occurences of the variable in both build & build-common.xml

Any preferences which one get changed?
> version declared in both build.xml and build-common.xml
> -------------------------------------------------------
>                 Key: GORA-42
>                 URL:
>             Project: Gora
>          Issue Type: Bug
>          Components: build process
>    Affects Versions: 0.1-incubating, 0.1.1-incubating
>            Reporter: Chris A. Mattmann
>            Assignee: Lewis John McGibbney
>             Fix For: 0.2-incubating
>         Attachments: GORA-42-v2.patch, GORA-42.patch, NUTCH-42.patch
> the ${version} property is defined in both build.xml, *and* build-common.xml. This is
confusing. We should decide on one place, and then just put it there and remove it from the
other one.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message