Proposal to create a separate svn repository for the OFBiz official plugins

[taher]

Hello Folks

This is a proposal to the community to restructure our SVN repository.
We do this by separating "official" plugins from the core OFBiz
framework and to provide build script tasks to easily download and
install these plugins. The details of this proposal are as follows:

1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches
and tags underneath as is)
2- Create a new tree under
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house all plugins
3- Remove /plugins/component-load.xml (any component in /plugins will
load automatically if it is enabled in ofbiz-component.xml)
4- Create a gradle task with the below syntax. This task downloads a
plugin from subversion and places it in /plugins and runs any install
logic that it may have
   Syntax: pullPluginSource -PpluginId=<plugin-id-here>
   Example: pullPluginSource -PpluginId=birt
5- Refactor the build scripts to cater for all the above
6- Update README.md to reflect all the above

So for example, under this proposal, trunk is located in:
http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk

And the birt component is located in:
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt

This would allow us to have in the future the ability to provide
releases not only for the framework but the plugins as well as two
separate products.

What do you think?

Cheers,

Taher Alkhateeb

[Jacopo Cappellato-5]

I agree with the svn layout that Taher is proposing which is also inline
with what other Apache projects are doing (see for example [*]).
The idea behind these layouts is that the top level folder is for the
"project" and its subfolders are for the project's products:
project/product1
project/product2
...
that for OFBiz would be (as already mentioned by Taher):
ofbiz/ofbiz
ofbiz/ofbiz-plugins
ofbiz/site
...
Each of the above folders may contain the "trunk", "tags" and "branches"
folders.
In fact it is worth to mention that each Apache project can publish more
than one product (and in fact several do); the OFBiz project doesn't
currently but it is better to have a layout that will allow us to produce
more than one product.

Thank you,

Jacopo

[*] http://svn.apache.org/repos/asf/lucene/


On Wed, Jan 11, 2017 at 4:01 PM, Taher Alkhateeb <[hidden email]
> wrote:

> Hello Folks
>
> This is a proposal to the community to restructure our SVN repository. We
> do this by separating "official" plugins from the core OFBiz framework and
> to provide build script tasks to easily download and install these plugins.
> The details of this proposal are as follows:
>
> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches and
> tags underneath as is)
> 2- Create a new tree under http://svn.apache.org/repos/as
> f/ofbiz/ofbiz-plugins to house all plugins
> 3- Remove /plugins/component-load.xml (any component in /plugins will load
> automatically if it is enabled in ofbiz-component.xml)
> 4- Create a gradle task with the below syntax. This task downloads a
> plugin from subversion and places it in /plugins and runs any install logic
> that it may have
>   Syntax: pullPluginSource -PpluginId=<plugin-id-here>
>   Example: pullPluginSource -PpluginId=birt
> 5- Refactor the build scripts to cater for all the above
> 6- Update README.md to reflect all the above
>
> So for example, under this proposal, trunk is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
>
> And the birt component is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
>
> This would allow us to have in the future the ability to provide releases
> not only for the framework but the plugins as well as two separate products.
>
> What do you think?
>
> Cheers,
>
> Taher Alkhateeb
>
>

[Pierre Smits]

We could also consider to have for each component a separate ASF git repo
that replicates to external repo structures like GitHub. This would
increase exposure and potentially attract more contributors as subject
matter experts.

Best regards,

Pierre Smits

ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Wed, Jan 11, 2017 at 4:54 PM, Jacopo Cappellato <
[hidden email]> wrote:

