Re: JavaScript Source Maps
Hello Aditya, Jacques, This is a great initiative! NPM is really powerful and is a plethora of packages. NPM has libraries for performing any common task one can think of and It saves a lot of time trying to reinvent the wheel. Furthermore, popular NPM packages are well maintained. Recently I automated the cumbersome task of manually minifying some of the custom JS and CSS files in my client project. I used the respective NPM packages but I was looking for a way to eliminate the requirement to manually install NPM and NodeJS on the system. This Gradle plugin would certainly prove helpful and would enable us to fully leverage the power of NPM. On Tue, Aug 18, 2020 at 10:38 PM Jacques Le Roux < [email protected]> wrote: > Mmm, > > I made all that below because, as a moderator, I before asked for the list > of subscribed emails to [email protected], but the answer was too long. > I just received it and Roque is not in this > list. Would you have a nother email address beginning by "ingeniu" > > Jacques > > Le 18/08/2020 à 17:19, Jacques Le Roux a écrit : > > Hi Roque, > > > > When I did, as you certainly saw, I did it in one only email (source > extract below) > > > >< >To: [email protected], Roque Hernandez , > > [email protected], > > [email protected] > >References: > > > > >From: Jacques Le Roux > > > >Le 18/08/2020 à 15:32, Roque Hernandez a écrit :>> > > > > It was the 1st time I did that (because I wanted to do it for both dev > and user MLs). Maybe it does not work that way :/ > > > > So I sent again 2 separated messages to respectively: > > > > [email protected], > > [email protected] > > > > Please confirm it worked for you. > > > > Also please confirm that you are not receiving emails from Nabble OFBiz > forums[1]. > > If you receive emails from there then you need to unsubscribe there. > > > > Thanks > > > > Jacques > > > > [1] http://ofbiz.135035.n4.nabble.com/ > > > >> Jacques, > >> I am sorry to bother you with something so trivial, but a couple of > weeks > >> ago I sent you an email stating that I wanted to be off the mailing > lists. > >> You replied that I was out, but I still get messages like this one. I > >> appreciate any time you might be able to spend on this and I thank you > >> ahead of time. > >> > >> Best regards > >> > >> Roque > >> > >> On Mon, Aug 17, 2020 at 10:52 AM Jacques Le Roux < > >> [email protected]> wrote: > >> > >>> Good news, thanks Aditya! > >>> > >>> Le 17/08/2020 à 16:53, Aditya Sharma a écrit : > Hi Jacques, everyone, > > I have created OFBIZ-11960[1] in this direction. Initially, I have > kept > >>> it > very simple, JS dependencies will be downloaded through NPM and used > from > the same downloaded path throughout. I will soon create a PR for the > >>> same. > > 1. https://issues.apache.org/jira/browse/OFBIZ-11960 > > Thanks and Regards, > Aditya Sharma > > On Mon, Aug 10, 2020 at 8:14 PM Jacques Le Roux < > [email protected]> wrote: > > > Hi, > > > > I have decided to let down my work at > > https://github.com/JacquesLeRoux/gradle-js-plugin > > > > I have put a sentence about > > https://plugins.gradle.org/plugin/com.github.node-gradle.node in the > > Alert of the wiki page > > > > Jacques > > > > Le 27/07/2020 à 13:07, Jacques Le Roux a écrit : > >> Hi Aditya, > >> > >> Maybe it will be easier to indeed use the node Gradle plugin. > >> > >> Though I'm not much versed in node, then I guess following the > steps I > > put in the alert at > >> https://cwiki.apache.org/confluence/display/OFBIZ/About+retire.js > >> > >> Would be easier? Notably > >> https://github.com/mozilla/source-map > >> > >>> > https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Use_a_source_map > >> Thanks > >> > >> Jacques > >> > >> Le 27/07/2020 à 09:48, Aditya Sharma a écrit : > >>> 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
Re: JavaScript Source Maps
Mmm, I made all that below because, as a moderator, I before asked for the list of subscribed emails to [email protected], but the answer was too long. I just received it and Roque is not in this list. Would you have a nother email address beginning by "ingeniu" Jacques Le 18/08/2020 à 17:19, Jacques Le Roux a écrit : Hi Roque, When I did, as you certainly saw, I did it in one only email (source extract below) <, [email protected], [email protected] References: From: Jacques Le Roux Le 18/08/2020 à 15:32, Roque Hernandez a écrit :>> It was the 1st time I did that (because I wanted to do it for both dev and user MLs). Maybe it does not work that way :/ So I sent again 2 separated messages to respectively: [email protected], [email protected] Please confirm it worked for you. Also please confirm that you are not receiving emails from Nabble OFBiz forums[1]. If you receive emails from there then you need to unsubscribe there. Thanks Jacques [1] http://ofbiz.135035.n4.nabble.com/ Jacques, I am sorry to bother you with something so trivial, but a couple of weeks ago I sent you an email stating that I wanted to be off the mailing lists. You replied that I was out, but I still get messages like this one. I appreciate any time you might be able to spend on this and I thank you ahead of time. Best regards Roque On Mon, Aug 17, 2020 at 10:52 AM Jacques Le Roux < [email protected]> wrote: Good news, thanks Aditya! Le 17/08/2020 à 16:53, Aditya Sharma a écrit : Hi Jacques, everyone, I have created OFBIZ-11960[1] in this direction. Initially, I have kept it very simple, JS dependencies will be downloaded through NPM and used from the same downloaded path throughout. I will soon create a PR for the same. 1. https://issues.apache.org/jira/browse/OFBIZ-11960 Thanks and Regards, Aditya Sharma On Mon, Aug 10, 2020 at 8:14 PM Jacques Le Roux < [email protected]> wrote: Hi, I have decided to let down my work at https://github.com/JacquesLeRoux/gradle-js-plugin I have put a sentence about https://plugins.gradle.org/plugin/com.github.node-gradle.node in the Alert of the wiki page Jacques Le 27/07/2020 à 13:07, Jacques Le Roux a écrit : Hi Aditya, Maybe it will be easier to indeed use the node Gradle plugin. Though I'm not much versed in node, then I guess following the steps I put in the alert at https://cwiki.apache.org/confluence/display/OFBIZ/About+retire.js Would be easier? Notably https://github.com/mozilla/source-map https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Use_a_source_map Thanks Jacques Le 27/07/2020 à 09:48, Aditya Sharma a écrit : 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 < [email protected]> 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: /< 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
Re: JavaScript Source Maps
Hi Roque, When I did, as you certainly saw, I did it in one only email (source extract below) <, [email protected], [email protected] References: From: Jacques Le Roux Le 18/08/2020 à 15:32, Roque Hernandez a écrit :>> It was the 1st time I did that (because I wanted to do it for both dev and user MLs). Maybe it does not work that way :/ So I sent again 2 separated messages to respectively: [email protected], [email protected] Please confirm it worked for you. Also please confirm that you are not receiving emails from Nabble OFBiz forums[1]. If you receive emails from there then you need to unsubscribe there. Thanks Jacques [1] http://ofbiz.135035.n4.nabble.com/ Jacques, I am sorry to bother you with something so trivial, but a couple of weeks ago I sent you an email stating that I wanted to be off the mailing lists. You replied that I was out, but I still get messages like this one. I appreciate any time you might be able to spend on this and I thank you ahead of time. Best regards Roque On Mon, Aug 17, 2020 at 10:52 AM Jacques Le Roux < [email protected]> wrote: Good news, thanks Aditya! Le 17/08/2020 à 16:53, Aditya Sharma a écrit : Hi Jacques, everyone, I have created OFBIZ-11960[1] in this direction. Initially, I have kept it very simple, JS dependencies will be downloaded through NPM and used from the same downloaded path throughout. I will soon create a PR for the same. 1. https://issues.apache.org/jira/browse/OFBIZ-11960 Thanks and Regards, Aditya Sharma On Mon, Aug 10, 2020 at 8:14 PM Jacques Le Roux < [email protected]> wrote: Hi, I have decided to let down my work at https://github.com/JacquesLeRoux/gradle-js-plugin I have put a sentence about https://plugins.gradle.org/plugin/com.github.node-gradle.node in the Alert of the wiki page Jacques Le 27/07/2020 à 13:07, Jacques Le Roux a écrit : Hi Aditya, Maybe it will be easier to indeed use the node Gradle plugin. Though I'm not much versed in node, then I guess following the steps I put in the alert at https://cwiki.apache.org/confluence/display/OFBIZ/About+retire.js Would be easier? Notably https://github.com/mozilla/source-map https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Use_a_source_map Thanks Jacques Le 27/07/2020 à 09:48, Aditya Sharma a écrit : 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 < [email protected]> 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: /< 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
Re: JavaScript Source Maps
Jacques, I am sorry to bother you with something so trivial, but a couple of weeks ago I sent you an email stating that I wanted to be off the mailing lists. You replied that I was out, but I still get messages like this one. I appreciate any time you might be able to spend on this and I thank you ahead of time. Best regards Roque On Mon, Aug 17, 2020 at 10:52 AM Jacques Le Roux < [email protected]> wrote: > Good news, thanks Aditya! > > Le 17/08/2020 à 16:53, Aditya Sharma a écrit : > > Hi Jacques, everyone, > > > > I have created OFBIZ-11960[1] in this direction. Initially, I have kept > it > > very simple, JS dependencies will be downloaded through NPM and used from > > the same downloaded path throughout. I will soon create a PR for the > same. > > > > > > 1. https://issues.apache.org/jira/browse/OFBIZ-11960 > > > > Thanks and Regards, > > Aditya Sharma > > > > On Mon, Aug 10, 2020 at 8:14 PM Jacques Le Roux < > > [email protected]> wrote: > > > >> Hi, > >> > >> I have decided to let down my work at > >> https://github.com/JacquesLeRoux/gradle-js-plugin > >> > >> I have put a sentence about > >> https://plugins.gradle.org/plugin/com.github.node-gradle.node in the > >> Alert of the wiki page > >> > >> Jacques > >> > >> Le 27/07/2020 à 13:07, Jacques Le Roux a écrit : > >>> Hi Aditya, > >>> > >>> Maybe it will be easier to indeed use the node Gradle plugin. > >>> > >>> Though I'm not much versed in node, then I guess following the steps I > >> put in the alert at > >>> https://cwiki.apache.org/confluence/display/OFBIZ/About+retire.js > >>> > >>> Would be easier? Notably > >>> https://github.com/mozilla/source-map > >>> > >> > https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Use_a_source_map > >>> Thanks > >>> > >>> Jacques > >>> > >>> Le 27/07/2020 à 09:48, Aditya Sharma a écrit : > 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 < > [email protected]> 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: > > > > /< >> 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 > > > > >
Re: JavaScript Source Maps
Good news, thanks Aditya! Le 17/08/2020 à 16:53, Aditya Sharma a écrit : Hi Jacques, everyone, I have created OFBIZ-11960[1] in this direction. Initially, I have kept it very simple, JS dependencies will be downloaded through NPM and used from the same downloaded path throughout. I will soon create a PR for the same. 1. https://issues.apache.org/jira/browse/OFBIZ-11960 Thanks and Regards, Aditya Sharma On Mon, Aug 10, 2020 at 8:14 PM Jacques Le Roux < [email protected]> wrote: Hi, I have decided to let down my work at https://github.com/JacquesLeRoux/gradle-js-plugin I have put a sentence about https://plugins.gradle.org/plugin/com.github.node-gradle.node in the Alert of the wiki page Jacques Le 27/07/2020 à 13:07, Jacques Le Roux a écrit : Hi Aditya, Maybe it will be easier to indeed use the node Gradle plugin. Though I'm not much versed in node, then I guess following the steps I put in the alert at https://cwiki.apache.org/confluence/display/OFBIZ/About+retire.js Would be easier? Notably https://github.com/mozilla/source-map https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Use_a_source_map Thanks Jacques Le 27/07/2020 à 09:48, Aditya Sharma a écrit : 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 < [email protected]> 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: /< 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
Re: JavaScript Source Maps
Hi Jacques, everyone, I have created OFBIZ-11960[1] in this direction. Initially, I have kept it very simple, JS dependencies will be downloaded through NPM and used from the same downloaded path throughout. I will soon create a PR for the same. 1. https://issues.apache.org/jira/browse/OFBIZ-11960 Thanks and Regards, Aditya Sharma On Mon, Aug 10, 2020 at 8:14 PM Jacques Le Roux < [email protected]> wrote: > Hi, > > I have decided to let down my work at > https://github.com/JacquesLeRoux/gradle-js-plugin > > I have put a sentence about > https://plugins.gradle.org/plugin/com.github.node-gradle.node in the > Alert of the wiki page > > Jacques > > Le 27/07/2020 à 13:07, Jacques Le Roux a écrit : > > Hi Aditya, > > > > Maybe it will be easier to indeed use the node Gradle plugin. > > > > Though I'm not much versed in node, then I guess following the steps I > put in the alert at > > > > https://cwiki.apache.org/confluence/display/OFBIZ/About+retire.js > > > > Would be easier? Notably > > https://github.com/mozilla/source-map > > > https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Use_a_source_map > > > > Thanks > > > > Jacques > > > > Le 27/07/2020 à 09:48, Aditya Sharma a écrit : > >> 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 < > >> [email protected]> 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: > >>> > >>> /< 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 > >>> > >>> >
Re: JavaScript Source Maps
Hi, I have decided to let down my work at https://github.com/JacquesLeRoux/gradle-js-plugin I have put a sentence about https://plugins.gradle.org/plugin/com.github.node-gradle.node in the Alert of the wiki page Jacques Le 27/07/2020 à 13:07, Jacques Le Roux a écrit : Hi Aditya, Maybe it will be easier to indeed use the node Gradle plugin. Though I'm not much versed in node, then I guess following the steps I put in the alert at https://cwiki.apache.org/confluence/display/OFBIZ/About+retire.js Would be easier? Notably https://github.com/mozilla/source-map https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Use_a_source_map Thanks Jacques Le 27/07/2020 à 09:48, Aditya Sharma a écrit : 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 < [email protected]> 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: /<>/ So that's how people are poorly handling it :/ Jacques
Re: JavaScript Source Maps
Hi Aditya, Maybe it will be easier to indeed use the node Gradle plugin. Though I'm not much versed in node, then I guess following the steps I put in the alert at https://cwiki.apache.org/confluence/display/OFBIZ/About+retire.js Would be easier? Notably https://github.com/mozilla/source-map https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Use_a_source_map Thanks Jacques Le 27/07/2020 à 09:48, Aditya Sharma a écrit : 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 < [email protected]> 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: /<>/ So that's how people are poorly handling it :/ Jacques
Re: JavaScript Source Maps
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 < [email protected]> 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: > > /< 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 > >
Re: JavaScript Source Maps
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: /<>/ So that's how people are poorly handling it :/ Jacques
Re: JavaScript Source Maps
Hi Guys, I have a problem with that. Sorry for the long coming text :) Initially the gradle-js-plugin was created and published as a Gradle plugin by Eric Wendelin at https://github.com/eriwen/gradle-js-plugin. There is also https://github.com/eriwen/gradle-css-plugin 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. My concern is that if you want to publish using the "plugin publishing plugin"[5] you need to use a so called "'group" which is initially "com.eriwen". The Groovy code is "Licensed under the Apache License, Version 2.0" but also "Copyright[ed in] 2012 [by] Eric Wendelin"[6] That would not be a problem I guess, ASL2 should prevail. The concern is about the so called "'group" to publish to (initially "com.eriwen"). Since Eric Wendelin don't care anymore about PRs, it seems he is blocking publishs on "com.eriwen". 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) What I see for other forks is they still use "com.eriwen" in package, eg[7]. So I guess they are not officially published. I'm still unsure I don't miss anything. The JavaScript Source Map is a cool thing when you need to get into other minified libs. I must say I never got blocked by not being able to do that. But I'd have liked to be able to do so few times. 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] I put an alert about that at https://cwiki.apache.org/confluence/display/OFBIZ/About+retire.js My questions are: 1. Should we care about JavaScript source maps (I think we should)? 2. Should we care about gradle-js-plugin? 3. If we don't, is my alert in wiki enough (using js tools is uneasy to me)? Thanks to get to this point ;) Jacques [1] https://dzone.com/articles/javascript-webapps-gradle [2] https://github.com/eriwen/gradle-css-plugin/issues/58 [3] https://github.com/twwwt/gradle-js-plugin [4] https://github.com/tbutter/gradle-js-plugin/ [5] https://plugins.gradle.org/docs/submit [6] https://github.com/eriwen/gradle-js-plugin/blob/master/src/main/groovy/com/eriwen/gradle/js/tasks/CombineJsTask.groovy [7] https://github.com/twwwt/gradle-js-plugin/blob/master/src/main/groovy/com/eriwen/gradle/js/tasks/CombineJsTask.groovy [8] https://github.com/jquery/jquery/issues/4166 Le 24/07/2020 à 15:39, Jacques Le Roux a écrit : Thanks Aditya, It works only with 5.1 mine works with 6.3. I want to publish it as org.apache.ofbiz.gradle-js-plugin or maybe simply org.apache.ofbiz.js-plugin. Still have to complete that (one point is confusing) Jacques Le 24/07/2020 à 13:47, Aditya Sharma a écrit : That's great Jacques. Just for reference, another fork of gradle js plugin which was updated in May 2019. https://plugins.gradle.org/plugin/eu.butter.gradle.js https://github.com/tbutter/gradle-js-plugin/ Thanks and regards, Aditya Sharma On Thu, Jul 23, 2020 at 2:00 PM Jacques Le Roux < [email protected]> wrote: Hi All, Backport done, I have created a fork of gradle-js-plugin and it works with Gradle 6.3. I'll tell you more when I'll get a chance :) Jacques Le 19/07/2020 à 16:08, Jacques Le Roux a écrit : Thanks Aditya, @All, without more answers I'll exceptionally use a lazy consensus to backport changes in minified and add of maps files down to R17 in a week from "16/07/2020 à 15:01" This because, even if the Jiras are registered as improvements and we can't see anything in UI and OFBiz logs, there are 404 and lack of help in browser log. Thanks to Alex for the help! Jacques Le 17/07/2020 à 14:41, Aditya Sharma a écrit : Thank you, Jacques and Alex, for bringing this up. I think source maps can be a great aid for debugging. I am willing to give a hand. Thanks and regards, Aditya Sharma On Thu, Jul 16, 2020 at 8:36 PM Jacques Le Roux < [email protected]> wrote: Le 16/07/2020 à 15:01, Jacques Le Roux a écrit : https://issues.apache.org/jira/issues/?jql=project %3D OFBIZ AND text ~ "map alex" This url is easier to use: https://s.apache.org/xzdtx
Re: JavaScript Source Maps
Thanks Aditya, It works only with 5.1 mine works with 6.3. I want to publish it as org.apache.ofbiz.gradle-js-plugin or maybe simply org.apache.ofbiz.js-plugin. Still have to complete that (one point is confusing) Jacques Le 24/07/2020 à 13:47, Aditya Sharma a écrit : That's great Jacques. Just for reference, another fork of gradle js plugin which was updated in May 2019. https://plugins.gradle.org/plugin/eu.butter.gradle.js https://github.com/tbutter/gradle-js-plugin/ Thanks and regards, Aditya Sharma On Thu, Jul 23, 2020 at 2:00 PM Jacques Le Roux < [email protected]> wrote: Hi All, Backport done, I have created a fork of gradle-js-plugin and it works with Gradle 6.3. I'll tell you more when I'll get a chance :) Jacques Le 19/07/2020 à 16:08, Jacques Le Roux a écrit : Thanks Aditya, @All, without more answers I'll exceptionally use a lazy consensus to backport changes in minified and add of maps files down to R17 in a week from "16/07/2020 à 15:01" This because, even if the Jiras are registered as improvements and we can't see anything in UI and OFBiz logs, there are 404 and lack of help in browser log. Thanks to Alex for the help! Jacques Le 17/07/2020 à 14:41, Aditya Sharma a écrit : Thank you, Jacques and Alex, for bringing this up. I think source maps can be a great aid for debugging. I am willing to give a hand. Thanks and regards, Aditya Sharma On Thu, Jul 16, 2020 at 8:36 PM Jacques Le Roux < [email protected]> wrote: Le 16/07/2020 à 15:01, Jacques Le Roux a écrit : https://issues.apache.org/jira/issues/?jql=project %3D OFBIZ AND text ~ "map alex" This url is easier to use: https://s.apache.org/xzdtx
Re: JavaScript Source Maps
That's great Jacques. Just for reference, another fork of gradle js plugin which was updated in May 2019. https://plugins.gradle.org/plugin/eu.butter.gradle.js https://github.com/tbutter/gradle-js-plugin/ Thanks and regards, Aditya Sharma On Thu, Jul 23, 2020 at 2:00 PM Jacques Le Roux < [email protected]> wrote: > Hi All, > > Backport done, I have created a fork of gradle-js-plugin and it works with > Gradle 6.3. I'll tell you more when I'll get a chance :) > > Jacques > > Le 19/07/2020 à 16:08, Jacques Le Roux a écrit : > > Thanks Aditya, > > > > @All, without more answers I'll exceptionally use a lazy consensus to > backport changes in minified and add of maps files down to R17 in a week > from > > "16/07/2020 à 15:01" > > > > This because, even if the Jiras are registered as improvements and we > can't see anything in UI and OFBiz logs, there are 404 and lack of help in > > browser log. > > > > Thanks to Alex for the help! > > > > Jacques > > > > Le 17/07/2020 à 14:41, Aditya Sharma a écrit : > >> Thank you, Jacques and Alex, for bringing this up. I think source maps > can > >> be a great aid for debugging. I am willing to give a hand. > >> > >> Thanks and regards, > >> Aditya Sharma > >> > >> On Thu, Jul 16, 2020 at 8:36 PM Jacques Le Roux < > >> [email protected]> wrote: > >> > >>> Le 16/07/2020 à 15:01, Jacques Le Roux a écrit : > https://issues.apache.org/jira/issues/?jql=project %3D OFBIZ AND > text ~ > >>> "map alex" > >>> This url is easier to use: https://s.apache.org/xzdtx > >>> > >>> >
Re: JavaScript Source Maps
Hi All, Backport done, I have created a fork of gradle-js-plugin and it works with Gradle 6.3. I'll tell you more when I'll get a chance :) Jacques Le 19/07/2020 à 16:08, Jacques Le Roux a écrit : Thanks Aditya, @All, without more answers I'll exceptionally use a lazy consensus to backport changes in minified and add of maps files down to R17 in a week from "16/07/2020 à 15:01" This because, even if the Jiras are registered as improvements and we can't see anything in UI and OFBiz logs, there are 404 and lack of help in browser log. Thanks to Alex for the help! Jacques Le 17/07/2020 à 14:41, Aditya Sharma a écrit : Thank you, Jacques and Alex, for bringing this up. I think source maps can be a great aid for debugging. I am willing to give a hand. Thanks and regards, Aditya Sharma On Thu, Jul 16, 2020 at 8:36 PM Jacques Le Roux < [email protected]> wrote: Le 16/07/2020 à 15:01, Jacques Le Roux a écrit : https://issues.apache.org/jira/issues/?jql=project %3D OFBIZ AND text ~ "map alex" This url is easier to use: https://s.apache.org/xzdtx
Re: JavaScript Source Maps
Thanks Aditya, @All, without more answers I'll exceptionally use a lazy consensus to backport changes in minified and add of maps files down to R17 in a week from "16/07/2020 à 15:01" This because, even if the Jiras are registered as improvements and we can't see anything in UI and OFBiz logs, there are 404 and lack of help in browser log. Thanks to Alex for the help! Jacques Le 17/07/2020 à 14:41, Aditya Sharma a écrit : Thank you, Jacques and Alex, for bringing this up. I think source maps can be a great aid for debugging. I am willing to give a hand. Thanks and regards, Aditya Sharma On Thu, Jul 16, 2020 at 8:36 PM Jacques Le Roux < [email protected]> wrote: Le 16/07/2020 à 15:01, Jacques Le Roux a écrit : https://issues.apache.org/jira/issues/?jql=project %3D OFBIZ AND text ~ "map alex" This url is easier to use: https://s.apache.org/xzdtx
Re: JavaScript Source Maps
Thank you, Jacques and Alex, for bringing this up. I think source maps can be a great aid for debugging. I am willing to give a hand. Thanks and regards, Aditya Sharma On Thu, Jul 16, 2020 at 8:36 PM Jacques Le Roux < [email protected]> wrote: > Le 16/07/2020 à 15:01, Jacques Le Roux a écrit : > > https://issues.apache.org/jira/issues/?jql=project %3D OFBIZ AND text ~ > "map alex" > This url is easier to use: https://s.apache.org/xzdtx > >
Re: JavaScript Source Maps
Le 16/07/2020 à 15:01, Jacques Le Roux a écrit : https://issues.apache.org/jira/issues/?jql=project %3D OFBIZ AND text ~ "map alex" This url is easier to use: https://s.apache.org/xzdtx
