Re: Discuss of release steps preparation

Because it means it is possible that the wrong version got into build.properties. -Alex On 9/17/19, 11:20 AM, "Piotr Zarzycki" wrote: Alex, I will fix those issues once we make current release. Both of them are not a blockers in my opinion. How issue in release

Re: Discuss of release steps preparation

If you had to do that, how do you know the RC is still valid? Sounds like there is a version number that isn't right in the source package. One reason to have scripts is to detect things that are not right. Yes there might be bugs in the scripts, but if you didn't have to do this before, it

Re: Discuss of release steps preparation

Another small issue which I discovered is that I had to specify in Step 13 -Drelease.version=0.9.6 -Dreleaseversion=0.9.6 - With dot and without dot, cause script failed on compiler cloning. Thanks, Piotr wt., 17 wrz 2019 o 10:47 Piotr Zarzycki napisał(a): > Hi Guys, > > I'm in a process of

Re: Discuss of release steps preparation

Hi Guys, I'm in a process of uploading Maven artifacts and after upload I got following problem [1]. I will sign those artifacts manually, but this is something what should be fixed in the script for the next release. [1] https://ibb.co/zh0r5nn Thanks, Piotr niedz., 15 wrz 2019 o 08:18 Alex

Re: Discuss of release steps preparation

Glad you are getting back to normal. Please review what is in the release branch before the RC so we can fix things before Piotr spends a lot of time creating the RC. https://github.com/apache/royale-asjs/blob/release/0.9.6/RELEASE_NOTES.md

Re: Discuss of release steps preparation

We have power and internet again, at last. I guess I should wait to review texts until the next version of the release candidate. On Sat, Sep 14, 2019 at 3:01 PM Piotr Zarzycki wrote: > Hi Carlos, > > I see you did commit to 0.9.6 branch, so we are good unless there is > something left in

Discuss of release steps preparation

Hi Carlos, I see you did commit to 0.9.6 branch, so we are good unless there is something left in develop which should I pick. I will review all of that on Monday. Thanks, Piotr On Sat, Sep 14, 2019, 5:26 PM Carlos Rovira wrote: > Hi Piotr, > > seems there was a little confusion here and Greg

Re: Discuss of release steps preparation

Hi Alex, Yesterday I forgot to email this. I installed NPM beta10 version. this is my results: *macbookpro:~ carlosrovira$ mxmlc* *Using Royale Compiler codebase: /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../..* *Using Royale SDK:

Re: Discuss of release steps preparation

Hi Piotr, seems there was a little confusion here and Greg and I did the changes in the release version of RELEASE_NOTES. Hope you can merge both in your process. I followed my changes since December to try to bring all relevant things done. Thanks El sáb., 14 sept. 2019 a las 15:39, Piotr

Re: Discuss of release steps preparation

Hi Greg, I'm sorry for a late response. I'm going to take what's develop has in it on Monday by cherry picking - to do not break release branch, so where you commit it will be good and won't miss it. Thanks, Piotr pt., 13 wrz 2019 o 19:24 Greg Dove napisał(a): > Hi Piotr, > > I'm not so

Re: Discuss of release steps preparation

Hi, thanks Greg for bringing all that stuff. I completely forgot about all that improvements. I'm thinking that for Jewel there's many improvements. As well MX/Spark emulation have many ones too. I'll try to see if I can add some for Jewel. For MX/Spark emulation maybe others that worked on it

Re: Discuss of release steps preparation

I tested the installation (beta 10) and the subsequent steps using royale-cli and everything seems to be working. Thanks for all the fixes, Alex. Regards, Om On Fri, Sep 13, 2019 at 10:33 AM Greg Dove wrote: > Oh thanks, Josh! I will do that later today. > > > On Sat, Sep 14, 2019 at 5:32 AM

Re: Discuss of release steps preparation

Oh thanks, Josh! I will do that later today. On Sat, Sep 14, 2019 at 5:32 AM Josh Tynjala wrote: > In royale-compiler, I already added my release notes from develop into > release/0.9.6. I simply forgot to do the same for royale-asjs. I added > that > line about RoyaleUnit just now. Go ahead

Re: Discuss of release steps preparation