> I agree with the svn layout that Taher is proposing which is also inline
> with what other Apache projects are doing (see for example [*]).
> The idea behind these layouts is that the top level folder is for the
> "project" and its subfolders are for the project's products:
> project/product1
> project/product2
> ...
> that for OFBiz would be (as already mentioned by Taher):
> ofbiz/ofbiz
> ofbiz/ofbiz-plugins
> ofbiz/site
> ...
> Each of the above folders may contain the "trunk", "tags" and "branches"
> folders.
> In fact it is worth to mention that each Apache project can publish more
> than one product (and in fact several do); the OFBiz project doesn't
> currently but it is better to have a layout that will allow us to produce
> more than one product.
>
> Thank you,
>
> Jacopo
>
> [*] http://svn.apache.org/repos/asf/lucene/
>
>
> On Wed, Jan 11, 2017 at 4:01 PM, Taher Alkhateeb <
> [hidden email]
> > wrote:
>
> > Hello Folks
> >
> > This is a proposal to the community to restructure our SVN repository. We
> > do this by separating "official" plugins from the core OFBiz framework
> and
> > to provide build script tasks to easily download and install these
> plugins.
> > The details of this proposal are as follows:
> >
> > 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches
> and
> > tags underneath as is)
> > 2- Create a new tree under http://svn.apache.org/repos/as
> > f/ofbiz/ofbiz-plugins to house all plugins
> > 3- Remove /plugins/component-load.xml (any component in /plugins will
> load
> > automatically if it is enabled in ofbiz-component.xml)
> > 4- Create a gradle task with the below syntax. This task downloads a
> > plugin from subversion and places it in /plugins and runs any install
> logic
> > that it may have
> >   Syntax: pullPluginSource -PpluginId=<plugin-id-here>
> >   Example: pullPluginSource -PpluginId=birt
> > 5- Refactor the build scripts to cater for all the above
> > 6- Update README.md to reflect all the above
> >
> > So for example, under this proposal, trunk is located in:
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
> >
> > And the birt component is located in:
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
> >
> > This would allow us to have in the future the ability to provide releases
> > not only for the framework but the plugins as well as two separate
> products.
> >
> > What do you think?
> >
> > Cheers,
> >
> > Taher Alkhateeb
> >
> >
>

[Shi Jinghai-3]

+1 to the svn folder structure.

On the plugin publish and install, could we consider publish a zip file to maven repository as well as the jars? In production environment, unzip the zip file under plugins and then it can work, or even better, don't unzip it, let it work similar to an android apk file.


-----邮件原件-----
发件人: Taher Alkhateeb [mailto:[hidden email]]
发送时间: 2017年1月11日 23:02
收件人: [hidden email]
主题: Proposal to create a separate svn repository for the OFBiz official plugins

Hello Folks

This is a proposal to the community to restructure our SVN repository.
We do this by separating "official" plugins from the core OFBiz framework and to provide build script tasks to easily download and install these plugins. The details of this proposal are as follows:

1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches and tags underneath as is)
2- Create a new tree under
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house all plugins
3- Remove /plugins/component-load.xml (any component in /plugins will load automatically if it is enabled in ofbiz-component.xml)
4- Create a gradle task with the below syntax. This task downloads a plugin from subversion and places it in /plugins and runs any install logic that it may have
   Syntax: pullPluginSource -PpluginId=<plugin-id-here>
   Example: pullPluginSource -PpluginId=birt
5- Refactor the build scripts to cater for all the above
6- Update README.md to reflect all the above

So for example, under this proposal, trunk is located in:
http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk

And the birt component is located in:
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt

This would allow us to have in the future the ability to provide releases not only for the framework but the plugins as well as two separate products.

What do you think?

Cheers,

Taher Alkhateeb

[Deepak Dixit-3]

+1 for the svn folder structure.

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

On Thu, Jan 12, 2017 at 6:31 AM, Shi Jinghai <[hidden email]> wrote:

> +1 to the svn folder structure.
>
> On the plugin publish and install, could we consider publish a zip file to
> maven repository as well as the jars? In production environment, unzip the
> zip file under plugins and then it can work, or even better, don't unzip
> it, let it work similar to an android apk file.
>
>
> -----邮件原件-----
> 发件人: Taher Alkhateeb [mailto:[hidden email]]
> 发送时间: 2017年1月11日 23:02
> 收件人: [hidden email]
> 主题: Proposal to create a separate svn repository for the OFBiz official
> plugins
>
> Hello Folks
>
> This is a proposal to the community to restructure our SVN repository.
> We do this by separating "official" plugins from the core OFBiz framework
> and to provide build script tasks to easily download and install these
> plugins. The details of this proposal are as follows:
>
> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches and
> tags underneath as is)
> 2- Create a new tree under
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house all plugins
> 3- Remove /plugins/component-load.xml (any component in /plugins will load
> automatically if it is enabled in ofbiz-component.xml)
> 4- Create a gradle task with the below syntax. This task downloads a
> plugin from subversion and places it in /plugins and runs any install logic
> that it may have
>    Syntax: pullPluginSource -PpluginId=<plugin-id-here>
>    Example: pullPluginSource -PpluginId=birt
> 5- Refactor the build scripts to cater for all the above
> 6- Update README.md to reflect all the above
>
> So for example, under this proposal, trunk is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
>
> And the birt component is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
>
> This would allow us to have in the future the ability to provide releases
> not only for the framework but the plugins as well as two separate products.
>
> What do you think?
>
> Cheers,
>
> Taher Alkhateeb
>
>

