I deployed flex-sdk-converter-extension 1.1.0-SNAPSHOT to Apache snapshots
to allow testing of my bugfix. I updated the royale-compiler develop branch
to use it, along with playerglobal 32.0 instead of 20.0 because Adobe no
longer makes 20.0 available for download.

Similar to how it worked in the past, before flex-sdk-converter-extension
1.0 was released, you are now required to tell Maven to use
settings-template.xml (but I think only the first time) to find this
snapshot when building royale-compiler.

mvn clean install -P option-with-swf -s settings-template.xml

Using settings-template.xml is temporary. I plan to start the full release
process for 1.1.0 as soon as others verify that it's working for them too.
So please pull from the develop branch of royale-compiler and try to build
using the command above. Thanks!

I'll hold off on updating royale-asjs to use 1.1.0-SNAPSHOT and
playerglobal 32.0 until Yishay creates the release branch in that repo, so
that the release branches remain in sync.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Tue, Jan 31, 2023 at 12:24 PM Josh Tynjala <joshtynj...@bowlerhat.dev>
wrote:

> I think I want to try publishing flex-sdk-converter-extension
> 1.1.0-SNAPSHOT to Apache's Maven snapshots repo. Then, we can use the "-s
> settings-template.xml" trick to get our build to use that snapshot version.
> This is how we did it with 1.0.0-SNAPSHOT before Chris released the proper
> 1.0.0. That'll at least get us unstuck. Later, I'll try to do a proper
> release of 1.1.0.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Tue, Jan 31, 2023 at 10:23 AM Josh Tynjala <joshtynj...@bowlerhat.dev>
> wrote:
>
>> Okay, I rebuilt flex-sdk-converter-extension on my local machine (it's in
>> the flex-utilities repo, for anyone interested). If I change the URL for
>> sdk-installer-config-4.0.xml from http to https, it successfully downloads.
>>
>> So, for some reason, the 301 redirect is not being handled correctly.
>> Presumably, something changed on the server. Perhaps it was still serving
>> http in the past, and it was forced to https more recently.
>>
>> I found this explanation about redirects in Java:
>>
>> > After discussion among Java Networking engineers, it is felt that we
>> shouldn't automatically follow redirect from one protocol to another, for
>> instance, from http to https and vise versa, doing so may have serious
>> security consequences. Thus the fix is to return the server responses for
>> redirect. Check response code and Location header field value for redirect
>> information. It's the application's responsibility to follow the redirect.
>>
>> Looks like flex-sdk-converter-extension needs to update this URL and get
>> a new release, since the redirect from http to https won't work.
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC <https://bowlerhat.dev>
>>
>>
>> On Tue, Jan 31, 2023 at 9:24 AM Josh Tynjala <joshtynj...@bowlerhat.dev>
>> wrote:
>>
>>> I tried changing to playerglobal 32.0, and it is still failing.
>>> Interestingly, I see these lower level exceptions in the log when I add the
>>> -X option to mvn:
>>>
>>> Caused by:
>>> org.apache.flex.utilities.converter.retrievers.exceptions.RetrieverException:
>>> Error parsing 'sdk-installer-config-4.0.xml'
>>> Caused by: org.xml.sax.SAXParseException: Premature end of file.
>>>
>>> So it's trying to download
>>> http://flex.apache.org/installer/sdk-installer-config-4.0.xml (where it
>>> will find the URL to playerglobal.swc), and something is going wrong
>>> parsing that file.
>>>
>>> It seems to be valid XML, so maybe it's getting some kind of error
>>> document from the web server instead of the proper file.
>>>
>>> I'll keep digging...
>>>
>>> --
>>> Josh Tynjala
>>> Bowler Hat LLC <https://bowlerhat.dev>
>>>
>>>
>>> On Tue, Jan 31, 2023 at 8:47 AM Josh Tynjala <joshtynj...@bowlerhat.dev>
>>> wrote:
>>>
>>>> I seem to recall that Adobe stopped making most older versions of
>>>> playerglobal.swc available for download from their servers. I think it
>>>> might be only version 32.0 that's still available.
>>>>
>>>> We have flash.version set to 20.0 in our pom.xml:
>>>>
>>>> <flash.version>20.0</flash.version>
>>>>
>>>> We might need to change that to 32.0.
>>>>
>>>> Most of us wouldn't notice that the download wasn't available because
>>>> we installed playerglobal months/years ago, before Adobe removed their
>>>> downloads, and the Maven extension probably doesn't try to download it
>>>> again, if it's already available locally.
>>>>
>>>> I'm going to try to see if I can mess with my local Maven cache to
>>>> trigger this error on my computer.
>>>>
>>>> --
>>>> Josh Tynjala
>>>> Bowler Hat LLC <https://bowlerhat.dev>
>>>>
>>>>
>>>> On Tue, Jan 31, 2023 at 8:35 AM Josh Tynjala <joshtynj...@bowlerhat.dev>
>>>> wrote:
>>>>
>>>>> We use some kind of Maven plugin/extension that downloads
>>>>> playerglobal.swc from Adobe.
>>>>>
>>>>> I think it's the flex-sdk-converter-maven-extension referenced in
>>>>> .mvn/extensions.xml
>>>>>
>>>>> --
>>>>> Josh Tynjala
>>>>> Bowler Hat LLC <https://bowlerhat.dev>
>>>>>
>>>>>
>>>>> On Tue, Jan 31, 2023 at 7:43 AM Yishay Weiss <yishayj...@hotmail.com>
>>>>> wrote:
>>>>>
>>>>>> Compiler release is failing [1] due to playerglobal not being found
>>>>>> in maven repo. I checked and I can’t find com.adobe.flash there [2] any
>>>>>> ideas?
>>>>>>
>>>>>> [1] Royale_Release_Step_002 #9 Console [Jenkins] (azure.com)<
>>>>>> http://apacheroyale.francecentral.cloudapp.azure.com:8080/job/Royale_Release_Step_002/lastBuild/console
>>>>>> >
>>>>>> [2] Central Repository: com/adobe (apache.org)<
>>>>>> https://repo.maven.apache.org/maven2/com/adobe/>
>>>>>>
>>>>>

Reply via email to