In royale-compiler, I already added my release notes from develop into release/0.9.6. I simply forgot to do the same for royale-asjs. I added that line about RoyaleUnit just now. Go ahead and add yours too, Greg. We'll be merging release/0.9.6 back into develop later, so if you put them directly

Re: Discuss of release steps preparation

Hi Piotr, I'm not so familiar with the release process. Do you want additions to go directly into the release branch or should that be added to develop (assuming you would merge into release)? I see Josh added note about RoyalUnit in develop [1], which is not yet in release.[2] . So perhaps you

Discuss of release steps preparation

Hi Guys, I would like to cut RC1 again on Monday, so if anything should be tested or added please do so before Monday. Let me know if anything is against that. Thanks, Piotr On Fri, Sep 13, 2019, 12:32 AM Alex Harui wrote: > I pushed changes to update the config.xml files. It seemed to work

Re: Discuss of release steps preparation

I pushed changes to update the config.xml files. It seemed to work for me. Try beta10 if you want to test it. npm install @apache-royale/royale-js-swf@0.9.6-beta10 -g Thanks, -Alex On 9/12/19, 10:56 AM, "Alex Harui" wrote: I guess that’s expected. I didn’t realize I had a

Re: Discuss of release steps preparation

I guess that’s expected. I didn’t realize I had a PLAYERGLOBAL_HOME environment variable that was overriding. The post install script would have to go replace the target-player in every -config.xml file (like royale-config.xml). If you add -target-player=25.0, that will get you past it.

Re: Discuss of release steps preparation

Hi Alex, I uninstall then install again. Commented all my paths (royale, flash player, AIR,...) in my .bash_profile. Then open a new terminal window. Results: macbookpro:~ carlosrovira$ mxmlc Using Royale Compiler codebase:

Re: Discuss of release steps preparation

Thanks for catching the places where FlexJS was still being used. Your output indicates that there is a ROYALE_HOME environment variable so it appears to be using your dev versions since I don't think NPM would store its stuff in /Users/carlosrovira/Dev. Anyway, good to know that the

Re: Discuss of release steps preparation

I installed the npm package on Windows 10 successfully, and I see that mxmlc, compc, asjsc, asjscompc, and asnodec all seem to be available on my path, and I can run them. -- Josh Tynjala Bowler Hat LLC On Thu, Sep 12, 2019 at 1:53 AM Carlos Rovira wrote: > Hi, > >

Re: Discuss of release steps preparation

Hi, think al went fine :) this is my output: + @apache-royale/royale-js-swf@0.9.6-beta9 added 146 packages from 108 contributors in 426.831s then I tried "mxmlc" just from command line: macbookpro:~ carlosrovira$ mxmlc Using Royale Compiler codebase:

Re: Discuss of release steps preparation

gt; > > >> > > > You are seeing full console output > > actually. > > > > Nothing > > > > >> more > > > > >> >

Re: Discuss of release steps preparation

> > > > >> > > > > Yes, you have set the variables, but > have > > the > > > other > > > >> steps > > > >> > run that > > > >> > > > > generate an SVN

Re: Discuss of release steps preparation

> >> > > > > Again, the goal is here to debug the > > scripts, > > > not to > > > >> skip > > > >> > them. > >

Re: Discuss of release steps preparation

> > > > related to it. > > >> > > > > > > >> > > > > HTH, > > >> > > > > -Alex > > >> > > > > > > >>

Re: Discuss of release steps preparation

y upload artifacts >>> > manually and >>> > > > run RC1. >>> > > > > >>> > > > > śr., 4 wrz 2019 o 16:30 Piotr Zarzycki < >>> > > &g

Re: Discuss of release steps preparation

> > >> > > > > > Buildfile: >> > > /Users/piotr/Downloads/royale/releasesteps_asjs.xml >> > > > > > >> > > > > > check-name-and-svn: >> > > > >

Discuss of release steps preparation

gt; [echo] svn.dist.release: > > > > > /Users/piotr/Downloads/royale/dist/release > > > > > > [echo] svn: /usr/bin/svn > > > > > > > > > > > > BUILD FAILED > > > > > > > > /Users/piotr/Downloads/royale/releasesteps_asjs.xml:1537: The > > > > > svn.dist.dev > &

Re: Discuss of release steps preparation