[Gavin Mabie-2]

+1 Like it
Gavin

On Thu, Jan 12, 2017 at 7:00 AM, Deepak Dixit <
[hidden email]> wrote:

> +1 for the svn folder structure.
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
>
> On Thu, Jan 12, 2017 at 6:31 AM, Shi Jinghai <[hidden email]> wrote:
>
> > +1 to the svn folder structure.
> >
> > On the plugin publish and install, could we consider publish a zip file
> to
> > maven repository as well as the jars? In production environment, unzip
> the
> > zip file under plugins and then it can work, or even better, don't unzip
> > it, let it work similar to an android apk file.
> >
> >
> > -----邮件原件-----
> > 发件人: Taher Alkhateeb [mailto:[hidden email]]
> > 发送时间: 2017年1月11日 23:02
> > 收件人: [hidden email]
> > 主题: Proposal to create a separate svn repository for the OFBiz official
> > plugins
> >
> > Hello Folks
> >
> > This is a proposal to the community to restructure our SVN repository.
> > We do this by separating "official" plugins from the core OFBiz framework
> > and to provide build script tasks to easily download and install these
> > plugins. The details of this proposal are as follows:
> >
> > 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches
> and
> > tags underneath as is)
> > 2- Create a new tree under
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house all plugins
> > 3- Remove /plugins/component-load.xml (any component in /plugins will
> load
> > automatically if it is enabled in ofbiz-component.xml)
> > 4- Create a gradle task with the below syntax. This task downloads a
> > plugin from subversion and places it in /plugins and runs any install
> logic
> > that it may have
> >    Syntax: pullPluginSource -PpluginId=<plugin-id-here>
> >    Example: pullPluginSource -PpluginId=birt
> > 5- Refactor the build scripts to cater for all the above
> > 6- Update README.md to reflect all the above
> >
> > So for example, under this proposal, trunk is located in:
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
> >
> > And the birt component is located in:
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
> >
> > This would allow us to have in the future the ability to provide releases
> > not only for the framework but the plugins as well as two separate
> products.
> >
> > What do you think?
> >
> > Cheers,
> >
> > Taher Alkhateeb
> >
> >
>

[Arun Patidar-2]

+1 for directory structure and OFBiz plugin management.

--
Thanks & Regards
---
Arun Patidar
Manager,Enterprise Software Development
HotWax Mediawww.hotwaxsystems.com


On Thu, Jan 12, 2017 at 10:34 AM, Gavin Mabie <[hidden email]> wrote:

