Closed erichelgeson closed 6 years ago
Hi, There was a similar issue reported here which was closed, from the comment on close looks like not a proper response. Anything can be done to resolve this issue? https://github.com/bertramdev/asset-pipeline/issues/101
Seems to be related to the ExecutorService not capturing the Exceptions… looking into it
On Mar 21, 2018, at 6:27 AM, makfair notifications@github.com wrote:
Hi, There was a similar issue reported here which was closed, from the comment on close looks like not a proper response. Anything can be done to resolve this issue?
101 https://github.com/bertramdev/asset-pipeline/issues/101
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bertramdev/asset-pipeline/issues/196#issuecomment-374906411, or mute the thread https://github.com/notifications/unsubscribe-auth/AABaEnWBuL9cmRcrePaMgygW5Mtjd5DDks5tgjkbgaJpZM4SaTS7.
Fixed in soon to be released 3.0.2
Hi, does anyone know about this issue? 3.0.6 don't break the build if assetCompile have errors
asset-pipeline should fail the build if
:assetCompile
has an error.For example I accidentally used a ES6 feature in ES5 mode. It produced an empty file but did not fail the build so it went unnoticed.
Grails 3.3.x AP 2.14.6