> /Users/piotr/Downloads/royale/dist/release > > > > > > [echo] svn: /usr/bin/svn > > > > > > > > > > > > BUILD FAILED > > > > > > > > /Users/piotr/Downloads/royale/releasesteps_asjs.xml:1537: The > > > > > svn.dist.dev >

Discuss of release steps preparation

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdevdata=02%7C01%7Caharui%40adobe.com%7Cd8000c2487bb40a3e66908d732b94347%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637033643651232147sdata=TnDwwWNdgu4txHMAqvSb0YyiOVKqYjCq98uxb0m7AMA%3Dreserved=0 > > > > . > > > > > > > > > > As you can see above I have

Re: Discuss of release steps preparation

794aed2c178decee1%7C0%7C0%7C637032107443413136sdata=Et8HJHapB3FvMonYzhnsfNoonvUfRd1VNr5GUktMcDs%3Dreserved=0 > > > > . > > > > > > > > > > As you can see above I have all properties setup cause I > made > > > an > > >

Re: Discuss of release steps preparation

> > > > > > > Thanks, > > > > Piotr > > > > > > > > śr., 4 wrz 2019 o 13:13 Piotr Zarzycki < > > piotrzarzyck...@gmail.com> > > > > napisał(a): > > >

Re: Discuss of release steps preparation

> > > napisał(a): > > > > > >> I was able to produce ant artifacts on Mac! I will try get an > RC1 > > today. > > >> > > >> śr., 4 wrz 2019 o 11:11 Yishay Weiss > > napisał(a): >

Re: Discuss of release steps preparation

t;>> > >>> > >>> > >>> ANT_HOME > >>> > >>> C:\dev\ant\apache-ant-1.10.1 > >>> > >>> > >>> > >>>

Re: Discuss of release steps preparation

> >>> Here’s what I’ve got. > >>> > >>> > >>> > >>> ANT_HOME > >>> > >>> C:\dev\ant\apache-ant-1.10.1 > >>> > >>> > >>> > >>> __

Re: Discuss of release steps preparation

; ANT_HOME >>> >>> C:\dev\ant\apache-ant-1.10.1 >>> >>> >>> >>> >>> From: Piotr Zarzycki >>> Sent: Wednesday, September 4, 2019 11:56:02 AM >>> To: de

Re: Discuss of release steps preparation

Yishay Weiss napisał(a): >> >>> Here’s what I’ve got. >>> >>> >>> >>> ANT_HOME >>> >>> C:\dev\ant\apache-ant-1.10.1 >>> >>> >>> >>> >>> From: Piotr Zar

Re: Discuss of release steps preparation

/sources/royale-asjs/build.xml:1636: >> > >> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/${env.ANT_HOME}/lib >> > does not exist. >> > >> > >> > >> > Is ANT_HOME env var defined? >> > >> > >>

Re: Discuss of release steps preparation

ycki > Sent: Wednesday, September 4, 2019 11:56:02 AM > To: dev@royale.apache.org > Subject: Re: Discuss of release steps preparation > > Hi Yishay, > > It was pretty stupid from my sight. I was certain that I have this env > variable setup, cause ant is working for me.

RE: Discuss of release steps preparation

Here’s what I’ve got. ANT_HOME C:\dev\ant\apache-ant-1.10.1 From: Piotr Zarzycki Sent: Wednesday, September 4, 2019 11:56:02 AM To: dev@royale.apache.org Subject: Re: Discuss of release steps preparation Hi Yishay, It was pretty stupid from my sight. I

Re: Discuss of release steps preparation

r Zarzycki > Sent: Wednesday, September 4, 2019 11:24:09 AM > To: dev@royale.apache.org > Subject: Re: Discuss of release steps preparation > > Hi, > > It moved farther, but failed with different stacktrace [1]. I will try to > investigate this, unless someone has immediate

RE: Discuss of release steps preparation

From: Piotr Zarzycki Sent: Wednesday, September 4, 2019 11:24:09 AM To: dev@royale.apache.org Subject: Re: Discuss of release steps preparation Hi, It moved farther, but failed with different stacktrace [1]. I will try to investigate this, unless someone has immediate idea why I got that issue

Re: Discuss of release steps preparation

gt; > > > > > >> > > wrote: > > > >> > > > > > >> > > > In Mac is different - maybe I setup it wrong. Does anyone > know > > > >> whether > > > >> > I > > > >>

