royale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com.INVALID>
Subject Re: [Discuss] Start release process 0.9.3
Date Thu, 11 Oct 2018 16:43:33 GMT
After digging through the output you pasted, it appears that the "check-empty-folder" target isn't quite right and didn't catch that you didn't run "maven" against an empty folder.  Although I am a bit puzzled why there were modified files in the working copy.

Maven and the scripts have some expectation that you are starting from the beginning, so if Maven got far enough to create a tag and you have to start over, you have to remove the tag.  These scripts are still under development so you should not expect that every situation has been accounted for.

So, go delete the tag.  Instructions for doing so are in the wiki.  Maybe figure out why those files were modified, but maybe because your earlier run didn't have the right gpg password.

Try changing the check-empty-folder to also test for:

        <available file="${basedir}/royale-asjs/build.properties"
            type="file"
            property="found.build.properties" value="true" />

Then it should catch you on the steps where you are supposed to start by pulling down the repos again.

If you don't have time for any of that, let us know here so the next RM can know where to start.

-Alex

On 10/11/18, 2:05 AM, "Piotr Zarzycki" <piotrzarzycki21@gmail.com> wrote:

    I gave up again :) It costs me to much time. I thought since Om did so much
    progress I will launch the script and will work. It's still failing.
    
    https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FWJ44&amp;data=02%7C01%7Caharui%40adobe.com%7C7b4f4f106a0e4832f0bc08d62f58b09f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636748455300137124&amp;sdata=VPvmFmVVt4GPIN49a2PqnG5D%2BvyQRELMH9rmntm1%2BcE%3D&amp;reserved=0
    
    I run first time and had problem with gpg password - just forgot it, but
    run it again and type correct password. Probably first time this tag was
    created and now script failing cause tag exits. Never ending story.
    
    I'm in that step - If someone would like to try it out let me know and I
    won't revert anything for now:
    
    ant -f releasecandidate.xml -Drelease.version="0.9.4" -Dbrowser="c:\Program
    Files\Mozilla Firefox\firefox.exe" -Drc=1 maven
    
    Thanks,
    Piotr
    
    
    czw., 11 paź 2018 o 10:13 Piotr Zarzycki <piotrzarzycki21@gmail.com>
    napisał(a):
    
    > Hi Alex,
    >
    > This is what I'm getting for git status for royale-compiler [1]
    >
    > [1] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FYuiH&amp;data=02%7C01%7Caharui%40adobe.com%7C7b4f4f106a0e4832f0bc08d62f58b09f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636748455300137124&amp;sdata=gXJ6R%2Fdf0DFd8vp16PjOONvUoqJpm5q7ajbdG5DsQMY%3D&amp;reserved=0
    >
    > Thanks,
    > Piotr
    >
    > śr., 10 paź 2018 o 17:50 Alex Harui <aharui@adobe.com.invalid> napisał(a):
    >
    >> What does 'git status' return for that local copy of the royale-compiler
    >> repo?
    >>
    >> That part of the script is trying to see if compiler-jburg-types and
    >> compiler-build-tools needed a version update that needs to be pushed.
    >> Those two projects should be at 1.0.0 since we rarely, if ever, will need
    >> to modify it.  There shouldn't have been modifications in this release, yet
    >> Git status is reporting modifications to some file.  A test is done to
    >> check for the word "modified:" in the 'git status' output, then that
    >> attempt to push is executed.  Somehow, the git status is implying
    >> modifications but the files we are trying to push are not modified.
    >>
    >> The solutions should not require reverting of the release branch.  It
    >> looks like you have successfully created a correct set of branches and the
    >> steps you are running start by pulling down the release branch.  I didn't
    >> see any commits to the release branch from the scripts, so to re-start, it
    >> should just be manually deleting the local copies of the repos and running
    >> the Ant command again after making one of the changes to
    >> releasecandidate.xml I will describe below:
    >>
    >> IMO, the choices are (and there may be more choices)
    >> 1.  Figure out how to be smarter about what 'git status' output will say
    >> so the test works correctly
    >> 2. Set failonerror="false" on the push step and not care if that push
    >> succeeds.  This is slightly risky if we ever do want to push changes, but
    >> again, that is low probability, IMO.
    >> 3. Comment out those steps since it will be rare we will need them.  If
    >> we do need them some day, the RM will have to remember to uncomment those
    >> steps.
    >>
    >> HTH,
    >> -Alex
    >>
    >> On 10/10/18, 2:52 AM, "Piotr Zarzycki" <piotrzarzycki21@gmail.com>
    >> wrote:
    >>
    >>     Ok It's failed :) However I passed step 3 in instruction. Step 4 is
    >> failing
    >>     [1] - if someone know what could it be - I will wait with reverting
    >> changes.
    >>
    >>     Lines in stacktrace are pointing in ant script to following targets:
    >>
    >>     Line 556: git-commit-and-push-utils
    >>     Line 487: git-commit-and-push-utils-if-modified
    >>     Line 473:
    >>
    >>     <exec executable="${git}" dir="${compiler}" failonerror="true" >
    >>                 <arg value="commit" />
    >>                 <arg value="-m" />
    >>                 <arg value="remove SNAPSHOT from compiler-jburg-types and
    >>     compiler-build-tools versions" />
    >>             </exec>
    >>
    >>     [1]
    >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fbg5e&amp;data=02%7C01%7Caharui%40adobe.com%7C7b4f4f106a0e4832f0bc08d62f58b09f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636748455300137124&amp;sdata=EgkW%2BtCG8WM229zkua3ObIqpQR0PJ29LjvKdsFijY9E%3D&amp;reserved=0
    >>
    >>     Thanks,
    >>     Piotr
    >>
    >>
    >>     śr., 10 paź 2018 o 11:34 Carlos Rovira <carlosrovira@apache.org>
    >> napisał(a):
    >>
    >>     > Ok Piotr, good luck! :)
    >>     >
    >>     > El mié., 10 oct. 2018 a las 10:34, Piotr Zarzycki (<
    >>     > piotrzarzycki21@gmail.com>) escribió:
    >>     >
    >>     > > Hi Guys,
    >>     > >
    >>     > > I will try right now process from my PC. We will see how far I
    >> will go
    >>     > with
    >>     > > that.
    >>     > >
    >>     > > Piotr
    >>     > >
    >>     > > czw., 4 paź 2018 o 22:01 Alex Harui <aharui@adobe.com.invalid>
    >>     > napisał(a):
    >>     > >
    >>     > > > Hi Om,
    >>     > > >
    >>     > > > If make_branches succeeds, then you shouldn't need to go back
    >> and
    >>     > delete
    >>     > > > branches and tags and run make_branches again if the "maven"
    >> step
    >>     > fails.
    >>     > > >
    >>     > > > You might need to revert any changes to the release branch that
    >> the
    >>     > > > "maven" step did, but then you should be able to delete the
    >> local copy
    >>     > of
    >>     > > > the branches and start again with "maven" or
    >>     > > > "maven_skip_compiler_and_typedefs" if you got all the way up to
    >>     > > royale-asjs.
    >>     > > >
    >>     > > > What are some of the 200+ files that don't get reverted back to
    >> 0.9.4?
    >>     > > >
    >>     > > > You are welcome to try to add the "continue" option.  I would
    >> suggest
    >>     > > > adding a dummy parameter.  So if the script currently calls
    >> Maven like
    >>     > > this:
    >>     > > >
    >>     > > >         <exec executable="${mvn}"
    >> dir="${basedir}/maven-release-plugin"
    >>     > > > failonerror="true" >
    >>     > > >             <arg value="clean" />
    >>     > > >             <arg value="install" />
    >>     > > >         </exec>
    >>     > > >
    >>     > > > You can try changing it to something like this:
    >>     > > >
    >>     > > >         <property name="continueOption" value="-Ddummy=0" />
    >>     > > >         <exec executable="${mvn}"
    >> dir="${basedir}/maven-release-plugin"
    >>     > > > failonerror="true" >
    >>     > > >             <arg value="${continueOption}" />
    >>     > > >             <arg value="clean" />
    >>     > > >             <arg value="install" />
    >>     > > >         </exec>
    >>     > > >
    >>     > > > Then you should be able to set in your local.properties:
    >>     > > >
    >>     > > > continueOption=-rf JewelExample
    >>     > > >
    >>     > > > You will probably need to use different names for each call to
    >> Maven so
    >>     > > > subsequent Maven calls don't pick up the same option.
    >>     > > >
    >>     > > > HTH,
    >>     > > > -Alex
    >>     > > >
    >>     > > > On 10/4/18, 11:58 AM, "OmPrakash Muppirala" <
    >> bigosmallm@gmail.com>
    >>     > > wrote:
    >>     > > >
    >>     > > >     On Thu, Oct 4, 2018 at 1:48 AM Alex Harui
    >> <aharui@adobe.com.invalid
    >>     > >
    >>     > > > wrote:
    >>     > > >
    >>     > > >     > Om, it looks like you are still deleting and recreating
    >> the
    >>     > > branches.
    >>     > > >     > Does this mean you have never completed the make_branches
    >> step?
    >>     > > >
    >>     > > >
    >>     > > >     Yes, I delete the tags, branches (remote) each time
    >> something
    >>     > fails.
    >>     > > > Then
    >>     > > >     I do a global search for 0.9.5 and replace it with 0.9.4
    >> (some 200+
    >>     > > > files
    >>     > > >     across 3 repos), then push them into remote/develop.
    >>     > > >
    >>     > > >     Then I do the make_branches step first.  Then do a git push
    >> in
    >>     > > > roayale-asjs
    >>     > > >     as per the instructions in the commandline. I have never
    >> had issues
    >>     > > > with
    >>     > > >     this step.  It is always the maven step that fails for some
    >> reason
    >>     > or
    >>     > > > the
    >>     > > >     other.
    >>     > > >
    >>     > > >
    >>     > > >     > Is make_branches failing trying to run a build in the
    >> develop
    >>     > > branch
    >>     > > > and
    >>     > > >     > uploading 0.9.5-SNAPSHOT artifacts?
    >>     > > >
    >>     > > >
    >>     > > >     No
    >>     > > >
    >>     > > >
    >>     > > >     > I supposed we could try to find a way to skip that, but
    >> you will
    >>     > > need
    >>     > > >     > reliable uploading to repository.a.o to be an RM without
    >> going
    >>     > > crazy.
    >>     > > >     >
    >>     > > >
    >>     > > >     Hmm, I use the same internet connection for personal and
    >> work
    >>     > related
    >>     > > >     activities.  I don't usually have issues with internet.
    >> Either we
    >>     > > are
    >>     > > > very
    >>     > > >     unlucky here or we need a more reselient way to pick up
    >> things if
    >>     > we
    >>     > > > lose
    >>     > > >     internet connectivity momentarily.
    >>     > > >
    >>     > > >     It takes upwards of 90 minutes of uploading stuff. I dont
    >> do this
    >>     > > kind
    >>     > > > of
    >>     > > >     uploading for my regular work, so that is probably I have
    >> never hit
    >>     > > > this
    >>     > > >     issue before.
    >>     > > >
    >>     > > >     I still think that looking into the 'resume-from' directive
    >> in
    >>     > maven
    >>     > > is
    >>     > > >     worthwhile.
    >>     > > >
    >>     > > >     Thanks,
    >>     > > >     Om
    >>     > > >
    >>     > > >
    >>     > > >     >
    >>     > > >     > -Alex
    >>     > > >     >
    >>     > > >     > On 10/3/18, 2:11 PM, "OmPrakash Muppirala" <
    >> bigosmallm@gmail.com
    >>     > >
    >>     > > > wrote:
    >>     > > >     >
    >>     > > >     >     On Wed, Oct 3, 2018 at 2:02 PM Alex Harui
    >>     > > > <aharui@adobe.com.invalid>
    >>     > > >     > wrote:
    >>     > > >     >
    >>     > > >     >     > Hi Om,
    >>     > > >     >     >
    >>     > > >     >     > Does anything deploy, or is that the first thing
    >> that is
    >>     > > > attempted to
    >>     > > >     >     > deploy?  I found this article that might help:
    >>     > > >     >     >
    >>     > > >     >     >
    >>     > > >     >
    >>     > > >
    >>     > >
    >>     >
    >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.apigee.com%2Fquestions%2F50756%2Funable-to-deploy-using-maven-script-due-to-error-r.html&amp;data=02%7C01%7Caharui%40adobe.com%7C7b4f4f106a0e4832f0bc08d62f58b09f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636748455300137124&amp;sdata=awLuDDC0qBKtdbrjKvbMgZD6rQ0mC7k%2BrdRK%2Fvkv1to%3D&amp;reserved=0
    >>     > > >     >
    >>     > > >     >
    >>     > > >     >     It deployed a lot of artifacts before hitting this
    >> error.  I
    >>     > > > don't see
    >>     > > >     >     anything special with this artifact.  So, I am
    >> guessing that
    >>     > it
    >>     > > > was a
    >>     > > >     >     momentary bad connection that caused this.
    >>     > > >     >
    >>     > > >     >
    >>     > > >     >     >
    >>     > > >     >     >
    >>     > > >     >     > I would be concerned about restarting from the
    >> middle of a
    >>     > > > Maven
    >>     > > >     > call.  I
    >>     > > >     >     > suppose you could try it, but what if it skipped an
    >>     > artifact?
    >>     > > >     >     >
    >>     > > >     >
    >>     > > >     >     The maven error message explicitly says this:
    >>     > > >     >
    >>     > > >     >          [exec] [INFO] [ERROR] After correcting the
    >> problems, you
    >>     > > can
    >>     > > >     > resume
    >>     > > >     >     the build with the command
    >>     > > >     >
    >>     > > >     >          [exec] [INFO] [ERROR]   mvn <goals> -rf
    >>     > > >     >     :Jewel-Light-NoFlat-Primary-Sunflower-Theme
    >>     > > >     >
    >>     > > >     >
    >>     > > >     >     >
    >>     > > >     >     > There should be Ant targets for starting only on
    >>     > royale-asjs
    >>     > > if
    >>     > > >     >     > royale-compiler and royale=typedefs worked ok.
    >>     > > >     >     >
    >>     > > >     >     > HTH,
    >>     > > >     >     > -Alex
    >>     > > >     >     >
    >>     > > >     >     > On 10/3/18, 11:58 AM, "OmPrakash Muppirala" <
    >>     > > > bigosmallm@gmail.com>
    >>     > > >     > wrote:
    >>     > > >     >     >
    >>     > > >     >     >     Another suggestion I have is - can we do all
    >> the pushes
    >>     > > to
    >>     > > >     > remote after
    >>     > > >     >     >     everything is done locally?  That way, if
    >> something
    >>     > goes
    >>     > > > wrong
    >>     > > >     >     > halfway, we
    >>     > > >     >     >     can just delete the royale-* dirs locally and
    >> rerun the
    >>     > > >     >     > releasecandiate ant
    >>     > > >     >     >     script?
    >>     > > >     >     >
    >>     > > >     >     >     Not sure if this is an easy change?
    >>     > > >     >     >
    >>     > > >     >     >     Thanks,
    >>     > > >     >     >     Om
    >>     > > >     >     >
    >>     > > >     >     >     On Wed, Oct 3, 2018 at 11:42 AM OmPrakash
    >> Muppirala <
    >>     > > >     >     > bigosmallm@gmail.com>
    >>     > > >     >     >     wrote:
    >>     > > >     >     >
    >>     > > >     >     >     > Okay, I tried a couple of times and I have
    >> started
    >>     > > > getting
    >>     > > >     > `SSL peer
    >>     > > >     >     > shut
    >>     > > >     >     >     > down incorrectly errors`
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [INFO]
    >>     > > >     >     >     >
    >>     > > >     >     >
    >>     > > >     >
    >>     > > >
    >>     >
    >> ------------------------------------------------------------------------
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [INFO] BUILD FAILURE
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [INFO]
    >>     > > >     >     >     >
    >>     > > >     >     >
    >>     > > >     >
    >>     > > >
    >>     >
    >> ------------------------------------------------------------------------
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [INFO] Total time: 16:04
    >> min
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [INFO] Finished at:
    >>     > > >     > 2018-10-03T11:38:49-07:00
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [INFO]
    >>     > > >     >     >     >
    >>     > > >     >     >
    >>     > > >     >
    >>     > > >
    >>     >
    >> ------------------------------------------------------------------------
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [ERROR] Failed to execute
    >> goal
    >>     > > >     >     >     >
    >>     > > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
    >>     > > >     >     > (default-deploy)
    >>     > > >     >     >     > on project
    >>     > Jewel-Light-NoFlat-Primary-Sunflower-Theme:
    >>     > > > Failed
    >>     > > >     > to
    >>     > > >     >     > deploy
    >>     > > >     >     >     > artifacts: Could not transfer artifact
    >>     > > >     >     >     >
    >>     > > >     >     >
    >>     > > >     >
    >>     > > >
    >>     > >
    >>     >
    >> org.apache.royale.framework:Jewel-Light-NoFlat-Primary-Sunflower-Theme:swc:0.9.4
    >>     > > >     >     >     > from/to apache.releases.https (
    >>     > > >     >     >     >
    >>     > > >     >     >
    >>     > > >     >
    >>     > > >
    >>     > >
    >>     >
    >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fservice%2Flocal%2Fstaging%2Fdeploy%2Fmaven2&amp;data=02%7C01%7Caharui%40adobe.com%7C7b4f4f106a0e4832f0bc08d62f58b09f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636748455300137124&amp;sdata=1C5tkO6gLEDUOXGLZgwQSkx25Ud8bUG2X6d1DQCaPmQ%3D&amp;reserved=0
    >>     > > >     >     > ):
    >>     > > >     >     >     > Remote host closed connection during
    >> handshake: SSL
    >>     > > peer
    >>     > > > shut
    >>     > > >     > down
    >>     > > >     >     >     > incorrectly -> [Help 1]
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [ERROR]
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [ERROR] To see the full
    >> stack
    >>     > trace
    >>     > > > of the
    >>     > > >     > errors,
    >>     > > >     >     >     > re-run Maven with the -e switch.
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [ERROR] Re-run Maven using
    >> the -X
    >>     > > > switch to
    >>     > > >     > enable
    >>     > > >     >     >     > full debug logging.
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [ERROR]
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [ERROR] For more
    >> information about
    >>     > > the
    >>     > > >     > errors and
    >>     > > >     >     >     > possible solutions, please read the following
    >>     > articles:
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [ERROR] [Help 1]
    >>     > > >     >     >     >
    >>     > > >     >     >
    >>     > > >     >
    >>     > > >
    >>     > >
    >>     >
    >> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionException&amp;data=02%7C01%7Caharui%40adobe.com%7C7b4f4f106a0e4832f0bc08d62f58b09f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636748455300147133&amp;sdata=hvNM5inigC4ldfW8OqDU%2BnocoR%2BZqewteKhWKFdk7bk%3D&amp;reserved=0
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [ERROR]
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [ERROR] After correcting
    >> the
    >>     > > > problems, you
    >>     > > >     > can
    >>     > > >     >     > resume
    >>     > > >     >     >     > the build with the command
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO] [ERROR]   mvn <goals> -rf
    >>     > > >     >     >     > :Jewel-Light-NoFlat-Primary-Sunflower-Theme
    >>     > > >     >     >     >
    >>     > > >     >     >     >      [exec] [INFO]
    >>     > > >     >     >     >
    >>     > > >     >     >
    >>     > > >     >
    >>     > > >
    >>     >
    >> ------------------------------------------------------------------------
    >>     > > >     >     >     >
    >>     > > >     >     >     >
    >>     > > >     >     >     > I am guessing it is a bad internet
    >> connection.  I am
    >>     > > > wondering
    >>     > > >     > if we
    >>     > > >     >     > can
    >>     > > >     >     >     > pass a -rf (resume from) option to the maven
    >> call
    >>     > from
    >>     > > > ant?
    >>     > > >     >     > Otherwise
    >>     > > >     >     >     > doing all this from scratch everytime is a
    >> big pain.
    >>     > > >     >     >     >
    >>     > > >     >     >     > Thanks,
    >>     > > >     >     >     > Om
    >>     > > >     >     >     >
    >>     > > >     >     >     > On Wed, Oct 3, 2018 at 12:47 AM Alex Harui
    >>     > > >     > <aharui@adobe.com.invalid
    >>     > > >     >     > >
    >>     > > >     >     >     > wrote:
    >>     > > >     >     >     >
    >>     > > >     >     >     >> Looks like it was a missing [
    >>     > > >     >     >     >>
    >>     > > >     >     >     >> MXRoyale and SparkRoyale built for me.
    >>     > > >     >     >     >>
    >>     > > >     >     >     >> HTH,
    >>     > > >     >     >     >> -Alex
    >>     > > >     >     >     >>
    >>     > > >     >     >     >> On 10/3/18, 12:43 AM, "OmPrakash Muppirala" <
    >>     > > >     > bigosmallm@gmail.com>
    >>     > > >     >     >     >> wrote:
    >>     > > >     >     >     >>
    >>     > > >     >     >     >>     Thanks!
    >>     > > >     >     >     >>
    >>     > > >     >     >     >>     I reverted everything back to previous
    >> state.  I
    >>     > > > can give
    >>     > > >     > it a
    >>     > > >     >     > shot
    >>     > > >     >     >     >>     tomorrow evening.
    >>     > > >     >     >     >>
    >>     > > >     >     >     >>     Regards,
    >>     > > >     >     >     >>     Om
    >>     > > >     >     >     >>
    >>     > > >     >     >     >>     On Wed, Oct 3, 2018 at 12:41 AM Alex
    >> Harui
    >>     > > >     >     > <aharui@adobe.com.invalid>
    >>     > > >     >     >     >> wrote:
    >>     > > >     >     >     >>
    >>     > > >     >     >     >>     > It was in a releasable state.
    >> TourDeFlex was
    >>     > > > running
    >>     > > >     > on it.
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     > I'm trying to track down the change
    >> that broke
    >>     > > it.
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     > -Alex
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     > On 10/3/18, 12:32 AM, "OmPrakash
    >> Muppirala" <
    >>     > > >     >     > bigosmallm@gmail.com>
    >>     > > >     >     >     >> wrote:
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >     A bit more progress. Now we are
    >> failing on
    >>     > > the
    >>     > > >     > MXRoyale
    >>     > > >     >     > project:
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [INFO]
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>
    >>     > > >     >     >
    >>     > > >     >
    >>     > > >
    >>     >
    >> ------------------------------------------------------------------------
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [INFO] BUILD
    >> FAILURE
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [INFO]
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>
    >>     > > >     >     >
    >>     > > >     >
    >>     > > >
    >>     >
    >> ------------------------------------------------------------------------
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [INFO] Total
    >> time:
    >>     > 01:34
    >>     > > > min
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [INFO] Finished
    >> at:
    >>     > > >     >     > 2018-10-03T00:28:14-07:00
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [INFO]
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>
    >>     > > >     >     >
    >>     > > >     >
    >>     > > >
    >>     >
    >> ------------------------------------------------------------------------
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [ERROR] Failed
    >> to
    >>     > execute
    >>     > > > goal
    >>     > > >     >     >     >>     >
    >>     > > >     >     >
    >>     > > > org.apache.royale.compiler:royale-maven-plugin:0.9.4:compile-as
    >>     > > >     >     >     >>     >     (default-compile-as) on project
    >> MXRoyale:
    >>     > > > There were
    >>     > > >     >     > errors
    >>     > > >     >     >     >> during the
    >>     > > >     >     >     >>     >     build. Got return code 3 -> [Help
    >> 1]
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [ERROR]
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [ERROR] To see
    >> the full
    >>     > > > stack
    >>     > > >     > trace of
    >>     > > >     >     > the
    >>     > > >     >     >     >> errors,
    >>     > > >     >     >     >>     >     re-run Maven with the -e switch.
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [ERROR] Re-run
    >> Maven
    >>     > > using
    >>     > > > the -X
    >>     > > >     >     > switch to
    >>     > > >     >     >     >> enable
    >>     > > >     >     >     >>     > full
    >>     > > >     >     >     >>     >     debug logging.
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [ERROR]
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [ERROR] For more
    >>     > > > information
    >>     > > >     > about the
    >>     > > >     >     >     >> errors and
    >>     > > >     >     >     >>     >     possible solutions, please read the
    >>     > > following
    >>     > > >     > articles:
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [ERROR] [Help 1]
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>
    >>     > > >     >     >
    >>     > > >     >
    >>     > > >
    >>     > >
    >>     >
    >> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionException&amp;data=02%7C01%7Caharui%40adobe.com%7C7b4f4f106a0e4832f0bc08d62f58b09f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636748455300147133&amp;sdata=hvNM5inigC4ldfW8OqDU%2BnocoR%2BZqewteKhWKFdk7bk%3D&amp;reserved=0
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [ERROR]
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [ERROR] After
    >>     > correcting
    >>     > > > the
    >>     > > >     > problems,
    >>     > > >     >     > you
    >>     > > >     >     >     >> can
    >>     > > >     >     >     >>     > resume
    >>     > > >     >     >     >>     >     the build with the command
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >          [exec] [INFO] [ERROR]   mvn
    >> <goals>
    >>     > -rf
    >>     > > >     > :MXRoyale
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >     Can we perhaps turn this project
    >> off?  Is
    >>     > it
    >>     > > > in a
    >>     > > >     >     > releasable
    >>     > > >     >     >     >> state?
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >     On Tue, Oct 2, 2018 at 7:30 PM
    >> OmPrakash
    >>     > > > Muppirala <
    >>     > > >     >     >     >>     > bigosmallm@gmail.com>
    >>     > > >     >     >     >>     >     wrote:
    >>     > > >     >     >     >>     >
    >>     > > >     >     >     >>     >     > I'm going to give this another
    >> shot in a
    >>     > > > couple of
    >>     > > >     >     > hours,
    >>     > > >     >     >     >> unless
    >>     > > >     >     >     >>     > there are
    >>     > > >     >     >     >>     >     > any objections.
    >>     > > >     >     >     >>     >     >
    >>     > > >     >     >     >>     >     > Thanks,
    >>     > > >     >     >     >>     >     > Om
    >>     > > >     >     >     >>     >     >
    >>     > > >     >     >     >>     >     > On Mon, Oct 1, 2018, 2:04 PM
    >> Alex Harui
    >>     > > >     >     >     >> <aharui@adobe.com.invalid>
    >>     > > >     >     >     >>     > wrote:
    >>     > > >     >     >     >>     >     >
    >>     > > >     >     >     >>     >     >> Jewel is mentioned in there.  I
    >> added
    >>     > > > mention of
    >>     > > >     > the
    >>     > > >     >     >     >> migration
    >>     > > >     >     >     >>     > components
    >>     > > >     >     >     >>     >     >> and tour de flex.  Not sure if
    >> I got
    >>     > the
    >>     > > >     > formatting
    >>     > > >     >     > right.
    >>     > > >     >     >     >> I think
    >>     > > >     >     >     >>     > it is
    >>     > > >     >     >     >>     >     >> good enough.
    >>     > > >     >     >     >>     >     >>
    >>     > > >     >     >     >>     >     >> -Alex
    >>     > > >     >     >     >>     >     >>
    >>     > > >     >     >     >>     >     >> On 10/1/18, 12:13 PM, "OmPrakash
    >>     > > > Muppirala" <
    >>     > > >     >     >     >> bigosmallm@gmail.com>
    >>     > > >     >     >     >>     >     >> wrote:
    >>     > > >     >     >     >>     >     >>
    >>     > > >     >     >     >>     >     >>     I updated it, although it
    >> looks a
    >>     > bit
    >>     > > > sparse
    >>     > > >     > now.
    >>     > > >     >     > Can
    >>     > > >     >     >     >> we list
    >>     > > >     >     >     >>     > a few
    >>     > > >     >     >     >>     >     >> major
    >>     > > >     >     >     >>     >     >>     highlights here, that I can
    >> go add
    >>     > to
    >>     > > > the
    >>     > > >     > release
    >>     > > >     >     > notes?
    >>     > > >     >     >     >>     >     >>     Jewel should at least have
    >> several
    >>     > > > updates.
    >>     > > >     >     >     >>     >     >>
    >>     > > >     >     >     >>     >     >>     Thanks,
    >>     > > >     >     >     >>     >     >>     Om
    >>     > > >     >     >     >>     >     >>
    >>     > > >     >     >     >>     >     >>     On Mon, Oct 1, 2018 at
    >> 12:09 PM
    >>     > Alex
    >>     > > > Harui
    >>     > > >     >     >     >>     > <aharui@adobe.com.invalid>
    >>     > > >     >     >     >>     >     >> wrote:
    >>     > > >     >     >     >>     >     >>
    >>     > > >     >     >     >>     >     >>     > Hey, I just noticed that
    >> nobody
    >>     > put
    >>     > > > a 0.9.4
    >>     > > >     >     > section in
    >>     > > >     >     >     >> the
    >>     > > >     >     >     >>     >     >> RELEASE_NOTES.
    >>     > > >     >     >     >>     >     >>     > Maybe just rename the
    >> 0.9.3
    >>     > > section?
    >>     > > >     >     >     >>     >     >>     >
    >>     > > >     >     >     >>     >     >>     > -Alex
    >>     > > >     >     >     >>     >     >>     >
    >>     > > >     >     >     >>     >     >>     > On 10/1/18, 12:07 PM,
    >> "OmPrakash
    >>     > > >     > Muppirala" <
    >>     > > >     >     >     >>     > bigosmallm@gmail.com>
    >>     > > >     >     >     >>     >     >> wrote:
    >>     > > >     >     >     >>     >     >>     >
    >>     > > >     >     >     >>     >     >>     >     Good catch!  I just
    >> pushed a
    >>     > > fix
    >>     > > > for
    >>     > > >     > that.
    >>     > > >     >     >     >>     >     >>     >
    >>     > > >     >     >     >>     >     >>     >     Thanks,
    >>     > > >     >     >     >>     >     >>     >     Om
    >>     > > >     >     >     >>     >     >>     >
    >>     > > >     >     >     >>     >     >>     >     On Mon, Oct 1, 2018
    >> at 11:04
    >>     > AM
    >>     > > > Alex
    >>     > > >     > Harui
    >>     > > >     >     >     >>     >     >> <aharui@adobe.com.invalid>
    >>     > > >     >     >     >>     >     >>     > wrote:
    >>     > > >     >     >     >>     >     >>     >
    >>     > > >     >     >     >>     >     >>     >     > Om,
    >>     > > >     >     >     >>     >     >>     >     >
    >>     > > >     >     >     >>     >     >>     >     > I think the
    >>     > > > <tag>release/0.9.4</tag>
    >>     > > >     > in
    >>     > > >     >     >     >>     > royale-asjs/pom.xml
    >>     > > >     >     >     >>     >     >> needs to
    >>     > > >     >     >     >>     >     >>     > be
    >>     > > >     >     >     >>     >     >>     >     > reverted back to
    >> 0.9.3.
    >>     > > >     >     >     >>     >     >>     >     >
    >>     > > >     >     >     >>     >     >>     >     > Everything else
    >> looks ok
    >>     > from
    >>     > > > my
    >>     > > >     > quick
    >>     > > >     >     >     >> examination.
    >>     > > >     >     >     >>     >     >>     >     >
    >>     > > >     >     >     >>     >     >>     >     > Thanks and good
    >> luck,
    >>     > > >     >     >     >>     >     >>     >     > -Alex
    >>     > > >     >     >     >>     >     >>     >     >
    >>     > > >     >     >     >>     >     >>     >     > On 10/1/18, 10:29
    >> AM,
    >>     > "Piotr
    >>     > > >     > Zarzycki" <
    >>     > > >     >     >     >>     >     >> piotrzarzycki21@gmail.com>
    >>     > > >     >     >     >>     >     >>     > wrote:
    >>     > > >     >     >     >>     >     >>     >     >
    >>     > > >     >     >     >>     >     >>     >     >     I saw your
    >> commit and I
    >>     > > > think you
    >>     > > >     >     > should be
    >>     > > >     >     >     >> ok.
    >>     > > >     >     >     >>     >     >>     >     >
    >>     > > >     >     >     >>     >     >>     >     >     pon., 1 paź
    >> 2018 o
    >>     > 19:21
    >>     > > >     > OmPrakash
    >>     > > >     >     > Muppirala
    >>     > > >     >     >     >> <
    >>     > > >     >     >     >>     >     >>     > bigosmallm@gmail.com>
    >>     > > >     >     >     >>     >     >>     >     >     napisał(a):
    >>     > > >     >     >     >>     >     >>     >     >
    >>     > > >     >     >     >>     >     >>     >     >     > Okay, I did
    >> the
    >>     > > > following to
    >>     > > >     > reset:
    >>     > > >     >     >     >>     >     >>     >     >     >
    >>     > > >     >     >     >>     >     >>     >     >     > For all three
    >> repos:
    >>     > > >     >     >     >>     >     >>     >     >     > * Reverted all
    >>     > > > references of
    >>     > > >     > 0.9.5
    >>     > > >     >     > to 0.9.4
    >>     > > >     >     >     >>     >     >>     >     >     > * Deleted
    >> 0.9.4-rc1
    >>     > tag
    >>     > > >     >     >     >>     >     >>     >     >     > * Deleted
    >> branch:
    >>     > > > release/0.9.4
    >>     > > >     >     >     >>     >     >>     >     >     >
    >>     > > >     >     >     >>     >     >>     >     >     > Can someone
    >> please
    >>     > make
    >>     > > > sure
    >>     > > >     > that we
    >>     > > >     >     > are
    >>     > > >     >     >     >> good
    >>     > > >     >     >     >>     > before
    >>     > > >     >     >     >>     >     >> starting
    >>     > > >     >     >     >>     >     >>     > work?
    >>     > > >     >     >     >>     >     >>     >     >     >
    >>     > > >     >     >     >>     >     >>     >     >     > Thanks,
    >>     > > >     >     >     >>     >     >>     >     >     > Om
    >>     > > >     >     >     >>     >     >>     >     >     >
    >>     > > >     >     >     >>     >     >>     >     >     > On Mon, Oct
    >> 1, 2018
    >>     > at
    >>     > > > 1:51 AM
    >>     > > >     > Carlos
    >>     > > >     >     >     >> Rovira <
    >>     > > >     >     >     >>     >     >>     >     >
    >> carlosrovira@apache.org>
    >>     > > >     >     >     >>     >     >>     >     >     > wrote:
    >>     > > >     >     >     >>     >     >>     >     >     >
    >>     > > >     >     >     >>     >     >>     >     >     > > Hi Om,
    >>     > > >     >     >     >>     >     >>     >     >     > > is related
    >> to flash
    >>     > > > player
    >>     > > >     >     > debugger not
    >>     > > >     >     >     >>     > launched? are
    >>     > > >     >     >     >>     >     >> you on
    >>     > > >     >     >     >>     >     >>     > Mac?
    >>     > > >     >     >     >>     >     >>     >     >     > > I think on
    >> Mac I
    >>     > have
    >>     > > > to
    >>     > > >     > make *.swf
    >>     > > >     >     >     >> files be
    >>     > > >     >     >     >>     > always
    >>     > > >     >     >     >>     >     >> opened
    >>     > > >     >     >     >>     >     >>     > by Flash
    >>     > > >     >     >     >>     >     >>     >     >     > Player
    >>     > > >     >     >     >>     >     >>     >     >     > > debugger.
    >>     > > >     >     >     >>     >     >>     >     >     > >
    >>     > > >     >     >     >>     >     >>     >     >     > > In the
    >> other hand,
    >>     > I
    >>     > > > need to
    >>     > > >     > commit
    >>     > > >     >     >     >> during the
    >>     > > >     >     >     >>     > day
    >>     > > >     >     >     >>     >     >> some
    >>     > > >     >     >     >>     >     >>     > fixes, one
    >>     > > >     >     >     >>     >     >>     >     > on
    >>     > > >     >     >     >>     >     >>     >     >     > > typedefs
    >> and expect
    >>     > > > more on
    >>     > > >     >     > compiler. So
    >>     > > >     >     >     >> if you
    >>     > > >     >     >     >>     > plan
    >>     > > >     >     >     >>     >     >> to try
    >>     > > >     >     >     >>     >     >>     > again
    >>     > > >     >     >     >>     >     >>     >     > some
    >>     > > >     >     >     >>     >     >>     >     >     > > hours ago,
    >> please,
    >>     > > > remove the
    >>     > > >     >     > commits to
    >>     > > >     >     >     >> left
    >>     > > >     >     >     >>     > the
    >>     > > >     >     >     >>     >     >> repos so
    >>     > > >     >     >     >>     >     >>     > we can
    >>     > > >     >     >     >>     >     >>     >     > commit
    >>     > > >     >     >     >>     >     >>     >     >     > > new work
    >>     > > >     >     >     >>     >     >>     >     >     > >
    >>     > > >     >     >     >>     >     >>     >     >     > > thanks!
    >>     > > >     >     >     >>     >     >>     >     >     > >
    >>     > > >     >     >     >>     >     >>     >     >     > > Carlos
    >>     > > >     >     >     >>     >     >>     >     >     > >
    >>     > > >     >     >     >>     >     >>     >     >     > >
    >>     > > >     >     >     >>     >     >>     >     >     > >
    >>     > > >     >     >     >>     >     >>     >     >     > >
    >>     > > >     >     >     >>     >     >>     >     >     > >
    >>     > > >     >     >     >>     >     >>     >     >     > > El lun., 1
    >> oct.
    >>     > 2018
    >>     > > a
    >>     > > > las
    >>     > > >     > 10:29,
    >>     > > >     >     >     >> OmPrakash
    >>     > > >     >     >     >>     > Muppirala
    >>     > > >     >     >     >>     >     >> (<
    >>     > > >     >     >     >>     >     >>     >     >     > >
    >>     > bigosmallm@gmail.com
    >>     > > >)
    >>     > > >     >     >     >>     >     >>     >     >     > > escribió:
    >>     > > >     >     >     >>     >     >>     >     >     > >
    >>     > > >     >     >     >>     >     >>     >     >     > > > I
    >> provided path
    >>     > to
    >>     > > > Chrome
    >>     > > >     > via
    >>     > > >     >     >     >> -Dbrowser, but
    >>     > > >     >     >     >>     > I got
    >>     > > >     >     >     >>     >     >> an
    >>     > > >     >     >     >>     >     >>     > error that
    >>     > > >     >     >     >>     >     >>     >     > ant
    >>     > > >     >     >     >>     >     >>     >     >     > was
    >>     > > >     >     >     >>     >     >>     >     >     > > > not able
    >> to
    >>     > access
    >>     > > > the
    >>     > > >     >     > application.
    >>     > > >     >     >     >>     >     >>     >     >     > > > So, I
    >> tried
    >>     > > > installing
    >>     > > >     > firefox
    >>     > > >     >     > and that
    >>     > > >     >     >     >>     > seemed to
    >>     > > >     >     >     >>     >     >> work.
    >>     > > >     >     >     >>     >     >>     >     >     > > >
    >>     > > >     >     >     >>     >     >>     >     >     > > > On Mon,
    >> Oct 1,
    >>     > 2018
    >>     > > > at
    >>     > > >     > 1:26 AM
    >>     > > >     >     > Piotr
    >>     > > >     >     >     >> Zarzycki
    >>     > > >     >     >     >>     > <
    >>     > > >     >     >     >>     >     >>     >     >     >
    >>     > > > piotrzarzycki21@gmail.com
    >>     > > >     >     >     >>     >     >>     >     >     > > >
    >>     > > >     >     >     >>     >     >>     >     >     > > > wrote:
    >>     > > >     >     >     >>     >     >>     >     >     > > >
    >>     > > >     >     >     >>     >     >>     >     >     > > > > Hi Om,
    >>     > > >     >     >     >>     >     >>     >     >     > > > >
    >>     > > >     >     >     >>     >     >>     >     >     > > > > You did
    >> use
    >>     > > > Firefox for
    >>     > > >     > that
    >>     > > >     >     > purpose
    >>     > > >     >     >     >> ? I
    >>     > > >     >     >     >>     > had to
    >>     > > >     >     >     >>     >     >> specify
    >>     > > >     >     >     >>     >     >>     >     >     > -Dbrowser=path
    >>     > > >     >     >     >>     >     >>     >     >     > > to
    >>     > > >     >     >     >>     >     >>     >     >     > > > >
    >> firefox.exe
    >>     > > >     >     >     >>     >     >>     >     >     > > > >
    >>     > > >     >     >     >>     >     >>     >     >     > > > > Thanks,
    >>     > > >     >     >     >>     >     >>     >     >     > > > > Piotr
    >>     > > >     >     >     >>     >     >>     >     >     > > > >
    >>     > > >     >     >     >>     >     >>     >     >     > > > > pon., 1
    >> paź
    >>     > 2018
    >>     > > o
    >>     > > > 10:22
    >>     > > >     >     > OmPrakash
    >>     > > >     >     >     >>     > Muppirala <
    >>     > > >     >     >     >>     >     >>     >     >
    >> bigosmallm@gmail.com>
    >>     > > >     >     >     >>     >     >>     >     >     > > > >
    >> napisał(a):
    >>     > > >     >     >     >>     >     >>     >     >     > > > >
    >>     > > >     >     >     >>     >     >>     >     >     > > > > > Okay,
    >> I made
    >>     > > > several
    >>     > > >     > attempts
    >>     > > >     >     >     >> through the
    >>     > > >     >     >     >>     > day,
    >>     > > >     >     >     >>     >     >> making
    >>     > > >     >     >     >>     >     >>     >     > progress each
    >>     > > >     >     >     >>     >     >>     >     >     > > > time.
    >>     > > >     >     >     >>     >     >>     >     >     > > > > >  The
    >> last run
    >>     > > > failed
    >>     > > >     > because
    >>     > > >     >     > the
    >>     > > >     >     >     >> browser
    >>     > > >     >     >     >>     > could
    >>     > > >     >     >     >>     >     >> not be
    >>     > > >     >     >     >>     >     >>     >     > launched.
    >>     > > >     >     >     >>     >     >>     >     >     > > > > > I am
    >> going to
    >>     > > > pause on
    >>     > > >     > this
    >>     > > >     >     > and
    >>     > > >     >     >     >> try again
    >>     > > >     >     >     >>     >     >> tomorrow (or
    >>     > > >     >     >     >>     >     >>     >     > later) . If
    >>     > > >     >     >     >>     >     >>     >     >     > > > > someone
    >>     > > >
    >
    >
    >
    > --
    >
    > Piotr Zarzycki
    >
    > Patreon: *https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C7b4f4f106a0e4832f0bc08d62f58b09f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636748455300147133&amp;sdata=vhmED%2Bw%2BDFOYmZnwbQpTfgXrEKyeFkxAkRbrYIK5L3U%3D&amp;reserved=0
    > <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C7b4f4f106a0e4832f0bc08d62f58b09f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636748455300147133&amp;sdata=vhmED%2Bw%2BDFOYmZnwbQpTfgXrEKyeFkxAkRbrYIK5L3U%3D&amp;reserved=0>*
    >
    
    
    -- 
    
    Piotr Zarzycki
    
    Patreon: *https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C7b4f4f106a0e4832f0bc08d62f58b09f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636748455300147133&amp;sdata=vhmED%2Bw%2BDFOYmZnwbQpTfgXrEKyeFkxAkRbrYIK5L3U%3D&amp;reserved=0
    <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&amp;data=02%7C01%7Caharui%40adobe.com%7C7b4f4f106a0e4832f0bc08d62f58b09f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636748455300147133&amp;sdata=vhmED%2Bw%2BDFOYmZnwbQpTfgXrEKyeFkxAkRbrYIK5L3U%3D&amp;reserved=0>*
    

Mime
View raw message