Hi Yishay, I think that is not triggered by profile, but run by default
during normal build of Jewel. It was not an ideal solution, but iirc I was
not able to get the normal sass compilation to pass through the special
characters from the original source unchanged, so had to add that
post-processing step with token replacement.

I'm not sure what to do about this yet, but I can try to figure it out in
my evening tomorrow night (e.g. maybe from around 10.30am your time
tomorrow). If you want, we can discuss in more detail in Apache Royale
Slack channel around that time.



On Tue, Jun 22, 2021 at 3:33 AM Yishay Weiss <[email protected]> wrote:

> Greg,
>
> Regarding commit 9a76ca5db2d0ed52fe92003a61b93ac89e0c223b in royale-asjs
>
> Can you explain which profiles trigger this?
>
> I think I may be running into
>
> https://code.google.com/archive/p/maven-replacer-plugin/issues/1
>
> Which messes with binary reproducibility for 0.9.8 release.
>
>
>
>
>

Reply via email to