Re: Discuss of release steps preparation

t;flashplayer.app" or just "flashplayer"? > > >> > > > > > >> > > > Thanks, > > >> > > > Piotr > > >> > > > > > >> > > > > > >> > > > >

Re: Discuss of release steps preparation

gt; > In Mac is different - maybe I setup it wrong. Does anyone know > > >> whether > > >> > I > > >> > > > should setup it to "flashplayer.app" or just "flashplayer"? > > >> > > > > > >> > > > Thanks,

Re: Discuss of release steps preparation

. Does anyone know > >> whether > >> > I > >> > > > should setup it to "flashplayer.app" or just "flashplayer"? > >> > > > > >> > > > Thanks, > >> > > > Piotr > >> > > > > >> > > > > >> > > > > >> > > > On Tue

Re: Discuss of release steps preparation

tup it to "flashplayer.app" or just "flashplayer"? > >> > > > > >> > > > Thanks, > >> > > > Piotr > >> > > > > >> > > > > >> > > > > >> > > > On

Re: Discuss of release steps preparation

> > wrote: >> > > > >> > > > > All failures look to be on flash tests. Are you sure you’re >> pointing >> > at >> > > > > the right FLASHPLAYER_DEBUGGER? >> > > > > >> > > > >

Re: Discuss of release steps preparation

ures look to be on flash tests. Are you sure you’re > pointing > > at > > > > > the right FLASHPLAYER_DEBUGGER? > > > > > > > > > > > > > > > > > > > > I have env var > > > > > > > >

Re: Discuss of release steps preparation

to be on flash tests. Are you sure you’re pointing > at > > > > the right FLASHPLAYER_DEBUGGER? > > > > > > > > > > > > > > > > I have env var > > > > > > > > > > > > > > > > FLASHPLAYER_DEBUGGER >

Re: Discuss of release steps preparation

UGGER? > > > > > > > > > > > > I have env var > > > > > > > > > > > > FLASHPLAYER_DEBUGGER > > > > > > == > > > > > > C:\dev\flash\flashplayer_18_sa_debug.exe > > > > > > > > > > > > ___

Re: Discuss of release steps preparation

> > > > > > > > I have env var > > > > > > > > FLASHPLAYER_DEBUGGER > > > > == > > > > C:\dev\flash\flashplayer_18_sa_debug.exe > > > > > > > > ____________ > > From: Piotr Zar

Discuss of release steps preparation

gt;> further up in the output? > >> > >> > >> > >> [1] [junit] > >> > /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-compiler/compiler/target/junit-temp/ASDateTests2436056786678332499.as(16): > >> col: 1 Error: Prope

RE: Discuss of release steps preparation

To: dev@royale.apache.org Subject: Re: Discuss of release steps preparation Ok but in folder junit-reprots there were two files [1][2] [1] https://paste.apache.org/fu49t [2] https://paste.apache.org/2dd6c wt., 3 wrz 2019 o 14:46 Piotr Zarzycki napisał(a): > Hi Yishay, > > In

Re: Discuss of release steps preparation

eTests2436056786678332499.as(16): >> col: 1 Error: Property timezoneOffset is read-only. >> >> >> >> >> >> ________ >> From: Piotr Zarzycki >> Sent: Tuesday, September 3, 2019 2:52:11 PM >> To: dev@royale.apache.org >>

Re: Discuss of release steps preparation

ler/compiler/target/junit-temp/ASDateTests2436056786678332499.as(16): > col: 1 Error: Property timezoneOffset is read-only. > > > > > > > From: Piotr Zarzycki > Sent: Tuesday, September 3, 2019 2:52:11 PM > To: dev@royale.apache.org > Subject: R

RE: Discuss of release steps preparation

Subject: Re: Discuss of release steps preparation I have setup my Mac instead to have a ANT build. Unfortunately one of the compiler test failed [1]. I have used -DskipTests=true, so why actually those tests run ? [1] https://paste.apache.org/kzm3t wt., 3 wrz 2019 o 12:20 Piotr Zarzycki napisał

Re: Discuss of release steps preparation

I have setup my Mac instead to have a ANT build. Unfortunately one of the compiler test failed [1]. I have used -DskipTests=true, so why actually those tests run ? [1] https://paste.apache.org/kzm3t wt., 3 wrz 2019 o 12:20 Piotr Zarzycki napisał(a): > Just FYI I have tried several times and

