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="http://maven.apache.org/SETTINGS/1.1.0
> http://maven.apache.org/xsd/settings-1.1.0.xsd";
> xmlns="http://maven.apache.org/SETTINGS/1.1.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> <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.
