Benoit Sautel

Changing the repository URL is indeed not enough. You have to use a custom repository (not just the URL but the whole configuration). I don't know very well this part...

Ok, I see what you mean. It's not very elegant, that's clear, but does it work as expected now? I don't know enough how repository works to explain why the...

Could you give us the error you get with the VariantBuilder? In the future version, we rewrote completely the code to Kotlin and the VariantBuilder no longer exists. Maybe this...

This happens because the inputs and outputs of the tasks are not configured correctly. If it was the case, those tasks would run only if needed. First, I advice you...

Ok, you will also get this error with the new version because this code still exists. But it is only here to support very old versions of Node.js that are...

I just come to fix #100. So in the next version you will be able to do it without having this error in the VariantBuilder (we no longer parse the...

The project I am working on contains about 70 000 files (according to the comment in your command above). The up-to-date check is really fast on my laptop (less than...

I don't use Windows, it is probably the reason why I don't get this behavior. As far as I understand, you suggest to disable the up-to-date detection. This will cause...

@anuraaga which version of the plugin do you use? The version 2.2.0 introduced a big performance drop due to up-to-date checking which is due to the fact we now declare...

Personnally, I use a different approach to do that. I make a jar including the webapp in its resources and I add an `implementation` dependency to this jar to get...