[jira] [Updated] (NUTCH-1561) improve usability of parse-metatags and index-metadata
[
https://issues.apache.org/jira/browse/NUTCH-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Nagel updated NUTCH-1561:
---
Attachment: NUTCH-1561-trunk-v3.patch
New patch: indentation is fixed, tests now pass, default of property
metatags.names now uses , instead of ;.
improve usability of parse-metatags and index-metadata
--
Key: NUTCH-1561
URL: https://issues.apache.org/jira/browse/NUTCH-1561
Project: Nutch
Issue Type: Improvement
Affects Versions: 1.6
Reporter: Sebastian Nagel
Assignee: Sebastian Nagel
Priority: Minor
Fix For: 1.9
Attachments: NUTCH-1561-trunk-v2.patch, NUTCH-1561-trunk-v3.patch,
NUTCH-1561-v1.patch
Usually, the plugins parse-metatags and index-metadata are used in
combination: the former extracts meta tags, the latter adds the extracted
tags as fields to the index.
Configuration of the two plugins differs which causes pitfalls and reduces
the usability (see example config):
* the property metatags.names of parse-metatags uses ';' as separator
instead of ',' used by index-metadata
* meta tags have to be lowercased in index-metadata
{code}
property
namemetatags.names/name
valueDC.creator;DCTERMS.bibliographicCitation/value
/property
property
nameindex.parse.md/name
valuemetatag.dc.creator,metatag.dcterms.bibliographiccitation/value
/property
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (NUTCH-1755) Project name bug in build.xml
[
https://issues.apache.org/jira/browse/NUTCH-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072736#comment-14072736
]
bin wang commented on NUTCH-1755:
-
[~lewismc], right now, the project name in the build.xml is trying to referring
to the variable ${name}. However, even if you change that to ${final.name},
which suppose to be ${name}-${version}. It still won't work. The reason is
because Ant won't parse and get the reference for `default`, `name`, `basedir`
and several other attributes in the project tag, like it will do for the
properties. You can refer to the Project class of ant for more information.
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)
[jira] [Comment Edited] (NUTCH-1755) Project name bug in build.xml
[
https://issues.apache.org/jira/browse/NUTCH-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072736#comment-14072736
]
bin wang edited comment on NUTCH-1755 at 7/24/14 3:11 AM:
--
[~lewismc], right now, the project name in the build.xml is trying to referring
to the variable ${name}. However, even if you change that to ${final.name},
which suppose to be $ { name } - $ { version }. It still won't work. The reason
is because Ant won't parse and get the reference for `default`, `name`,
`basedir` and several other attributes in the project tag, like it will do for
the properties. You can refer to the Project class of ant for more information.
was (Author: biwa7636):
[~lewismc], right now, the project name in the build.xml is trying to referring
to the variable ${name}. However, even if you change that to ${final.name},
which suppose to be ${name} - ${version}. It still won't work. The reason is
because Ant won't parse and get the reference for `default`, `name`, `basedir`
and several other attributes in the project tag, like it will do for the
properties. You can refer to the Project class of ant for more information.
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)
[jira] [Comment Edited] (NUTCH-1755) Project name bug in build.xml
[
https://issues.apache.org/jira/browse/NUTCH-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072736#comment-14072736
]
bin wang edited comment on NUTCH-1755 at 7/24/14 3:10 AM:
--
[~lewismc], right now, the project name in the build.xml is trying to referring
to the variable ${name}. However, even if you change that to ${final.name},
which suppose to be ${name} - ${version}. It still won't work. The reason is
because Ant won't parse and get the reference for `default`, `name`, `basedir`
and several other attributes in the project tag, like it will do for the
properties. You can refer to the Project class of ant for more information.
was (Author: biwa7636):
[~lewismc], right now, the project name in the build.xml is trying to referring
to the variable ${name}. However, even if you change that to ${final.name},
which suppose to be ${name}-${version}. It still won't work. The reason is
because Ant won't parse and get the reference for `default`, `name`, `basedir`
and several other attributes in the project tag, like it will do for the
properties. You can refer to the Project class of ant for more information.
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)
[jira] [Comment Edited] (NUTCH-1755) Project name bug in build.xml
[
https://issues.apache.org/jira/browse/NUTCH-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072736#comment-14072736
]
bin wang edited comment on NUTCH-1755 at 7/24/14 3:12 AM:
--
[~lewismc], right now, the project name in the build.xml is trying to referring
to the variable `name`. However, even if you change that to `final.name`, which
suppose to be `name`-`version`. It still won't work. The reason is because Ant
won't parse and get the reference for `default`, `name`, `basedir` and several
other attributes in the project tag, like it will do for the properties. You
can refer to the Project class of ant for more information.
was (Author: biwa7636):
[~lewismc], right now, the project name in the build.xml is trying to referring
to the variable ${name}. However, even if you change that to ${final.name},
which suppose to be ${name}-${version}. It still won't work. The reason is
because Ant won't parse and get the reference for `default`, `name`, `basedir`
and several other attributes in the project tag, like it will do for the
properties. You can refer to the Project class of ant for more information.
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)
[jira] [Comment Edited] (NUTCH-1755) Project name bug in build.xml
[
https://issues.apache.org/jira/browse/NUTCH-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072736#comment-14072736
]
bin wang edited comment on NUTCH-1755 at 7/24/14 3:11 AM:
--
[~lewismc], right now, the project name in the build.xml is trying to referring
to the variable ${name}. However, even if you change that to ${final.name},
which suppose to be ${name}-${version}. It still won't work. The reason is
because Ant won't parse and get the reference for `default`, `name`, `basedir`
and several other attributes in the project tag, like it will do for the
properties. You can refer to the Project class of ant for more information.
was (Author: biwa7636):
[~lewismc], right now, the project name in the build.xml is trying to referring
to the variable ${name}. However, even if you change that to ${final.name},
which suppose to be $ { name } - $ { version }. It still won't work. The reason
is because Ant won't parse and get the reference for `default`, `name`,
`basedir` and several other attributes in the project tag, like it will do for
the properties. You can refer to the Project class of ant for more information.
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)
[jira] [Comment Edited] (NUTCH-1755) Project name bug in build.xml
[
https://issues.apache.org/jira/browse/NUTCH-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072736#comment-14072736
]
bin wang edited comment on NUTCH-1755 at 7/24/14 3:16 AM:
--
[~lewismc], right now, the project name in the build.xml is trying to referring
to the variable `name`, which is defined in the default.properties. However,
even if one changes that to `final.name`, which suppose to be `name`-`version`.
It still won't work. The reason is because Ant won't parse and get the
reference for `default`, `name`, `basedir` and several other attributes in the
project tag, like it will do for the properties. You can refer to the Project
class of ant for more information. In another way, the project name attribute
won't accept reference and will save the plain text as the project name.
(Note: dollar sign and curly brackets will totally mess up the comment format,
so I put them in quote)
was (Author: biwa7636):
[~lewismc], right now, the project name in the build.xml is trying to referring
to the variable `name`, which is defined in the default.properties. However,
even if one changes that to `final.name`, which suppose to be `name`-`version`.
It still won't work. The reason is because Ant won't parse and get the
reference for `default`, `name`, `basedir` and several other attributes in the
project tag, like it will do for the properties. You can refer to the Project
class of ant for more information. In another way, the project name attribute
won't accept reference and will save the plain text as the project name.
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)
[jira] [Comment Edited] (NUTCH-1755) Project name bug in build.xml
[
https://issues.apache.org/jira/browse/NUTCH-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072736#comment-14072736
]
bin wang edited comment on NUTCH-1755 at 7/24/14 3:14 AM:
--
[~lewismc], right now, the project name in the build.xml is trying to referring
to the variable `name`, which is defined in the default.properties. However,
even if one changes that to `final.name`, which suppose to be `name`-`version`.
It still won't work. The reason is because Ant won't parse and get the
reference for `default`, `name`, `basedir` and several other attributes in the
project tag, like it will do for the properties. You can refer to the Project
class of ant for more information. In another way, the project name attribute
won't accept reference and will save the plain text as the project name.
was (Author: biwa7636):
[~lewismc], right now, the project name in the build.xml is trying to referring
to the variable `name`. However, even if you change that to `final.name`, which
suppose to be `name`-`version`. It still won't work. The reason is because Ant
won't parse and get the reference for `default`, `name`, `basedir` and several
other attributes in the project tag, like it will do for the properties. You
can refer to the Project class of ant for more information.
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)
[jira] [Commented] (NUTCH-1755) Project name bug in build.xml
[
https://issues.apache.org/jira/browse/NUTCH-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072764#comment-14072764
]
Lewis John McGibbney commented on NUTCH-1755:
-
Hey [~biwa7636] thanks for input here. I wonder if you are working with trunk
and can provide a patch?
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)
[jira] [Commented] (NUTCH-1755) Project name bug in build.xml
[
https://issues.apache.org/jira/browse/NUTCH-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072796#comment-14072796
]
bin wang commented on NUTCH-1755:
-
[~lewismc] Yes. I am looking at the trunk. Then should I go ahead and remove
the `name` reference in the project tag in build.xml and instead, hard code
that field to be `nutch`?
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)
[jira] [Commented] (NUTCH-1755) Project name bug in build.xml
[
https://issues.apache.org/jira/browse/NUTCH-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Updated] (NUTCH-1755) Project name bug in build.xml
[
https://issues.apache.org/jira/browse/NUTCH-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney updated NUTCH-1755:
Fix Version/s: 1.9
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, 1.9
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)
