The "snapshot" in the script output should just be checking if the release is
for jburg-types as well as the main jars (which it isn't).
The main pom.xml should not be using -SNAPSHOT for jburg-types and build-tools.
It seems ok to me.
Verify the Java version on the system that has a difference. It needs to be
the same as the CI server. Then diff the two jars and see what is different.
Try unzipping each jar in a separate directory and compare the directories.
HTH,
-Alex
On 11/29/20, 4:05 AM, "Harbs" <harbs.li...@gmail.com> wrote:
Yes. But that was compiler-build-tools. This is compiler-jburg-types.
> On Nov 29, 2020, at 2:02 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
wrote:
>
> In a Apache Maven central - when you staged artifacts (I don't remember
> url), after vote on release you need to click there to make that release
> happen. Did you do something like this ?
>
> niedz., 29 lis 2020 o 12:44 Harbs <harbs.li...@gmail.com> napisał(a):
>
>> I see that compiler-jburg-types is still 1.2.0-SNAPSHOT.
>>
>> Did I need to do a release on that in addition to compiler-build-tools?
>>
>> I really don’t understand all these Maven side-projects...
>>
>>> On Nov 29, 2020, at 1:38 PM, Harbs <harbs.li...@gmail.com> wrote:
>>>
>>> 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 <aha...@adobe.com.INVALID>
>> 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" <harbs.li...@gmail.com> 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 <
>> christofer.d...@c-ware.de> 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 <harbs.li...@gmail.com>
>>>>> Datum: Donnerstag, 26. November 2020 um 21:53
>>>>> An: Apache Royale Development <dev@royale.apache.org>
>>>>> 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, apacheroyal...@gmail.com 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%7C3b62358176f84f2d5bb708d8945f0147%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637422483049313883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=cYM0ec%2Fmp6p85HuPUCTvdEDWdbhXYksLI3jtUdb4Vx4%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%7C3b62358176f84f2d5bb708d8945f0147%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637422483049313883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gkQYahOi7iiCAfPdgH8ly4yvCIoHVmVOTwEELdB5Ix8%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%7C3b62358176f84f2d5bb708d8945f0147%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637422483049313883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=cYM0ec%2Fmp6p85HuPUCTvdEDWdbhXYksLI3jtUdb4Vx4%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%7C3b62358176f84f2d5bb708d8945f0147%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637422483049313883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=F6KyoaJ4POyzTwVyNF8eSRBB0t%2BFplQwAXoblnygmSE%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.
>>>>
>>>>
>>>>
>>>
>>
>>
>
> --
>
> Piotr Zarzycki