Re: Discuss of release steps preparation

Just FYI I have tried several times and I still cannot properly prepare ANT artifacts for 0.9.6 release. I have uninstall TortoiseGIT, but files which I cannot delete has been still hold by some processes related to build. I'm going to try this very last step do on our remote PC to see whether it

Re: Discuss of release steps preparation

Failonerror is typically false when deleting in case the folder has already been deleted. Pretty sure that at least on Windows, if a jar is being used by a running application that you cannot delete the jar. In theory, the Ant scripts should not be loading jars when building the source

Re: Discuss of release steps preparation

I think that's the option. :) I hope I will finally get to an end this. śr., 28 sie 2019 o 17:27 Josh Tynjala napisał(a): > With that in mind, it seems like you may need to temporarily disable > TortoiseGit while running the build. > > -- > Josh Tynjala > Bowler Hat LLC

Re: Discuss of release steps preparation

With that in mind, it seems like you may need to temporarily disable TortoiseGit while running the build. -- Josh Tynjala Bowler Hat LLC On Wed, Aug 28, 2019 at 6:28 AM Piotr Zarzycki wrote: > I'm not sure if it's related, but I have tried deleted that folder manually

Re: Discuss of release steps preparation

I'm not sure if it's related, but I have tried deleted that folder manually and it's being blocked by Git [1] [1] https://ibb.co/bsm48DV Thanks, Piotr śr., 28 sie 2019 o 15:07 Piotr Zarzycki napisał(a): > I have modified build.xml script locally and I got following result -> >

Re: Discuss of release steps preparation

I have modified build.xml script locally and I got following result -> https://paste.apache.org/m5mz5 What can hold that jar file ? śr., 28 sie 2019 o 14:23 Piotr Zarzycki napisał(a): > Hi Alex, > > I just made another attempt and it's failed. I missed your information > that

Re: Discuss of release steps preparation

Hi Alex, I just made another attempt and it's failed. I missed your information that "royale-asjs/js/lib/ " contains 2 jar files. I see them on my machine. I see also that we have [1] deletion line for that. My fix for deleting helped so far to get rid of problem with RoyaleUnit [2]. Maybe we

Re: Discuss of release steps preparation