> +1 Like it
> Gavin
>
> On Thu, Jan 12, 2017 at 7:00 AM, Deepak Dixit <
> [hidden email]> wrote:
>
> > +1 for the svn folder structure.
> >
> > Thanks & Regards
> > --
> > Deepak Dixit
> > www.hotwaxsystems.com
> >
> > On Thu, Jan 12, 2017 at 6:31 AM, Shi Jinghai <[hidden email]>
> wrote:
> >
> > > +1 to the svn folder structure.
> > >
> > > On the plugin publish and install, could we consider publish a zip file
> > to
> > > maven repository as well as the jars? In production environment, unzip
> > the
> > > zip file under plugins and then it can work, or even better, don't
> unzip
> > > it, let it work similar to an android apk file.
> > >
> > >
> > > -----邮件原件-----
> > > 发件人: Taher Alkhateeb [mailto:[hidden email]]
> > > 发送时间: 2017年1月11日 23:02
> > > 收件人: [hidden email]
> > > 主题: Proposal to create a separate svn repository for the OFBiz official
> > > plugins
> > >
> > > Hello Folks
> > >
> > > This is a proposal to the community to restructure our SVN repository.
> > > We do this by separating "official" plugins from the core OFBiz
> framework
> > > and to provide build script tasks to easily download and install these
> > > plugins. The details of this proposal are as follows:
> > >
> > > 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> > > http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches
> > and
> > > tags underneath as is)
> > > 2- Create a new tree under
> > > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house all
> plugins
> > > 3- Remove /plugins/component-load.xml (any component in /plugins will
> > load
> > > automatically if it is enabled in ofbiz-component.xml)
> > > 4- Create a gradle task with the below syntax. This task downloads a
> > > plugin from subversion and places it in /plugins and runs any install
> > logic
> > > that it may have
> > >    Syntax: pullPluginSource -PpluginId=<plugin-id-here>
> > >    Example: pullPluginSource -PpluginId=birt
> > > 5- Refactor the build scripts to cater for all the above
> > > 6- Update README.md to reflect all the above
> > >
> > > So for example, under this proposal, trunk is located in:
> > > http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
> > >
> > > And the birt component is located in:
> > > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
> > >
> > > This would allow us to have in the future the ability to provide
> releases
> > > not only for the framework but the plugins as well as two separate
> > products.
> > >
> > > What do you think?
> > >
> > > Cheers,
> > >
> > > Taher Alkhateeb
> > >
> > >
> >
>

[Pranay Pandey-3]

+1 for the proposal from Taher.

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Wed, Jan 11, 2017 at 8:31 PM, Taher Alkhateeb <[hidden email]
> wrote:

> Hello Folks
>
> This is a proposal to the community to restructure our SVN repository. We
> do this by separating "official" plugins from the core OFBiz framework and
> to provide build script tasks to easily download and install these plugins.
> The details of this proposal are as follows:
>
> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches and
> tags underneath as is)
> 2- Create a new tree under http://svn.apache.org/repos/as
> f/ofbiz/ofbiz-plugins to house all plugins
> 3- Remove /plugins/component-load.xml (any component in /plugins will load
> automatically if it is enabled in ofbiz-component.xml)
> 4- Create a gradle task with the below syntax. This task downloads a
> plugin from subversion and places it in /plugins and runs any install logic
> that it may have
>   Syntax: pullPluginSource -PpluginId=<plugin-id-here>
>   Example: pullPluginSource -PpluginId=birt
> 5- Refactor the build scripts to cater for all the above
> 6- Update README.md to reflect all the above
>
> So for example, under this proposal, trunk is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
>
> And the birt component is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
>
> This would allow us to have in the future the ability to provide releases
> not only for the framework but the plugins as well as two separate products.
>
> What do you think?
>
> Cheers,
>
> Taher Alkhateeb
>
>

[Jacopo Cappellato-5]

On Wed, Jan 11, 2017 at 6:54 PM, Pierre Smits <[hidden email]>
wrote:

> We could also consider to have for each component a separate ASF git repo
> that replicates to external repo structures like GitHub.


Agreed. it would be a natural consequence of the new layout and we should
definitely request this to the Infra.

Jacopo

[Pranay Pandey-3]

On Wed, Jan 11, 2017 at 6:54 PM, Pierre Smits <[hidden email]>
wrote:

> We could also consider to have for each component a separate ASF git repo
> that replicates to external repo structures like GitHub.

+1

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Thu, Jan 12, 2017 at 11:58 AM, Jacopo Cappellato <
[hidden email]> wrote:

> On Wed, Jan 11, 2017 at 6:54 PM, Pierre Smits <[hidden email]>
> wrote:
>
> > We could also consider to have for each component a separate ASF git repo
> > that replicates to external repo structures like GitHub.
>
>
> Agreed. it would be a natural consequence of the new layout and we should
> definitely request this to the Infra.
>
> Jacopo
>

[Ashish Vijaywargiya-4]

+1

--
Kind Regards
Ashish Vijaywargiya
HotWax Systems - est. 1997


On Wed, Jan 11, 2017 at 8:31 PM, Taher Alkhateeb <[hidden email]
> wrote:

