quick ping before open a Jira issue to the INFRA team, does anyone have
any idea why Jira issue edits haven't been generated mail to java-dev
since sometimes after November 2nd ?
A quick glance at the "recently edited" issues and the email archives for
hadoop and nutch indicate that the prob
We are having similar problems with Nutch.
Dennis
Chris Hostetter wrote:
quick ping before open a Jira issue to the INFRA team, does anyone have
any idea why Jira issue edits haven't been generated mail to java-dev
since sometimes after November 2nd ?
A quick glance at the "recently edited
: We are having similar problems with Nutch.
A Solr issue edited this morning confirmed that Solr isn't affected.
Opened issue since i haven't seen anyone chime in and say "oh i know
what's going on"...
https://issues.apache.org/jira/browse/INFRA-1397
-Hoss
--
Cool, I didn't know that is how we submit something to infrastructure.
Thanks.
Dennis
Chris Hostetter wrote:
: We are having similar problems with Nutch.
A Solr issue edited this morning confirmed that Solr isn't affected.
Opened issue since i haven't seen anyone chime in and say "oh i know
[
https://issues.apache.org/jira/browse/LUCENE-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1046:
-
Component/s: (was: contrib/benchmark)
contrib/*
> Dead code in SpellChecker.java (b
: > https://issues.apache.org/jira/browse/INFRA-1397
FYI: issue was caused by a change to Jira's outgoing email properties, and
some filtering options on *some* apache lists (hence it wasn't affecting
all subprojects)
Jira emails should be going through now.
-Hoss
-
A few times now i've seen people open issues in the "contrib/benchmark"
component thinking it ment "contrib or benchmark" and not the specitic
path -- so i added a new component for issues related to "contribs".
if we start to see lots of issues for individual contribs, we can add
their own
