I still cannot get it to work on that machine (MacBook Pro running Catalina).
It did work on my main machine (Mac Mini running Mojave), but now I’m getting
this failure:
get-utils-version:
[echo] utils version is 1.2.0-SNAPSHOT
write-out-maven-jars-list:
write-out-maven-utils-jars-list:
compare-jars:
[copy] Copying 1 file to /Apache/royale-compiler/temp_folder
loopOnce:
[copy] Copying 1 file to /Apache/royale-compiler/temp_folder
notlast:
get-jar-version:
compare_files:
[echo] comparing royale-maven-plugin-0.9.8
BUILD FAILED
/Apache/royale-compiler/releasesteps.xml:213: The following error occurred
while executing this line:
/Apache/royale-compiler/releasesteps.xml:241: The following error occurred
while executing this line:
/Apache/royale-compiler/releasesteps.xml:248: The following error occurred
while executing this line:
/Apache/royale-compiler/releasesteps.xml:283: royale-maven-plugin-0.9.8.jar
does not match
I don’t know why I’m not getting a reproducible build, but I wonder if it’s
because it’s using 1.2.0-SNAPSHOT instead of 1.2.1.
I don’t know why that would be. I’m on the release branch.
> On Nov 27, 2020, at 1:03 AM, Alex Harui <[email protected]> wrote:
>
> IIRC, on your local machine, if you clone the repo and run "mvn clean
> install", it should allow you to type a response and then that machine should
> be ok to use after that.
>
> -Alex
>
> On 11/26/20, 1:46 PM, "Harbs" <[email protected]> wrote:
>
> That’s on my local machine. Passing the Dcom option to the ant script
> doesn’t help.
>
> How would I manually get the Adobe artifacts on my machine?
>
>> On Nov 26, 2020, at 11:18 PM, Christofer Dutz <[email protected]>
>> wrote:
>>
>> I can tell you what’s going on here.
>>
>> You are building on a system where the Adobe artifacts aren’t available in
>> the maven local repo.
>> So the mavenizer (AKA maven extension I built to make non maven artifacts
>> available as Maven artifacts) is kicking in. It expects a user to accept the
>> license terms. It seems the MAC address of the network configuration of the
>> build machine changed. You need to pass
>>
>> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=b57aca16
>>
>> To the build job
>>
>> Chris
>>
>>
>> Von: Harbs <[email protected]>
>> Datum: Donnerstag, 26. November 2020 um 21:53
>> An: Apache Royale Development <[email protected]>
>> Betreff: Re: Release Step 003 Succeeded
>> I don’t get it. I’m getting an endless loop of:
>>
>> [exec] The Adobe SDK license agreement applies to the Adobe Flash Player
>> playerglobal.swc. Do you want to install the Adobe Flash Player
>> playerglobal.swc?
>> [exec] (In a non-interactive build such as a CI server build,
>> alternatively to typing y or yes you can also set a system property
>> containing your system which is interpreted as equivalent to accepting by
>> typing y or yes:
>> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=b57aca16
>> )
>> [exec] Do you accept (Yes/No) ? Your System-Id: b57aca16
>>
>> when I run:
>>> ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
>>
>> Where is that coming from and why?
>>
>>> On Nov 26, 2020, at 9:16 PM, [email protected] wrote:
>>>
>>> From the royale-compiler repo:
>>> 1. Run:
>>> ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
>>> This will download the artifacts then unzip and compile the source artifact.
>>> 2. Validate that the compiled artifacts match the downloaded artifacts.
>>> 3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign
>>> -Drelease.version=0.9.8
>>> This will PGP sign the source ZIP and compiled JARs
>>> 4. Then run ant -f releasesteps.xml Release_Step_003_Upload
>>> -Drelease.version=0.9.8
>>> This will upload the signed artifacts to Maven Release Staging. If you are
>>> getting 401 responses from Nexus (permission denied) please be sure to have
>>> your apache creedentials configured in your .m2/settings.xml file.
>>>
>>> Feel free to use this template if you haven't got a settings.xml yet:
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <settings
>>> xsi:schemaLocation="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmaven.apache.org%2FSETTINGS%2F1.1.0&data=04%7C01%7Caharui%40adobe.com%7Cc3e8334de4804345982a08d89254b15b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637420239736235404%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3ccTB4X%2BJ%2BDcgoXu4f5%2Bsn4gNvhzKW3XflhRviKqxxM%3D&reserved=0
>>>
>>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmaven.apache.org%2Fxsd%2Fsettings-1.1.0.xsd&data=04%7C01%7Caharui%40adobe.com%7Cc3e8334de4804345982a08d89254b15b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637420239736235404%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xlWxXIj0l7KQJhY%2BhYw1hf%2FwTZ%2Bteq5dnuTbkxTIS6I%3D&reserved=0";
>>>
>>> xmlns="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmaven.apache.org%2FSETTINGS%2F1.1.0&data=04%7C01%7Caharui%40adobe.com%7Cc3e8334de4804345982a08d89254b15b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637420239736235404%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3ccTB4X%2BJ%2BDcgoXu4f5%2Bsn4gNvhzKW3XflhRviKqxxM%3D&reserved=0";
>>>
>>> xmlns:xsi="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema-instance&data=04%7C01%7Caharui%40adobe.com%7Cc3e8334de4804345982a08d89254b15b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637420239736235404%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=b%2BVeRzz2WAJe8I7fMz3GVhdRPJ%2FIWBX4Jej5cRUU4wA%3D&reserved=0";>
>>> <servers>
>>> <!-- Apache Repo Settings -->
>>> <server>
>>> <id>apache.releases.https</id>
>>> <username>{your apache user id}</username>
>>> <password>{your apache user password}</password>
>>> </server>
>>> </servers>
>>> </settings>
>>>
>>> (Be sure to replace the placeholders with your actual apache committer id
>>> and your Apache password)
>>>
>>> If you already have a settings.xml, just be sure the "server" block
>>> containing your credentials is added to a servers block in that file.
>>>
>>> Do not "Close" the staging repository until the other repos have been added.
>
>
>
