Re: Adopting the onejar-maven-plugin

2024-05-06 Thread Patrick G. Heck
If you can find Simon and get him to grant an MIT or an unaltered BSD 3 clause license that would be awesome. I think the entire world was less savvy about licensing back in 2004, and his alterations probably didn't seem like a big deal, but now anything not exactly matching a known license is

Re: Adopting the onejar-maven-plugin

2024-05-06 Thread Alexander Kriegisch
Hi Patrick. I cannot comment on whether this issue was moved forward or not, only on this, simply to counter-balance it: > WRT maven plugins. I'm happy for them to exist, and would certainly > endeavor not to break them, but I'm not a fan of maven and use it only > when forced to (I went

Re: Adopting the onejar-maven-plugin

2024-05-05 Thread Patrick G. Heck
Hi, I'm the maintainer of UnoJar. I just happened to notice this conversation when it came up in a search. I'm curious what your result was. WRT maven plugins. I'm happy for them to exist, and would certainly endeavor not to break them, but I'm not a fan of maven and use it only when forced

Re: Adopting the onejar-maven-plugin

2022-01-30 Thread Hervé Boutemy
UnoJar is the place: the only drawback is that it kept the unusual license, unusual but permissive, then with a good maintainer, it's ok for the associated Maven, there is a GPL one outside Le dim. 30 janv. 2022 à 15:55, Jochen Wiedmann a écrit : > On Sat, Jan 29, 2022 at 4:01 AM Alexander

Re: Adopting the onejar-maven-plugin

2022-01-30 Thread Jochen Wiedmann
On Sat, Jan 29, 2022 at 4:01 AM Alexander Kriegisch wrote: > > As there was no recent development, I asked the plugin author whether > > he would be willing to donate it to mojohaus. And yes, he would do so. > > He would also change the License to Apache v2.0 for us. > > So what is the problem,

Re: Adopting the onejar-maven-plugin

2022-01-30 Thread Hervé Boutemy
IIUC: - the core OneJar comes from Simon with his specific license http://one-jar.sourceforge.net/index.php?page=documents=license that is quite permissive - Simon seems to be unresponsive to any update or contribution = this is the main issue with OneJar, because there was no update in 10 years -

Re: Adopting the onejar-maven-plugin

2022-01-28 Thread Alexander Kriegisch
Ben said in his original message: > As there was no recent development, I asked the plugin author whether > he would be willing to donate it to mojohaus. And yes, he would do so. > He would also change the License to Apache v2.0 for us. So what is the problem, really? -- Alexander Kriegisch

Re: Adopting the onejar-maven-plugin

2022-01-28 Thread Jochen Wiedmann
On Fri, Jan 28, 2022 at 8:18 AM Hervé Boutemy wrote: > > notice that there is UnoJar that already did the work of cleanly forking > OneJar and maintain it: > https://github.com/nsoft/uno-jar Thanks for the hint, Hervé. Reading through the license (and, consequently, through the original

Re: Adopting the onejar-maven-plugin

2022-01-27 Thread Hervé Boutemy
notice that there is UnoJar that already did the work of cleanly forking OneJar and maintain it: https://github.com/nsoft/uno-jar and it seems there is a Maven plugin listed in its README Le ven. 28 janv. 2022 à 05:41, Alexander Kriegisch a écrit : > My two cents, because I like to use this

Re: Adopting the onejar-maven-plugin

2022-01-27 Thread Alexander Kriegisch
My two cents, because I like to use this plugin for easily creating executable JARs for my AspectJ applications: I agree that not just the Maven plugin but also OneJAR itself ought to be maintained together. Whether it is OK for Mojohaus to maintain them as two modules of the same project, is up

Re: Adopting the onejar-maven-plugin

2022-01-27 Thread Hervé Boutemy
IIUC, it's not a question of site but source code: onejar-maven-plugin imports one-jar-boot as binary jar https://github.com/jolira/onejar-maven-plugin/tree/master/src/main/resources maintaining the plugin is nice, but we also need to have a maintained one-jar-boot, given it seems unmaintained

Re: Adopting the onejar-maven-plugin

2022-01-27 Thread Jochen Wiedmann
On Thu, Jan 27, 2022 at 11:44 AM Benjamin Marwell wrote: > We would host the usage on gh-pages like all other plugins. > Or do you speak of another site? No, I mean the same site. I am simply suggesting, that in this case we would host not only the plugin, but also it's main dependency. (If

Re: Adopting the onejar-maven-plugin

2022-01-27 Thread Benjamin Marwell
Which site? We would host the usage on gh-pages like all other plugins. Or do you speak of another site? jochen@gmail.com schrieb am Donnerstag, 27. Januar 2022 um 09:07:51 UTC+1: > On Thu, Jan 27, 2022 at 8:54 AM Ben M. wrote: > > > The advantage would be that we have everything compiled

Re: Adopting the onejar-maven-plugin

2022-01-27 Thread Jochen Wiedmann
On Thu, Jan 27, 2022 at 8:54 AM Ben M. wrote: > The advantage would be that we have everything compiled every time. That seems to be desirable to me. On the other hand, it would only work, if Simon would agree to maintain this site, rather than his Sourceforge repository. Jochen -- You

Re: Adopting the onejar-maven-plugin

2022-01-26 Thread Jochen Wiedmann
In this particular case, I'd hope that we can keep the sources of onejar itself, and the Maven plugin in a shared repository. Jochen On Wed, Jan 26, 2022 at 8:34 PM Ben M. wrote: > > Hello everyone, > > probably everyone of us has heard of or used the onejar-maven-plugin. > Due to some design

Adopting the onejar-maven-plugin

2022-01-26 Thread Ben M.
Hello everyone, probably everyone of us has heard of or used the onejar-maven-plugin. Due to some design decisions of the spring-boot-maven-plugin I use it every now and then. As there was no recent development, I asked the plugin author whether he would be willing to donate it to mojohaus.