Ahh!! That could be the case! Thanks for this I will try to check. Probably I should just analyze what is happen in current nightly build. wt., 27 sie 2019 o 07:03 Alex Harui napisał(a): > I could be wrong, but I believe that files are not missing. Files in the > target folder (and the target

Re: Discuss of release steps preparation

I could be wrong, but I believe that files are not missing. Files in the target folder (and the target folder itself) never got deleted/cleaned. HTH, -Alex On 8/26/19, 10:00 PM, "Piotr Zarzycki" wrote: I have moved RoyaleUnit to normal build for Maven. I'm thinking about ANT build

Re: Discuss of release steps preparation

I have moved RoyaleUnit to normal build for Maven. I'm thinking about ANT build more, if you did after that module creation with build the same what's with other why actually we have any kind of problems during release process. Why some files are missing... I need to dive into that more. pon.,

Re: Discuss of release steps preparation

Yeah, I think you should be able to add the project to Maven. If the pom is missing or incomplete, I expect that you can basically copy another project's pom and change a few names to get it working. Sorry for the trouble! It's easy to forget Maven sometimes. I'm surprised that this didn't come

Re: Discuss of release steps preparation

You are basically saying that in case of Maven I should try to move it as an standard module build. In case of Ant build I will try to figure it out - if I won't be able to I will wait to your free cycles. Thanks, Piotr pon., 26 sie 2019 o 16:39 Josh Tynjala napisał(a): > I guess that I

Re: Discuss of release steps preparation

I guess that I completely forgot to add RoyaleUnit to the Maven build. Someone else must have added it to the "broken" thing because I have no idea what that is. With the Ant build, I tried my best to copy what the build was doing with the other libraries. I guess this means that I missed some

Re: Discuss of release steps preparation

Hi Josh, You were working on RoyaleUnit ? I see that it is not even part of Maven build but it is part of profile "brokenbuild" [1]. In case of ANT see that this module is part of the build, but obviously something doesn't work in the end. [2] I'm not sure what actually I should do with that ?

Re: Discuss of release steps preparation

Alex, I see what is happening. I had the same issue when I was preparing Maven artifacts - I think so. Royale unit is not part of final src zip -> https://ibb.co/44ByBKV I have to figure out how add it there. Thanks, Piotr pon., 26 sie 2019 o 08:35 Alex Harui napisał(a): > The two zips are

Re: Discuss of release steps preparation

The two zips are different. The second zip contains several files that the first one doesn't. Try using other diff tools to find one that will help you see the differences. I just use my Mac's *nix command line with "diff -rwq" and "find". Cygwin and GitBash should have those tools on

Re: Discuss of release steps preparation

Links: zip1: https://1drv.ms/u/s!ApVpLyjpHDC2ic0S8UffcFPmhXGKGQ?e=ZstLev zip2: https://1drv.ms/u/s!ApVpLyjpHDC2ic0TPORa2P9OKsWRiw?e=k8fQ7T Thanks, Piotr pon., 26 sie 2019 o 00:48 Alex Harui napisał(a): > Looks like there are 130 files in the "left" folder that aren't in the > "right"? Or I

Re: Discuss of release steps preparation

Looks like there are 130 files in the "left" folder that aren't in the "right"? Or I don't understand the output of whatever tool you are using. Post a link to the two zips if you want. HTH, -Alex On 8/25/19, 3:08 PM, "Piotr Zarzycki" wrote: Content in both zips is exactly the same.

Re: Discuss of release steps preparation

Content in both zips is exactly the same. I don't see now the reason to do not move forward with that -> https://ibb.co/XzDDVfd pon., 26 sie 2019 o 00:01 Piotr Zarzycki napisał(a): > Sorry that's not my day. It looks like my folder in Total Commander wasn't > refreshed. Both zips exists. I

Re: Discuss of release steps preparation

Sorry that's not my day. It looks like my folder in Total Commander wasn't refreshed. Both zips exists. I will compare them and provide results. On Sun, Aug 25, 2019, 11:58 PM Piotr Zarzycki wrote: > Alex, > > I just checked and I was mistake. Zip which should be inside source folder > is not

Re: Discuss of release steps preparation

Alex, I just checked and I was mistake. Zip which should be inside source folder is not exists at all. I'm wondering what could happen that this zip wasn't generated. Thanks, Piotr On Sun, Aug 25, 2019, 11:52 PM Alex Harui wrote: > The output says the -src.zip did not compare. Expand the two

Re: Discuss of release steps preparation

The output says the -src.zip did not compare. Expand the two zip files into different folders and compare the folders. HTH, -Alex On 8/25/19, 2:45 PM, "Piotr Zarzycki" wrote: Hi, I have spend another hours on release. Maven artifacts are deployed to the staging without the

Re: Discuss of release steps preparation

Hi, I have spend another hours on release. Maven artifacts are deployed to the staging without the problem. I stopped this time and the very end of the process, where I need to prepare ANT artifacts. Build on my PC failed [1] - size of compared zips are different - Step 13. During whole process

Re: Discuss of release steps preparation

Piotr, At this point, I would definitely recommend trying the three steps without any changes to the release_steps.xml file and use an ABSOLUTE path. That's the only way I tested the scripts. I did not try a relative path, and I highly recommend not putting all of these files in a working

Re: Discuss of release steps preparation

It looks like this is again problem with RoyaleUnit[1]. Here is the results of comparison. I'm not sure why left folder doesn't contains files. [1] https://pasteboard.co/IsWnHGq.png Thanks, Piotr pt., 16 sie 2019 o 11:08 Piotr Zarzycki napisał(a): > Ok I was mistake. Both zips exists, but

Re: Discuss of release steps preparation

Ok I was mistake. Both zips exists, but they have different sizes! So comparison went fine and I need to understand one sources are different... pt., 16 sie 2019 o 10:59 Piotr Zarzycki napisał(a): > I have analyzed that target (compare-src-zips) and it compares zip file in > following

Re: Discuss of release steps preparation

I have analyzed that target (compare-src-zips) and it compares zip file in following locations: 1) artifacts\apache-royale-0.9.6-src.zip 2) /sources/srczip/apache-royale-0.9.6-src.zip I have changed in that target all places where ${artifactfolder} to ../../${artifactfolder} and launch that

