Hi Carlos, as this is only one artifact, I would probably use something completely different, which wouldn’t make the use of the mavenizer required at all for getting the playerglobal.
We probably still need it for the AIR stuff, but I think that’s till available, isn t it? Chris Von: Carlos Rovira <[email protected]> Gesendet: Montag, 4. Januar 2021 09:33 An: Apache Royale Development <[email protected]>; Christofer Dutz <[email protected]> Betreff: Re: [Discuss] What to do with SWF target now that Adobe removed Flash Player in 2021 (Re: How to build from now on?) Ok, @Christofer Dutz<mailto:[email protected]> can you update and release mavenizer to use https://fpdownload.macromedia.com/get/flashplayer/updaters/32/playerglobal32_0.swc instead: https://fpdownload.macromedia.com/get/flashplayer/installers/archive/playerglobal/playerglobal20_0.swc I think that would solve the issue to build from a clean computer right? anyway i wonder if this url will be valid for long El dom, 3 ene 2021 a las 23:44, Harbs (<[email protected]<mailto:[email protected]>>) escribió: Why not just point to the current playerglobal? https://fpdownload.macromedia.com/get/flashplayer/updaters/32/playerglobal32_0.swc > On Jan 4, 2021, at 12:30 AM, Carlos Rovira > <[email protected]<mailto:[email protected]>> wrote: > > Hi, I think we are in real problems now. > If a new user comes and try to build he can't. Since he can download the > playerglobal.swc. > So for me that's a real problems today. > > El dom, 3 ene 2021 a las 20:07, Harbs > (<[email protected]<mailto:[email protected]>>) escribió: > >> Let’s wait and see whether we are dealing with real issues or not. If it’s >> an issue we can debate solutions. >> >> I’m happy to ask my Adobe contacts what the plan is. >> >>> On Jan 3, 2021, at 8:52 PM, Carlos Rovira >>> <[email protected]<mailto:[email protected]>> >> wrote: >>> >>> Hi Harbs, >>> >>> the problem here's that I think we are on Apache, and using a piece of >>> software that is under a clear license use will be against the foundation >>> rules. So although you or I can host the files, that's not seem to me >> like >>> a solution to the real problem. >>> >>> I'm for go step by step and first try to talk with Adobe representatives >> to >>> get the permission for Apache to host the player files only for our flex >>> and royale use cases. I think we could continue discussion after we know >>> the solution to this request >>> >>> Can you, Alex or others do this request? or if you want I can do it, but >>> need someone to provide me the contact at adobe. >>> >>> Thanks >>> >>> >>> >>> El dom, 3 ene 2021 a las 15:59, Harbs >>> (<[email protected]<mailto:[email protected]>>) >> escribió: >>> >>>> There’s no license agreement when downloading playerglobal or the >> content >>>> debugger. >>>> >>>> I’m willing to take the risk to personally host these files if >> necessary. >>>> >>>>> On Jan 3, 2021, at 4:47 PM, Christofer Dutz >>>>> <[email protected]<mailto:[email protected]> >>> >>>> wrote: >>>>> >>>>> And I doubt we would be allowed to simply upload Adobe stuff to any >>>> other server wirhout explicit conset from them. The license agreement >> you >>>> agreed to when downloading explicitly forbids that (at least it did, >> wenn >>>> we were working on the Flex Mavenizer and I doubt things changed) >>>> >>>> >>> >>> -- >>> Carlos Rovira >>> Apache Member & Apache Royale PMC >>> *Apache Software Foundation* >>> http://about.me/carlosrovira >> >> > > -- > Carlos Rovira > Apache Member & Apache Royale PMC > *Apache Software Foundation* > http://about.me/carlosrovira -- Carlos Rovira Apache Member & Apache Royale PMC Apache Software Foundation http://about.me/carlosrovira