> Hello Folks
>
> This is a proposal to the community to restructure our SVN repository. We
> do this by separating "official" plugins from the core OFBiz framework and
> to provide build script tasks to easily download and install these plugins.
> The details of this proposal are as follows:
>
> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches and
> tags underneath as is)
> 2- Create a new tree under http://svn.apache.org/repos/as
> f/ofbiz/ofbiz-plugins to house all plugins
> 3- Remove /plugins/component-load.xml (any component in /plugins will load
> automatically if it is enabled in ofbiz-component.xml)
> 4- Create a gradle task with the below syntax. This task downloads a
> plugin from subversion and places it in /plugins and runs any install logic
> that it may have
>   Syntax: pullPluginSource -PpluginId=<plugin-id-here>
>   Example: pullPluginSource -PpluginId=birt
> 5- Refactor the build scripts to cater for all the above
> 6- Update README.md to reflect all the above
>
> So for example, under this proposal, trunk is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
>
> And the birt component is located in:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
>
> This would allow us to have in the future the ability to provide releases
> not only for the framework but the plugins as well as two separate products.
>
> What do you think?
>
> Cheers,
>
> Taher Alkhateeb
>
>

[Nicolas Malin-2]

Hi Taher


Le 11/01/2017 à 16:01, Taher Alkhateeb a écrit :

> Hello Folks
>
> This is a proposal to the community to restructure our SVN repository.
> We do this by separating "official" plugins from the core OFBiz
> framework and to provide build script tasks to easily download and
> install these plugins. The details of this proposal are as follows:
>
> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches
> and tags underneath as is)

Why prepare the future in the same time to rename ofbiz as ofbiz-core ?
Like that we would have :
http://svn.apache.org/repos/asf/ofbiz/ofbiz-core
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugin

> 2- Create a new tree under ps to house all plugins
> 3- Remove /plugins/component-load.xml (any component in /plugins will
> load automatically if it is enabled in ofbiz-component.xml)
> 4- Create a gradle task with the below syntax. This task downloads a
> plugin from subversion and places it in /plugins and runs any install
> logic that it may have
>   Syntax: pullPluginSource -PpluginId=<plugin-id-here>
>   Example: pullPluginSource -PpluginId=birt
> 5- Refactor the build scripts to cater for all the above
> 6- Update README.md to reflect all the above

The rest sound good for me :)
> [...]
>
> Cheers,
>
> Taher Alkhateeb
>
>

[Nicolas Malin-2]

We can see this on second time to improve the taher's suggest task
pullPluginSource with list different repository on the build.gradle

But by default only the official repository source code can be listed.

Nicolas


Le 11/01/2017 à 18:54, Pierre Smits a écrit :

> We could also consider to have for each component a separate ASF git repo
> that replicates to external repo structures like GitHub. This would
> increase exposure and potentially attract more contributors as subject
> matter experts.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Wed, Jan 11, 2017 at 4:54 PM, Jacopo Cappellato <
> [hidden email]> wrote:
>
>> I agree with the svn layout that Taher is proposing which is also inline
>> with what other Apache projects are doing (see for example [*]).
>> The idea behind these layouts is that the top level folder is for the
>> "project" and its subfolders are for the project's products:
>> project/product1
>> project/product2
>> ...
>> that for OFBiz would be (as already mentioned by Taher):
>> ofbiz/ofbiz
>> ofbiz/ofbiz-plugins
>> ofbiz/site
>> ...
>> Each of the above folders may contain the "trunk", "tags" and "branches"
>> folders.
>> In fact it is worth to mention that each Apache project can publish more
>> than one product (and in fact several do); the OFBiz project doesn't
>> currently but it is better to have a layout that will allow us to produce
>> more than one product.
>>
>> Thank you,
>>
>> Jacopo
>>
>> [*] http://svn.apache.org/repos/asf/lucene/
>>
>>
>> On Wed, Jan 11, 2017 at 4:01 PM, Taher Alkhateeb <
>> [hidden email]
>>> wrote:
>>> Hello Folks
>>>
>>> This is a proposal to the community to restructure our SVN repository. We
>>> do this by separating "official" plugins from the core OFBiz framework
>> and
>>> to provide build script tasks to easily download and install these
>> plugins.
>>> The details of this proposal are as follows:
>>>
>>> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches
>> and
>>> tags underneath as is)
>>> 2- Create a new tree under http://svn.apache.org/repos/as
>>> f/ofbiz/ofbiz-plugins to house all plugins
>>> 3- Remove /plugins/component-load.xml (any component in /plugins will
>> load
>>> automatically if it is enabled in ofbiz-component.xml)
>>> 4- Create a gradle task with the below syntax. This task downloads a
>>> plugin from subversion and places it in /plugins and runs any install
>> logic
>>> that it may have
>>>    Syntax: pullPluginSource -PpluginId=<plugin-id-here>
>>>    Example: pullPluginSource -PpluginId=birt
>>> 5- Refactor the build scripts to cater for all the above
>>> 6- Update README.md to reflect all the above
>>>
>>> So for example, under this proposal, trunk is located in:
>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk
>>>
>>> And the birt component is located in:
>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt
>>>
>>> This would allow us to have in the future the ability to provide releases
>>> not only for the framework but the plugins as well as two separate
>> products.
>>> What do you think?
>>>
>>> Cheers,
>>>
>>> Taher Alkhateeb
>>>
>>>

