Hi Jacques, We should definitely care about JavaScript source maps as it is a great addon to debugging.
I think gradle-js-plugin is indeed a great tool but due to a dead community, it always made me reluctant to use it. Thanks for your efforts towards its update. I still want to understand how it will be further maintained. As I get some time I will try to come up with some solution using the requirejs, node, etc to ease these things. https://plugins.gradle.org/plugin/com.github.node-gradle.node >> So I want to change it to "org.apache.ofbiz" to be able to publish. I guess I also need to change the package names (not yet sure about that) I think we will only have to change the id I guess and we have the option to configure the implementationClass https://guides.gradle.org/publishing-plugins-to-gradle-plugin-portal/#configure_the_plugin_publishing_plugin >>Now we also know (thanks to Suraj) that "We will get source map URL in most of the libraries except jQuery, we will have to manually add it"[8] Aditya :D Thanks and regards, Aditya Sharma On Sun, Jul 26, 2020 at 8:48 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Le 26/07/2020 à 11:44, Jacques Le Roux a écrit : > > There was a good old time when this was available[1]. But with Gradle > upgrades these plugins were slowly abandoned by their creator, eg[2] > > > > Some forks where done, eg[3][4]. Seems that their creators could not get > PRs merged. So I don't know how/if they are published and used. > > I somehow actually answered to myself with > > > [2] https://github.com/eriwen/gradle-css-plugin/issues/58 > > I read it there and forgot: > > /<<If you try to use the plugin with Gradle 6 just by declaring it in > the plugin block it will not work.// > //The change is actually fixed in master but without a release > everyone is forced to manually build the plugin by himself and import the > jar the > classpath.//>>/ > > So that's how people are poorly handling it :/ > > Jacques > >
