Re: ERROR: unexpected value 'go' for plc4x in http://plc4x.apache.org/plc4x-doap.rdf
Sorry about that. The intention was eventually to copy the emails to the projects, as is done for DOAP syntax errors. But perhaps there is a better way of doing it for these errors which are likely to be more frequent. Any objections to setting up a notifications list for such messages? On Sat, 9 Sept 2023 at 04:00, Dave Fisher wrote: > > Changes were made to project doap processing and now I get spammed with > errors once a day. > > Please fix this asap or I’ll have to unsubscribe to site-...@apache.org! Why > is a Comdev process sending errors there? > > Best, > Dave > > Sent from my iPhone > > Begin forwarded message: > > > From: Projects > > Date: September 8, 2023 at 7:10:37 PM PDT > > To: Site Development > > Subject: ERROR: unexpected value 'go' for plc4x in > > http://plc4x.apache.org/plc4x-doap.rdf > > Reply-To: site-...@apache.org > > > > ERROR: unexpected value 'go' for plc4x in > > http://plc4x.apache.org/plc4x-doap.rdf - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-436) parsereleases produces false releases for solr
[ https://issues.apache.org/jira/browse/COMDEV-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763352#comment-17763352 ] Sebb commented on COMDEV-436: - A release must contain a source package. There are only a few extensions that are used for these, so I think the search could be considerably simplified. > parsereleases produces false releases for solr > -- > > Key: COMDEV-436 > URL: https://issues.apache.org/jira/browse/COMDEV-436 > Project: Community Development > Issue Type: Improvement >Reporter: Jan Høydahl >Priority: Major > Attachments: COMDEV-436.patch, releases.json > > > When viewing [https://projects.apache.org/releases.html] and searching for > "solr", there are too many "falase positives". > See the "solr" section of > [https://projects.apache.org/json/foundation/releases.json] > {code:java} > "solr": { > "all.yaml": "2021-11-11", > "index.yaml": "2021-11-11", > "solr-0.5.0": "2021-11-11", > "solr-0.5.0.tgz.prov": "2021-11-11", > "solr-operator-0.5.0": "2021-11-11", > "solr-operator-0.5.0.tgz.prov": "2021-11-11", > "solr-operator-v0.5.0": "2021-11-11", > "solrbackups.yaml": "2021-11-11", > "solrclouds.yaml": "2021-11-11", > "solrprometheusexporters.yaml": "2021-11-11", > "zookeeperclusters.yaml": "2021-11-11" > }, > {code} > The script mistakes some files as releases, which are really not. > Currently the Solr downloads repo [https://downloads.apache.org/solr/] > contains only one release for the "solr-opereator" project, which is not a > traditional java code release, but rather k8s Helm-charts and CRDs. The Solr > main releases are currently in "lucene" so we don't expect them to show up > here until the 9.0 release. > So the expected output for the current contents is simply: > {code:java} > "solr": { > "solr-operator-0.5.0": "2021-11-11", > }, > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-436) parsereleases produces false releases for solr
[ https://issues.apache.org/jira/browse/COMDEV-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763353#comment-17763353 ] Sebb commented on COMDEV-436: - In the meantime I have applied the patch. > parsereleases produces false releases for solr > -- > > Key: COMDEV-436 > URL: https://issues.apache.org/jira/browse/COMDEV-436 > Project: Community Development > Issue Type: Improvement >Reporter: Jan Høydahl >Priority: Major > Attachments: COMDEV-436.patch, releases.json > > > When viewing [https://projects.apache.org/releases.html] and searching for > "solr", there are too many "falase positives". > See the "solr" section of > [https://projects.apache.org/json/foundation/releases.json] > {code:java} > "solr": { > "all.yaml": "2021-11-11", > "index.yaml": "2021-11-11", > "solr-0.5.0": "2021-11-11", > "solr-0.5.0.tgz.prov": "2021-11-11", > "solr-operator-0.5.0": "2021-11-11", > "solr-operator-0.5.0.tgz.prov": "2021-11-11", > "solr-operator-v0.5.0": "2021-11-11", > "solrbackups.yaml": "2021-11-11", > "solrclouds.yaml": "2021-11-11", > "solrprometheusexporters.yaml": "2021-11-11", > "zookeeperclusters.yaml": "2021-11-11" > }, > {code} > The script mistakes some files as releases, which are really not. > Currently the Solr downloads repo [https://downloads.apache.org/solr/] > contains only one release for the "solr-opereator" project, which is not a > traditional java code release, but rather k8s Helm-charts and CRDs. The Solr > main releases are currently in "lucene" so we don't expect them to show up > here until the 9.0 release. > So the expected output for the current contents is simply: > {code:java} > "solr": { > "solr-operator-0.5.0": "2021-11-11", > }, > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org