[taher]

I like the idea of ofbiz-core Nicolas

On Jan 12, 2017 9:49 AM, "Nicolas Malin" <[hidden email]> wrote:

> Hi Taher
>
>
> Le 11/01/2017 à 16:01, Taher Alkhateeb a écrit :
>
>> Hello Folks
>>
>> This is a proposal to the community to restructure our SVN repository. We
>> do this by separating "official" plugins from the core OFBiz framework and
>> to provide build script tasks to easily download and install these plugins.
>> The details of this proposal are as follows:
>>
>> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to
>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, branches
>> and tags underneath as is)
>>
> Why prepare the future in the same time to rename ofbiz as ofbiz-core ?
> Like that we would have :
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-core
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugin
>
>> 2- Create a new tree under ps to house all plugins
>> 3- Remove /plugins/component-load.xml (any component in /plugins will
>> load automatically if it is enabled in ofbiz-component.xml)
>> 4- Create a gradle task with the below syntax. This task downloads a
>> plugin from subversion and places it in /plugins and runs any install logic
>> that it may have
>>   Syntax: pullPluginSource -PpluginId=<plugin-id-here>
>>   Example: pullPluginSource -PpluginId=birt
>> 5- Refactor the build scripts to cater for all the above
>> 6- Update README.md to reflect all the above
>>
> The rest sound good for me :)
>
>> [...]
>>
>> Cheers,
>>
>> Taher Alkhateeb
>>
>>
>>
>

[Jacopo Cappellato-5]

On Thu, Jan 12, 2017 at 7:40 AM, Nicolas Malin <[hidden email]>
wrote:

> Why prepare the future in the same time to rename ofbiz as ofbiz-core ?
> Like that we would have :
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-core
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugin


I like it. And maybe in the future we will split framework and core:
http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework
http://svn.apache.org/repos/asf/ofbiz/ofbiz-core
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugin

representing the three layers:
* framework: programming framework and api to develop enterprise/business
applications from scratch
* core: the OFBiz data model and core (CRUD etc...) services and other
artifacts (possibly the existing "applications")
* plugins

plugins can depend on core and framework
core depends on framework
framework doesn't depend on core and plugins

Jacopo

[Nicolas Malin-2]

Le 12/01/2017 à 09:13, Jacopo Cappellato a écrit :

> On Thu, Jan 12, 2017 at 7:40 AM, Nicolas Malin <[hidden email]>
> wrote:
>
>> Why prepare the future in the same time to rename ofbiz as ofbiz-core ?
>> Like that we would have :
>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-core
>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugin
>
> I like it. And maybe in the future we will split framework and core:
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-core
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugin
>
> representing the three layers:
> * framework: programming framework and api to develop enterprise/business
> applications from scratch
> * core: the OFBiz data model and core (CRUD etc...) services and other
> artifacts (possibly the existing "applications")
> * plugins
>
> plugins can depend on core and framework
> core depends on framework
> framework doesn't depend on core and plugins
>
> Jacopo

