Build failed in Jenkins: royale-asjs_jsonly #3460

See Changes: [piotrzarzycki21] Move RoyaleUnit to main build -- [...truncated 475.75 KB...] download-dependency: [echo] basedir is

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.,

Jenkins build is back to normal : royale-asjs_jsonly #3458

See

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

New apache-royale questions for Aug 26 - Stack Exchange

***1 new question in [ApacheRoyale Tag Notifications filter]() on stackexchange.com*** [Apache royale module is not working .not prompt a module

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

Jenkins build is back to normal : royale-asjs_MXTests #1089

See

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