New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error compiling assets: MALFORMED #93
Comments
Thats very weird the line number is just asking the jarFile for entries() and iterating. no more to that stack trace ? |
My team is seeing the same sporadic failure with asset-pipeline plugin 2.11.5 and Gradle 3.1. We also see one other random exception at the same line:
When this happens to us, In our case we have a fairly large multi-project build, with one child project which makes use of the asset-pipeline plugin; this one child project depends on a number of upstream projects. I haven't actually been able to reproduce the failure myself, but one potential cause I've been speculating about is changes to upstream project jar files in parallel to the assetCompile task execution. I've tried to deliberately introduce this type of change while the build was executing, though, and everything kept working. It seems like all the task dependencies are registered properly, so this might be a false lead. I'll be upgrading to 2.11.6 next, but I don't really think this will help us since we've only got a single subproject that uses this plugin. |
+1 |
this may be resolved in 2.12.x |
We've been having occasional trouble compiling assets under Grails, the process fails with the following stacktrace (I'm leaving out the Gradle part):
This error randomly starts showing up on certain developer machines and on our Teamcity build server. Deleting the
build
folder doesn't help, what usually does do the trick is to upgrade/downgrade the asset pipeline version (we're currently atasset-pipeline:3.2.1
andasset-pipeline-gradle:2.8.2
) - this helps for a while, I've just downgraded toasset-pipeline-gradle:2.8.1
so I could deploy the app. And if I switch right back to2.8.2
it works again! Since changing the version of the plugin helps I've tried running Gradle with--refresh-dependencies
but that doesn't make it work.Since the error occurs inside
JarAssetResolver
, happens randomly and is helped by changing the dependencies, perhaps the bug is triggered by JARs being processed in a specific order? Also, the errors began a month or so after our first Windows developer started working on the project (Linux developers only before that) - probably unrelated, but who knows..I'm assuming this is a Gradle issue so I'm posting the report to the pipeline core tracker, but can move to the Grails plugin one.
We're using Gradle 2.9, Java 8 and Grails 3.1.6
The text was updated successfully, but these errors were encountered: