Apache projects aren't supposed to make forks without permission. Getting permission is a whole process. For me, it was easier to put a copy in the Adobe Flex SourceForge repo and get it from there. That way Adobe is still the distributor.
-Alex On 12/20/16, 1:12 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >As we have been having problems like this quite regularly ... what would >prevent us from forking osmf and adding that to our flex extras git repo >and publishing osmf to maven-central. >Shouldn’t that resolve this type of problem once and for all? > >Chris > >Am 19.12.16, 23:27 schrieb "Justin Mclean" <jus...@classsoftware.com>: > > Hi, > > The same download is also failing on OSX currently so it not just a >windows issue. > > However it's not failing consistently on my 3rd try it worked. > > Using curl -v I notice it's doing a 302 redirect to: > >https://pilotfiber.dl.sourceforge.net/project/osmf.adobe/OSMF%202.0%20Rele >ase%20%28final%20source%2C%20ASDocs%2C%20pdf%20guides%20and%20release%20no >tes%29/OSMF.swc > > Perhaps using that URL would give more consistent results? > > Justin >
