Mathieu,why using strong words and disrespect other community people's work like this? This does not help in any way making things better.
Having said this, to the topic: users often have difficulties even to get OFBiz running while it seams easiest for us developers. Just read the users list for reference.
Having everything available and be done automatically helps people to get things running easier. By removing these features we would make things more complicated for them.
More advanced people who are familiar with the mentioned techniques can use them anyway.
Regards, Michael Am 11.11.19 um 20:37 schrieb Mathieu Lirzin:
Hello, Jacques Le Roux <[email protected]> writes:I propose that waiting for plugins Maven repos we simply continue to use Svn through Github as I explained elsewhereNo need to wait for Maven plugins before acting responsibly. :-) A preferable solution would be to simply remove the ‘push/pull/removePlugin*’ stuff from our build system which is the reason why we are discussing keeping this “Github SVN” hack initially. IMO people can manage their plugins more conveniently by directly running the “installation” command of their choice ‘git clone’, ‘svn checkout’, ‘ln -s’, ... in their plugins directory without needing OFBiz build system to do it poorly for them.Le 07/11/2019 à 14:00, Gil Portenseigne a écrit :Hello Deepak, all, I do not have a strong opinion about separating plugins into independent git repositories but here are my thought : Plugins integration in OFBiz is intended to be used with a maven repository that hosts the plugin releases for the users. See as a reference the ‘OFBiz Plugins tasks’ or README.adoc about ‘OFBiz plugin system’. We did not implemented an official maven repository for plugin releases, so there is no simple way to install a plugin without using VCS. There might be tasks to be done to have an nice answer to how an user can install a sole plugin from a downloaded release archive.
smime.p7s
Description: S/MIME Cryptographic Signature
