[
https://issues.apache.org/jira/browse/NUTCH-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072823#comment-14072823
]
Lewis John McGibbney commented on NUTCH-1755:
---------------------------------------------
Mmmm... we'll I think if they are hardcoded then it is better because at least
it shows up on the at output.
I also feel however that this is a larger issue surrounding the use of
default.properties in general. There is a LOT of dulication with regards to
Javadoc, plugin's Java-documentation, and properties in general which I wonder
if we could remove default.properties altogether and just use everything in
build.xml?
Anyone have thoughts on this one?
> Project name bug in build.xml
> -----------------------------
>
> Key: NUTCH-1755
> URL: https://issues.apache.org/jira/browse/NUTCH-1755
> Project: Nutch
> Issue Type: Bug
> Components: build, nutchNewbie
> Affects Versions: 1.8, 2.2.1
> Reporter: Lewis John McGibbney
> Priority: Minor
> Labels: nutchNewbie
> Fix For: 2.4
>
>
> When one enters an incorrect ant target as follows, you can see that project
> name is presented to us as "${name}". This should resolve to final.name value
> in default.properties
> http://svn.apache.org/repos/asf/nutch/branches/2.x/default.properties.
> I would imagine that this bug exists in both 1.X branch and 2.x.
> lewismc@vm-0:~/apache/2.x$ ant plugins-test
>
>
> Buildfile: /home/sarahp098/apache/2.x/build.xml
> Trying to override old definition of task javac
> [taskdef] Could not load definitions from resource
> org/sonar/ant/antlib.xml. It could not be found.
>
> BUILD FAILED
> Target "plugins-test" does not exist in the project "${name}".
--
This message was sent by Atlassian JIRA
(v6.2#6252)
