[
https://issues.apache.org/jira/browse/GORA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157312#comment-13157312
]
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
{code}
<property name="project.dir" value="${basedir}/.."/>
{code}
In build.xml it exists as
{code}
<property name="project.dir" value="${basedir}"/>
{code}
and in each module's ivy/ivy.xml it is used in the following context.
{code}
<include file="${project.dir}/ivy/ivy-configurations.xml"/>
{code}
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: https://issues.apache.org/jira/browse/GORA-42
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
