RE: Royale Compiler Build Tools Release Step 002 Succeeded

2020-04-13 Thread Yishay Weiss
got time. Thanks! [1] C:\temp7\artifacts\archive\ [2] C:\temp7\sources\target From: Christofer Dutz<mailto:christofer.d...@c-ware.de> Sent: Monday, April 13, 2020 2:55 PM To: dev@royale.apache.org<mailto:dev@royale.apache.org> Subject: Re: Royale Compiler Build Tools Release Step 002 S

Re: Royale Compiler Build Tools Release Step 002 Succeeded

2020-04-13 Thread Christofer Dutz
Hi Yishay, ok ... we never talked about comparing the JavaDocs ... just the binary artifacts. I updated the maven-javadoc-plugin to 3.2.0 which is the first reproducible version. Please feel free to merge the PRs (I also disabled the Javadoc in the typedefs as this doesn't make any sense there

RE: Royale Compiler Build Tools Release Step 002 Succeeded

2020-04-13 Thread Yishay Weiss
>2. Validate that the compiled artifacts match the downloaded artifacts. What does this mean? Looks to me like the jars are different [1]. I’ll see if I understand why. [1] C:\temp1>git diff C:\temp1\artifacts\archive\compiler-build-tools\target\local-release-dir\org\apache\royale\compiler\com