Re: Discuss of release steps preparation

Unfortunately I don't know what is happening but signing trough script hang for me. Stopped working. :( ant -f releasesteps.xml Release_Step_003_Sign -Drelease.version=0.9.6 Buildfile: d:\Work\royale-sources\royale-compiler\releasesteps.xml get-artifact-folder: [input] Enter the temporary

Re: Discuss of release steps preparation

With "../../" or without ? I just run script with -DskiptTests="true" and it passes, but failed on "compare-src-zips" - It looks like it is also problem with paths. :( pt., 16 sie 2019 o 09:15 Alex Harui napisał(a): > I would also need to see the output of the other two steps >

Re: Discuss of release steps preparation

I would also need to see the output of the other two steps (Release_Step_003 and Release_Step_003_Sign) Thanks, -Alex On 8/15/19, 11:14 PM, "Piotr Zarzycki" wrote: This console output is here [1], but it is version where script failing, cause there wasn't "../../". Let me know if

Re: Discuss of release steps preparation

This console output is here [1], but it is version where script failing, cause there wasn't "../../". Let me know if it's enough actually. [1] https://paste.apache.org/zvxoi czw., 15 sie 2019 o 22:37 Alex Harui napisał(a): > That's a possibility. I only used absolute paths. > > Piotr, it

Re: Discuss of release steps preparation

Sorry, that should be plural -DskipTests=true -Alex On 8/15/19, 4:15 PM, "Alex Harui" wrote: Also, try adding -DskipTest=true to skip the mustella tests. On 8/15/19, 1:37 PM, "Alex Harui" wrote: That's a possibility. I only used absolute paths.

Re: Discuss of release steps preparation

Also, try adding -DskipTest=true to skip the mustella tests. On 8/15/19, 1:37 PM, "Alex Harui" wrote: That's a possibility. I only used absolute paths. Piotr, it would nice to see the Windows console output including the paths you gave to help make this process more robust.

Re: Discuss of release steps preparation

That's a possibility. I only used absolute paths. Piotr, it would nice to see the Windows console output including the paths you gave to help make this process more robust. -Alex On 8/15/19, 1:21 PM, "Josh Tynjala" wrote: If it started working correctly after changing the path to

Re: Discuss of release steps preparation

If it started working correctly after changing the path to include ../../, perhaps ${artifactfolder} is being set to a relative path, but the script expects the path to be absolute. I'm not familiar with the release steps yet, so I'm just guessing, but does that make sense? -- Josh Tynjala Bowler

Discuss of release steps preparation

Nope Maven didn't provide such feature or at least I didn't get any questions on console. I was today on a last step which takes lot's of time - build on machine whole framework by ant, but if failed on mustella tests. I will try tomorrow and see whether it happen again. If that very last step

Re: Discuss of release steps preparation

Good to know. When it failed on Windows, did Maven offer command-line options to continue from the point of failure? Unless all future RMs have Macs, we still need to find a way for Windows-only RMs to be successful. -Alex On 8/15/19, 5:12 AM, "Piotr Zarzycki" wrote: Good news. I

Re: Discuss of release steps preparation

If we would use for release process develop it would impossible for me finish that process. I'm volunteer - even if current tasks is being paid job. - It means that I could do first 5 steps first day and in couple of days another 2 steps. If there would be some commit between those days - I will

Re: Discuss of release steps preparation

Good news. I tried today again upload artifacts from my Windows machine - it failed again. I copied my signed artifacts to my Mac machine which is using different internet connection. I'm not sure how it influences all the process but I have uploaded artifacts without any problem. I'm moving

Re: Discuss of release steps preparation

Carlos, In [1] that you referenced it says about release branches: "During that time, bug fixes may be applied in this branch (rather than on the develop branch)." To me, that means that new unstable changes should go into develop, but changes to make the release better should be discussed

Re: Discuss of release steps preparation

On 8/14/19, 1:14 AM, "Piotr Zarzycki" wrote: If your folder with artifacts is in ~/temp/releasesteps - What do you type when script asking you about ? I would type (on a Mac): /Users/aharui/temp/releasesteps There are 3 different Ant targets for Step 003: - Release_Step_003

  1   2   >