This is an automated email from the ASF dual-hosted git repository.

yishayw pushed a commit to branch release/0.9.8
in repository https://gitbox.apache.org/repos/asf/royale-asjs.git


The following commit(s) were added to refs/heads/release/0.9.8 by this push:
     new ee456f7  Work around sass -> css validation issue on windows - needs 
further investigation.
ee456f7 is described below

commit ee456f7e7dafc0146a788262cf98405f3b4e3c38
Author: Yishay Weiss <[email protected]>
AuthorDate: Thu Jun 24 08:26:20 2021 +0300

    Work around sass -> css validation issue on windows - needs further 
investigation.
---
 releasesteps.xml | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/releasesteps.xml b/releasesteps.xml
index afdcd8e..1475f14 100644
--- a/releasesteps.xml
+++ b/releasesteps.xml
@@ -192,7 +192,11 @@
         <unzip 
src="${artifactfolder}/artifacts/archive/target/local-release-dir/org/apache/royale/framework/royale-framework-parent/${release.version}/royale-framework-parent-${release.version}-source-release.zip"
 dest="${artifactfolder}/sources" >
             <cutdirsmapper dirs="1" />
         </unzip>
-        
+       <!-- Maven release plugin causes Jewel's defaults.css to go wrong and 
this seems to fix it ( at least on windows ) TODO change Step 11 on CI so this 
does not need to be applied -->
+       <!-- Although changing sass files' line endings to dos at this stage 
seems to fix this, I have not seen CRLF endings on the CI server's files, so I 
am not sure why this works. Needs further investigation. Yishay -->
+        <fixcrlf srcdir="${artifactfolder}/sources/frameworks/projects/Jewel" 
eol="dos" fixlast="false">
+               <include name="**/*.sass"/>
+        </fixcrlf>
         <!-- build these modules -->
         <exec executable="${mvn}" dir="${artifactfolder}/sources" 
failonerror="true" >
             <arg value="-X" />

Reply via email to