Alex,
In the other words If I have time today I can continue with the process? We
end up with situation where I need to remove tag and try again as I
remember?
Thanks,
Piotr
On Fri, Oct 12, 2018, 7:12 AM Alex Harui <aha...@adobe.com.invalid> wrote:
> Hi Piotr,
>
> I agree with your sentiments. However, I think one problem is that the
> revert emails are misleading. Unlike other commits, the subject of a
> revert does not show what branch was changed, so I think Carlos was
> reverting things in a branch.
>
> That said, it is still very troublesome that his Git tools are changing
> the tags. IMO, Carlos will have to stop using that tool.
>
> -Alex
>
> On 10/11/18, 9:57 PM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com> wrote:
>
> Carlos,
>
> You are expecting from people who are volunteers to do some things in
> one
> day? It's impossible to do that. I'm not working on that full time. I
> did
> first finally successful step for the release. Everything was reported
> on
> this list. I had problems and didn't have time to resolve it. Alex
> provide
> solution - next RM should pickup it and continue release. It can take
> days.
> If you have problems you should create branch from the last stable
> commit.
> Is it problem for you ?
>
> How can we now get back to the previous state now?
>
> Piotr
>
> pt., 12 paź 2018 o 02:09 Carlos Rovira <carlosrov...@apache.org>
> napisał(a):
>
> > Hi Alex,
> > if you check in actual develop for "0.9.5-SNAPSHOT" and
> "0.9.4-SNAPSHOT"
> > you'll see maven build compiler and typedefs 0.9.5-SNAPSHOT, but
> when build
> > framework, it downloads compiler and typedefs 0.9.4-SNAPSHOT since
> the
> > versions in framework are not updated. This is the reason you don't
> see any
> > fail when building with maven. If you update all to use the same
> number it
> > will fail. I recommend you as well to remove royale folder in your
> local
> > .m2 to see how maven generates compiler and typedefs and then
> download
> > other version.
> >
> > Maybe the rest of people didn't see this because they use ANT and
> that
> > build system is not affected by the release process. But I think we
> can't
> > left the failed release process without revert it for days, since we
> are
> > all seeing different things.
> >
> > For example, I was able to run your MX RO example with ANT, but I
> can make
> > it work with Maven, what means to me that I still can't use it since
> my
> > entire project is in maven.
> >
> > I'm trying to fix this for several hours now and still couldn't test
> mx RO
> > nor working on my project...
> >
> > I'm closing for today with all messed up. Tomorrow will try again,
> or will
> > need to block me in a branch to be able to continue working.
> >
> > Thanks
> >
> > Carlos
> >
> >
> >
> >
> >
> > El vie., 12 oct. 2018 a las 1:53, Alex Harui
> (<aha...@adobe.com.invalid>)
> > escribió:
> >
> > > The 0.9.4 release branch has been cut. I have not seen any
> problems
> > > reported against it, so I don't know of any reason to delete it.
> Thus,
> > the
> > > develop branch should be at 0.9.5-SNAPSHOT.
> > >
> > > I noticed you messed around with the versions so I have no idea
> what
> > state
> > > we are in, plus I continue to see that tags are being updated.
> You will
> > > probably have to stop using your Git GUI. We cannot have tags be
> > modified.
> > >
> > > -Alex
> > >
> > > On 10/11/18, 3:14 PM, "Carlos Rovira" <carlosrov...@apache.org>
> wrote:
> > >
> > > Hi,
> > >
> > > I'm a bit confused with the actual state of the repo. We
> should stay
> > in
> > > 0.9.4-SNAPSHOT? or 0.9.5-SNAPSHOT?
> > > I'm building with the latest since 1-2 days but removed all
> royale
> > > folder
> > > with all maven artifacts and rebuild from scratch, makes me
> have
> > mixed
> > > versions, since some artifacts are downloading 0.9.4 instead
> of use
> > > 0.9.5
> > >
> > > Piotr, seems nobody take the request to continue with the
> release
> > for
> > > now,
> > > so I propose to stabilize the repo.
> > >
> > > Thoughts?
> > >
> > > Carlos
> > >
> > >
> > >
> > >
> > >
> > > El jue., 11 oct. 2018 a las 20:33, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Alex,
> > > >
> > > > Unfortunately in the next couple of days I won't have time
> for
> > that.
> > > If
> > > > someone can do that feel free jump into it.
> > > >
> > > > Piotr
> > > >
> > > > On Thu, Oct 11, 2018, 6:43 PM Alex Harui
> <aha...@adobe.com.invalid
> > >
> > > wrote:
> > > >
> > > > > 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" <
> > piotrzarzyck...@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&data=02%7C01%7Caharui%40adobe.com%7C4c851882cf524936feab08d62fff3679%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636749170511993420&sdata=WrehniBEFG2PAqOOlZ7PxvO721oPIp14GNOV5zYtkxQ%3D&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 <
> > > piotrzarzyck...@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&data=02%7C01%7Caharui%40adobe.com%7C4c851882cf524936feab08d62fff3679%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636749170511993420&sdata=7H8bB%2Fcfzoej2%2BKyWfLhD1fYLD14j%2BU%2BNeP4%2F5FP1KE%3D&reserved=0
> > > > > >
> > > > > > Thanks,
> > > > > > Piotr
> > > > > >
> > > > > > śr., 10 paź 2018 o 17:50 Alex Harui
> > <aha...@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" <
> > > piotrzarzyck...@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&data=02%7C01%7Caharui%40adobe.com%7C4c851882cf524936feab08d62fff3679%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636749170511993420&sdata=N7mNbeXjpXHVFoHsYjERoaoTYSaqoLBYPwi9KJh1e54%3D&reserved=0
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Piotr
> > > > > >>
> > > > > >>
> > > > > >> śr., 10 paź 2018 o 11:34 Carlos Rovira <
> > > > carlosrov...@apache.org
> > > > > >
> > > > > >> napisał(a):
> > > > > >>
> > > > > >> > Ok Piotr, good luck! :)
> > > > > >> >
> > > > > >> > El mié., 10 oct. 2018 a las 10:34, Piotr
> Zarzycki (<
> > > > > >> > piotrzarzyck...@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
> > > > > <aha...@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" <
> > > > > >> bigosma...@gmail.com>
> > > > > >> > > wrote:
> > > > > >> > > >
> > > > > >> > > > On Thu, Oct 4, 2018 at 1:48 AM Alex
> Harui
> > > > > >> <aha...@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" <
> > > > > >> bigosma...@gmail.com
> > > > > >> > >
> > > > > >> > > > wrote:
> > > > > >> > > > >
> > > > > >> > > > > On Wed, Oct 3, 2018 at 2:02 PM
> Alex
> > > Harui
> > > > > >> > > > <aha...@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&data=02%7C01%7Caharui%40adobe.com%7C4c851882cf524936feab08d62fff3679%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636749170511993420&sdata=avwL9WdViB%2FT8BbuHI4JKTal68yJ5FHGTVIJkRCZHeM%3D&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"
> > > > <
> > > > > >> > > > bigosma...@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 <
> > > > > >> > > > > > bigosma...@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&data=02%7C01%7Caharui%40adobe.com%7C4c851882cf524936feab08d62fff3679%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636749170511993420&sdata=H5hBmJ710nh%2BOins3UWZBPnT2uauxBxp1AmfxYlPL4o%3D&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&data=02%7C01%7Caharui%40adobe.com%7C4c851882cf524936feab08d62fff3679%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636749170511993420&sdata=DydPCLlicCVtZNy%2FYGxISlhxVp811yQCfGmi0HN2j8E%3D&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
> > > > > >> > > > > <aha...@adobe.com.invalid
> > > > > >> > > > > > >
> > > > > >> > > > > > > wrote:
> > > > > >> > > > > > >
> > > > > >> > > > > > >> Looks like it was a
> missing [
> > > > > >>
