I agree with Taher,

We have to keep both framework and plugins separately.

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Sun, Feb 12, 2017 at 6:02 PM, Taher Alkhateeb <[email protected]
> wrote:

> Let's take a look at the big picture for a moment before we decide. We have
> broken OFBiz into essentially two products: framework and plugins.
>
> Why did we break it up? Why did we go through the trouble of creating two
> different repositories? I hope the answer is something like "because it is
> too big" or "because it carried a lot of non-essential functionality
> around"
>
> So breaking up the project brings the advantage of not having to _worry
> about everything_ on each and every commit. These are two projects with two
> release cycles and they don't need to be developed together simultaneously.
> People can specialize and focus on different areas.
>
> The whole idea of breaking the system up and then using gradle's plugin API
> for OFBiz is to remove the coupling between the two projects. If we
> introduce svn externals then all  we achieve is create two repositories
> only to merge them again. Why! that's pointless!
>
> Two products means two buildbot scripts, two releases, two development
> cycles, two different things!
>
> So to achieve true separation and decoupling, I suggest to avoid any hacks
> like svn externals.
>
> On Sun, Feb 12, 2017 at 1:31 PM, Jacques Le Roux <
> [email protected]> wrote:
>
> > Hi All,
> >
> > This discussion already happened at OFBIZ-9182, but only between Taher,
> > Nicolas and I.
> >
> > The question is simple, below reflects it, and the subject summarises it.
> >
> > So what are your thoughts and opinions?
> >
> > Also when answering I guess we can remove  '(was Re: Proposal to create a
> > separate svn repository for the OFBiz official plugins)' from the subject
> > (I was just "lazy" here)
> >
> > Thanks
> >
> > Jacques
> >
> >
> > Le 12/02/2017 à 11:22, Jacques Le Roux a écrit :
> >
> >> Sincerely I hardly see the benefit, but I see the disadvantages when I
> >> remember what happened with R13.07. I mean how and by who will be
> >> maintained the OOTB plugins?
> >>
> >> I think this should be more discussed, and maybe voted, here
> >>
> >> Jacques
> >>
> >>
> >> Le 12/02/2017 à 11:18, Deepak Dixit a écrit :
> >>
> >>> Hi Jacques,
> >>>
> >>> We can add gradle task to  pull all plugins from remote. As we are
> >>> de-coupling plugins from core so I think its good idea to keep them
> >>> separate. If any committer or developer want he can use gradle task for
> >>> the
> >>> same.
> >>>
> >>> Thanks & Regards
> >>> --
> >>> Deepak Dixit
> >>> www.hotwaxsystems.com
> >>>
> >>> On Sun, Feb 12, 2017 at 3:43 PM, Jacques Le Roux <
> >>> [email protected]> wrote:
> >>>
> >>> Yes this is the idea, why should we not? How else committers will
> easily
> >>>> maintain the plugins?
> >>>>
> >>>> Jacques
> >>>>
> >>>>
> >>>> Le 12/02/2017 à 10:25, Deepak Dixit a écrit :
> >>>>
> >>>> Hi Jacques,
> >>>>>
> >>>>> I think if we svn:external on trunk, then it will always checkout the
> >>>>> plugins with trunk
> >>>>>
> >>>>>
> >>>>> Thanks & Regards
> >>>>> --
> >>>>> Deepak Dixit
> >>>>> www.hotwaxsystems.com
> >>>>>
> >>>>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit <
> >>>>> [email protected]> wrote:
> >>>>>
> >>>>
> >
>

Reply via email to