I’m having a very hard time getting getting the jars to match perfectly. When building on Windows I get consistent line breaks, so that’s a work-around, but I’m having the following issues when comparing jars:
1. On one Windows machine, I believe file dates matched, but on a second machine they didn’t. 2. On my build I’m getting dependencies on - playerglobal com.adobe.flash.framework:playerglobal:swc:20. I noticed this in both flex-compiler-oem and compiler-jx. I don’t know what flex-compiler-oem does. In the case of compiler-jx, that dependency does not seem correct. So the CI build seems to be right, but my local build seems wrong. Maven is black magic to me, and I have no idea how to go about making this work. > On Dec 4, 2020, at 12:31 PM, Christofer Dutz <christofer.d...@c-ware.de> > wrote: > > Hi Harbs, > > Well I would assume that on the CI it was not built with “with-swf” option. > Theoretically the archives generated should be identical in the compiler > module with or without swf, it’s just that “with-swf” turns on all Flash > released tests and therefore needs a dependency to the playerglobal. > > Chris > > > > Von: Harbs <harbs.li...@gmail.com> > Datum: Freitag, 4. Dezember 2020 um 11:18 > An: dev@royale.apache.org <dev@royale.apache.org> > Betreff: Re: Release Step 003 Succeeded > OK. Progress. > > I got reproducible build of two jars, but I’m getting a failure on > flex-compiler-oem. > > My build has this in the DEPENDENCIES file which is missing in the CI build: > > - playerglobal com.adobe.flash.framework:playerglobal:swc:20.0 > > Any clues as to 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.
