[ 
https://issues.apache.org/jira/browse/LUCENE-7696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Høydahl updated LUCENE-7696:
--------------------------------
    Attachment: LUCENE-7696.patch

Attaching a patch against https://dist.apache.org/repos/dist/release/lucene/ 
which removes the folders and {{.htaccess}} files for mahout, nutch and tika.

This will cause these folders to be gone from the mirrors, *but remain as-is in 
the archive*.

Agree?

> Remove ancient projects from the dist area
> ------------------------------------------
>
>                 Key: LUCENE-7696
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7696
>             Project: Lucene - Core
>          Issue Type: Task
>          Components: general/website
>            Reporter: Jan Høydahl
>              Labels: archive, dist, download
>         Attachments: LUCENE-7696.patch
>
>
> In http://www.apache.org/dist/lucene/ we have these folders:
> {noformat}
> [DIR] java/                   2017-02-14 08:33    -   
> [DIR] mahout/                 2015-02-17 20:27    -   
> [DIR] nutch/                  2015-02-17 20:29    -   
> [DIR] pylucene/               2017-02-13 22:00    -   
> [DIR] solr/                   2017-02-14 08:33    -   
> [DIR] tika/                   2015-02-17 20:29    -   
> [   ] KEYS                    2016-08-30 09:59  148K  
> {noformat}
> Nobody will expect to find mahout, nutch and tika here anymore, and they are 
> only redirect links, so why not clean up?
> Regarding the archive, we'll keep all historic releases as is but ask Nutch 
> if they want to either copy the oldest releases to their archive or provide a 
> link to the lucene/nutch archive for the oldest releases. Tika already have 
> such a link, and hadoop already has a complete set of artifacts in their main 
> repo.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to