I fully support any endeavour to get to individual repos in Github for each
component in the application and plugin stack. It will increase more choice
for potential adopters and hopefully lead to more contributors.
Our CI tooling is capable enough to inject the code from these repos into
the
Le 06/11/2019 à 19:21, Jacques Le Roux a écrit :
BTW does someone knows if it's possible to have the same relationship between
Fisheye and Jira that we had when using Svn?
I created https://issues.apache.org/jira/browse/INFRA-19471 for that
Jacques
On Sun, Nov 10, 2019 at 4:12 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> Le 07/11/2019 à 11:50, Deepak Dixit a écrit :
> > As per current git repo, How user can only checkout and use ecommerce or
> bi
> > or any single component?
> >
> > It was possible in with svn, but in git we
Hello Jacques, Taher and Michael,
I am realizing that I have overreacted to Jacques question by turning it
into a vague (not that constructive) debate about extension mechanism
for providing plugins.
I think the question of removing push/pull/removePlugin* commands should
be post-poned when (1)
Hello Michael,
Michael Brohl 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
Hello Mathieu,
If you study the plugin system implementation, you will notice that it
is based on maven for dependency resolution, which already takes care
of many of the details you mentioned, especially with respect to
dependency management. The way it is designed avoids reinventing the
wheel
Taher Alkhateeb writes:
> I'm not sure I see this issue with the same perspective. Having the
> build system automatically download (and run some code) for a certain
> component is a convenience especially for the community components.
> Things are even easier when using git as there are many
Hi Taher, All,
I then propose that waiting for another Git solution based, we simply continue
to use Svn through Github :)
Jacques
Le 11/11/2019 à 22:47, Taher Alkhateeb a écrit :
I'm not sure I see this issue with the same perspective. Having the
build system automatically download (and run
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
I'm not sure I see this issue with the same perspective. Having the
build system automatically download (and run some code) for a certain
component is a convenience especially for the community components.
Things are even easier when using git as there are many plugins to
support that. I'm also
Hello,
Jacques Le Roux 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
Hi Gil, Deepak, Mathieu, All,
I propose that waiting for plugins Maven repos we simply continue to use Svn
through Github as I explained elsewhere
Jacques
Le 07/11/2019 à 14:00, Gil Portenseigne a écrit :
Hello Deepak, all,
I do not have a strong opinion about separating plugins into
Le 07/11/2019 à 11:50, Deepak Dixit a écrit :
As per current git repo, How user can only checkout and use ecommerce or bi
or any single component?
It was possible in with svn, but in git we need separate repository
Hi Deepak,
A Github feature[1] allows that. You can do it by checking out
>>How a great deal is that? I mean compared to what we already know about
"framework" dependencies on plugins and related issues. And we certainly
miss
some others...
I am not comparing, we already discussed this at the time of cutting
plugins from framework.
To achieve this right way is to have
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
Le 07/11/2019 à 11:50, Deepak Dixit a écrit :
Agree we may some issues, we need to find out and fix if found.
We have already found several, most are in:
https://issues.apache.org/jira/browse/OFBIZ-3500
https://issues.apache.org/jira/browse/OFBIZ-9322
As per current git repo, How user can
Agree we may some issues, we need to find out and fix if found.
As per current git repo, How user can only checkout and use ecommerce or bi
or any single component?
It was possible in with svn, but in git we need separate repository :)
Thanks & Regards
--
Deepak Dixit
ofbiz.apache.org
On Thu,
Le 07/11/2019 à 08:16, Deepak Dixit a écrit :
For instance, some features in applications are dependent on ecommerce
(maybe some other plugins). And a lot of
data used by applications are in ecommerce, and maybe even other plugins.
I think we already had an effort to remove plugin dependencies
Hi Mathieu,
On Wed, Nov 6, 2019 at 10:58 PM Mathieu Lirzin
wrote:
> Hello Deepak,
>
> Deepak Dixit writes:
>
> > As we moved to from svn to git, so I think now its time to create new git
> > repository for each and indiviaual plugins instead of maintaing single
> > ofbiz-plugins.git
> >
> > It
Hi Jacques,
On Wed, Nov 6, 2019 at 9:38 PM Jacques Le Roux
wrote:
> Le 06/11/2019 à 10:01, Deepak Dixit a écrit :
> > If we create git repo for each plugins definately we have to manage the
> > dependencies and release properly, I am confident that as a community we
> > can manage this
Le 06/11/2019 à 17:08, Jacques Le Roux a écrit :
Le 06/11/2019 à 10:01, Deepak Dixit a écrit :
If we create git repo for each plugins definately we have to manage the
dependencies and release properly, I am confident that as a community we
can manage this thing:)
Hi Deepak,
I'm not sure what
Hello Deepak,
Deepak Dixit writes:
> As we moved to from svn to git, so I think now its time to create new git
> repository for each and indiviaual plugins instead of maintaing single
> ofbiz-plugins.git
>
> It will help to manage the plugin life cycle properly,
> if anyone want to use single
Le 06/11/2019 à 10:01, Deepak Dixit a écrit :
If we create git repo for each plugins definately we have to manage the
dependencies and release properly, I am confident that as a community we
can manage this thing:)
Hi Deepak,
I'm not sure what you mean by that. For instance, some features in
Hi Deepak,
Thanks for bringing this topic.
The idea looks reasonability good to me.
Various Apache projects [1] are following this approach of maintaining the
plugins in separate repository.
Cordova [2] and Maven [3] are good examples of this.
[1] https://github.com/apache?utf8=%E2%9C%93=plugins
Hi All,
As we moved to from svn to git, so I think now its time to create new git
repository for each and indiviaual plugins instead of maintaing single
ofbiz-plugins.git
It will help to manage the plugin life cycle properly,
if anyone want to use single or set of plugins they can easiliy setup
25 matches
Mail list logo
