Royale_Compiler_Build_Tools_Release_Step_002 - Build # 2 - Still Failing!

[ap...@gmail.com]

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 2 - Still Failing:

Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/2/ to view the results.

Royale Compiler Build Tools Release Step 002 Succeeded

[ap...@gmail.com]

From the royale-compiler repo:
1. Run:
  ant -f releasesteps.xml Royale_Compiler_Build_Tools_Release_Step_002 -Drelease.version=1.2.0 -DskipTests=true
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 Royale_Compiler_Build_Tools_Release_Step_002_Sign -Drelease.version=1.2.0
This will PGP sign the source ZIP and compiled JARs
4. Then run:
ant -f releasesteps.xml Royale_Compiler_Build_Tools_Release_Step_002_Upload -Drelease.version=1.2.0
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 credentials 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.

Go to: https://repository.apache.org/ and verify that the artifacts are in the staging repo, then hit the close button to close the staging repo.

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 5 - Still Failing!

[ap...@gmail.com]

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 5 - Still Failing:

Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/5/ to view the results.

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 4 - Still Failing!

[ap...@gmail.com]

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 4 - Still Failing:

Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/4/ to view the results.

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 3 - Still Failing!

[ap...@gmail.com]

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 3 - Still Failing:

Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/3/ to view the results.