Exactly my mind :) , I just call about ofbiz-core because
ofbiz-framework isn't ready yet, that the reason that I said "prepare
the future" ;)

Nicolas

[Pierre Smits]

Before this is executed we should decide whether there are any components
of which we feel that they should go to the attic. Otherwise we would be
moving stuff around that needn't be moved.

Best regards,

Pierre Smits

ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Thu, Jan 12, 2017 at 9:31 AM, Nicolas Malin <[hidden email]>
wrote:

> Le 12/01/2017 à 09:13, Jacopo Cappellato a écrit :
>
>> On Thu, Jan 12, 2017 at 7:40 AM, Nicolas Malin <[hidden email]>
>> wrote:
>>
>> Why prepare the future in the same time to rename ofbiz as ofbiz-core ?
>>> Like that we would have :
>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-core
>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugin
>>>
>>
>> I like it. And maybe in the future we will split framework and core:
>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework
>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-core
>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugin
>>
>> representing the three layers:
>> * framework: programming framework and api to develop enterprise/business
>> applications from scratch
>> * core: the OFBiz data model and core (CRUD etc...) services and other
>> artifacts (possibly the existing "applications")
>> * plugins
>>
>> plugins can depend on core and framework
>> core depends on framework
>> framework doesn't depend on core and plugins
>>
>> Jacopo
>>
> Exactly my mind :) , I just call about ofbiz-core because ofbiz-framework
> isn't ready yet, that the reason that I said "prepare the future" ;)
>
> Nicolas
>

[Jacques Le Roux]

Le 11/01/2017 à 16:01, Taher Alkhateeb a écrit :
> 3- Remove /plugins/component-load.xml (any component in /plugins will load automatically if it is enabled in ofbiz-component.xml)
Could we not rather use the hot-deploy mechanism in plugins and use ofbiz-component.xml only when dependencies between plugins require an
ofbiz-component.xml ? In this case should we not rename ofbiz-component.xml to plugins-order.xml
Our goal is to have no dependencies between plugins so the hot-deploy mechanism would be welcome

Jacques

[Jacques Le Roux]

Le 12/01/2017 à 07:28, Jacopo Cappellato a écrit :

> On Wed, Jan 11, 2017 at 6:54 PM, Pierre Smits <[hidden email]>
> wrote:
>
>> We could also consider to have for each component a separate ASF git repo
>> that replicates to external repo structures like GitHub.
>
> Agreed. it would be a natural consequence of the new layout and we should
> definitely request this to the Infra.
>
> Jacopo
>

We just need to know/remember that moving from Subversion to Git entails loosing some history see "Impossible" section in
https://issues.apache.org/jira/browse/LUCENE-6933 description

Jacques

[Jacques Le Roux]

That's an important point indeed, have we not Jiras or else where the status/efforts are currently known?

Jacques


Le 12/01/2017 à 10:12, Pierre Smits a écrit :

> Before this is executed we should decide whether there are any components
> of which we feel that they should go to the attic. Otherwise we would be
> moving stuff around that needn't be moved.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Thu, Jan 12, 2017 at 9:31 AM, Nicolas Malin <[hidden email]>
> wrote:
>
>> Le 12/01/2017 à 09:13, Jacopo Cappellato a écrit :
>>
>>> On Thu, Jan 12, 2017 at 7:40 AM, Nicolas Malin <[hidden email]>
>>> wrote:
>>>
>>> Why prepare the future in the same time to rename ofbiz as ofbiz-core ?
>>>> Like that we would have :
>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-core
>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugin
>>>>
>>> I like it. And maybe in the future we will split framework and core:
>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework
>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-core
>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugin
>>>
>>> representing the three layers:
>>> * framework: programming framework and api to develop enterprise/business
>>> applications from scratch
>>> * core: the OFBiz data model and core (CRUD etc...) services and other
>>> artifacts (possibly the existing "applications")
>>> * plugins
>>>
>>> plugins can depend on core and framework
>>> core depends on framework
>>> framework doesn't depend on core and plugins
>>>
>>> Jacopo
>>>
>> Exactly my mind :) , I just call about ofbiz-core because ofbiz-framework
>> isn't ready yet, that the reason that I said "prepare the future" ;)
>>
>> Nicolas
>>