URL maintenance problem: googlecode closing, codehaus closed

13 views
Skip to first unread message

Martin Weber

unread,
Mar 24, 2015, 1:46:03 PM3/24/15
to ivyro...@googlegroups.com
Hi mainteners,

with googlecode closing and codehaus already closed, I see a lot of work in
maintaining homepage and download URLs coming up.

Here are some stats from ivyroundup.

Googlecode:

- Currently we have 165 homepage URLs pointing to googlecode. Unfortunately,
for projects that have moved, googlecode does not return a 'permanently moved'
HTTP response. So these URLs will have to be updated manually. I expect most
of the projects to move to github, which makes them easier to find again.

- Zero download URLs point to googlecode, fortunately. So nothing to do here.

Codehaus:

- 65 homepage URLs point to codehaus.org. Although codehaus states they will
supply Route53 hosting and an http(s) redirector for the codehaus.org domains
for at least the next 12 months to keep redirects operating, I get more and
more 'Can't get http://<project>.codehaus.org/'

- 34 download URLs point to codehaus.org. Some of them are already blocked
(see issue 509) and I expect all of them become unavailable. A solution would
be to change the packager.xmlS to use maven central for download.

I would suggest to drop at least some of the affected packages from
ivyroundup. But how do we ensure ivyroundup`s self-consistency then?

Martin

--
Cd wrttn wtht vwls s mch trsr.


Archie Cobbs

unread,
Mar 24, 2015, 3:51:29 PM3/24/15
to Ivy RoundUp Mailing List
On Tue, Mar 24, 2015 at 12:45 PM, Martin Weber <fifteen...@gmail.com> wrote:
with googlecode closing and codehaus already closed, I see a lot of work in
maintaining homepage and download URLs coming up.

Here are some stats from ivyroundup.

Thanks for collecting this info.
 
Googlecode:

- Currently we have 165 homepage URLs pointing to googlecode. Unfortunately,
for projects that have moved, googlecode does not return a 'permanently moved'
HTTP response. So these URLs will have to be updated manually. I expect most
of the projects to move to github, which makes them easier to find again.

- Zero download URLs point to googlecode, fortunately. So nothing to do here.

Codehaus:

- 65 homepage URLs point to codehaus.org. Although codehaus states they will
supply Route53 hosting and an http(s) redirector for the codehaus.org domains
for at least the next 12 months to keep redirects operating, I get more and
more 'Can't get http://<project>.codehaus.org/'

- 34 download URLs point to codehaus.org. Some of them are already blocked
(see issue 509) and I expect all of them become unavailable. A solution would
be to change the packager.xmlS to use maven central for download.

I would suggest to drop at least some of the affected packages from
ivyroundup. But how do we ensure ivyroundup`s self-consistency then?

We will just have to fix these over time. The fail-safe for any module that is broken is that if some user out there cares, and discovers one day that s(he) can't download it anymore, then they will figure out how to update it and let us know :)

-AC

--
Archie L. Cobbs

Archie Cobbs

unread,
Apr 20, 2015, 1:16:26 PM4/20/15
to Ivy RoundUp Mailing List
I'm starting to do the import.

If you are one of these people and have a github account please let me know your github username so I can link your commits.

neil.g.miller.98
fifteenknots505
jing.xue
ales.nosek

Thanks,
-Archie

On Tue, Mar 24, 2015 at 12:45 PM, Martin Weber <fifteen...@gmail.com> wrote:
with googlecode closing and codehaus already closed, I see a lot of work in
maintaining homepage and download URLs coming up.

--
Archie L. Cobbs
Reply all
Reply to author
Forward
0 new messages