Hello Michael,

Michael Brohl <michael.br...@ecomify.de> writes:

> why using strong words and disrespect other community people's work
> like this? This does not help in any way making things better.

If I showed disrespect to people in that community I am sorry about
that, that was not intended. I was just trying to tell that we might be
better off providing those package management commands that are lacking
important features, are troublesome to maintain.

> 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.

This is true when things works reliably. But when things fails (which is
expected with tinkered tools) it is worse for users who are then
helpless because of the added complexity, when instead we could have
just expect them to know how to download a repository and place it in
particular directory which is not a hard requirement IMO.

> More advanced people who are familiar with the mentioned techniques
> can use them anyway.

In the case of plugin management, I claim that we can make things easier
for everyone (developpers, users) by adopting well known Jar
distribution mechanism to manage both the framework and the plugins
installation (but that is ongoing work [1]).

[1] https://issues.apache.org/jira/browse/OFBIZ-11161

>
> Regards,
>
> Michael
>
> Am 11.11.19 um 20:37 schrieb Mathieu Lirzin:
>> Hello,
>>
>> Jacques Le Roux <jacques.le.r...@les7arts.com> writes:
>>
>>> I propose that waiting for plugins Maven repos we simply continue to
>>> use Svn through Github as I explained elsewhere
>> No 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.
>>>>
>

-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

Reply via email to