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

[taher]

Hi Jacques,

Sorry I'm a little confused I don't understand what you mean. What are you
suggesting to do exactly?

Regarding the comment "Our goal is to have no dependencies between plugins"
is the opposite of what the plugin system offers. The plugin system
specifically allows you to define dependencies from plugins on other
plugins, unless I understood you incorrectly.

Regards,

On Fri, Jan 13, 2017 at 12:31 PM, Jacques Le Roux <
[hidden email]> wrote:

> 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 à 09:31, Nicolas Malin a écrit :

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

I see some Moqui inspiration here and I too think it's a good proposition

Jacques

[Jacques Le Roux]

HI Taher,

OK I forgot that with Gradle we no longer worry about dependencies between components/plugins (is that good, future will tell...)

But my question stands

Jacques


Le 13/01/2017 à 10:38, Taher Alkhateeb a écrit :

> Hi Jacques,
>
> Sorry I'm a little confused I don't understand what you mean. What are you
> suggesting to do exactly?
>
> Regarding the comment "Our goal is to have no dependencies between plugins"
> is the opposite of what the plugin system offers. The plugin system
> specifically allows you to define dependencies from plugins on other
> plugins, unless I understood you incorrectly.
>
> Regards,
>
> On Fri, Jan 13, 2017 at 12:31 PM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> 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 13/01/2017 à 10:56, Jacques Le Roux a écrit :

> Le 12/01/2017 à 09:31, Nicolas Malin a écrit :
>> 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
>>
> I see some Moqui inspiration here and I too think it's a good proposition
>
> Jacques
>
>

Ha also I remember we decided to move the tools folder out so we would have a new
http://svn.apache.org/repos/asf/ofbiz/ofbiz-tools

Jacques

[Jacques Le Roux]

That's an interesting proposition ans should be considered indeed

Thanks Jinghai

Jacques


Le 12/01/2017 à 02:01, Shi Jinghai a écrit :

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

[Jacques Le Roux]

Le 13/01/2017 à 10:35, Jacques Le Roux a écrit :

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

There are also the svn props, see what Daniel Gruno said 2,5 years ago
https://www.linux.com/blog/apache-hadoop-transitions-git
"There are a few things like property settings that are lost, and the overall structure of a repository changes, which can make it somewhat difficult
to browse what happened in the past - until you suddenly learn how it's all set up, and then it gets easy."

Anyway nothing blocking, just to be known

Jacques

[Jacques Le Roux]

Actually you already spoke about it at http://markmail.org/message/tww4jaoy2a3l5ghs

Jacques

Le 13/01/2017 à 11:02, Jacques Le Roux a écrit :

> HI Taher,
>
> OK I forgot that with Gradle we no longer worry about dependencies between components/plugins (is that good, future will tell...)
>
> But my question stands
>
> Jacques
>
>
> Le 13/01/2017 à 10:38, Taher Alkhateeb a écrit :
>> Hi Jacques,
>>
>> Sorry I'm a little confused I don't understand what you mean. What are you
>> suggesting to do exactly?
>>
>> Regarding the comment "Our goal is to have no dependencies between plugins"
>> is the opposite of what the plugin system offers. The plugin system
>> specifically allows you to define dependencies from plugins on other
>> plugins, unless I understood you incorrectly.
>>
>> Regards,
>>
>> On Fri, Jan 13, 2017 at 12:31 PM, Jacques Le Roux <
>> [hidden email]> wrote:
>>
>>> 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
>>>
>>>
>

[Olivier.heintz]

+1 to the svn folder structure.
and I like separation between ofbiz-framework and ofbiz-core

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
>

[taher]

Thank you all very much for your votes and participation. I think this
request pretty much got approval from everyone who participated.

I will apply everything in the proposal with a minor change in reference to
a related discussion here -> https://s.apache.org/yLpE

The change is to relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/
to http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework (instead of just
/ofbiz/ofbiz)

On Sat, Jan 14, 2017 at 10:39 AM, Olivier Heintz <
[hidden email]> wrote:

> +1 to the svn folder structure.
> and I like separation between ofbiz-framework and ofbiz-core
>
> 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
> >
>

[Jacques Le Roux]

Hi Jinghai, Taher,

Taher, what do you think agout Jinghais proposition?

Jinghai, if nobody opposes the idea, would you mind creating a Jira?

Thanks

Jacques


Le 13/01/2017 à 11:09, Jacques Le Roux a écrit :

> That's an interesting proposition ans should be considered indeed
>
> Thanks Jinghai
>
> Jacques
>
>
> Le 12/01/2017 à 02:01, Shi Jinghai a écrit :
>> +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
>>
>
>

[taher]

The plugins are already published as zip archives in the implementation

On Jan 31, 2017 5:09 PM, "Jacques Le Roux" <[hidden email]>
wrote:

> Hi Jinghai, Taher,
>
> Taher, what do you think agout Jinghais proposition?
>
> Jinghai, if nobody opposes the idea, would you mind creating a Jira?
>
> Thanks
>
> Jacques
>
>
> Le 13/01/2017 à 11:09, Jacques Le Roux a écrit :
>
>> That's an interesting proposition ans should be considered indeed
>>
>> Thanks Jinghai
>>
>> Jacques
>>
>>
>> Le 12/01/2017 à 02:01, Shi Jinghai a écrit :
>>
>>> +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
>>>
>>>
>>
>>
>

[Jacques Le Roux]

Thanks Taher,

Jacques


Le 31/01/2017 à 15:12, Taher Alkhateeb a écrit :

> The plugins are already published as zip archives in the implementation
>
> On Jan 31, 2017 5:09 PM, "Jacques Le Roux" <[hidden email]>
> wrote:
>
>> Hi Jinghai, Taher,
>>
>> Taher, what do you think agout Jinghais proposition?
>>
>> Jinghai, if nobody opposes the idea, would you mind creating a Jira?
>>
>> Thanks
>>
>> Jacques
>>
>>
>> Le 13/01/2017 à 11:09, Jacques Le Roux a écrit :
>>
>>> That's an interesting proposition ans should be considered indeed
>>>
>>> Thanks Jinghai
>>>
>>> Jacques
>>>
>>>
>>> Le 12/01/2017 à 02:01, Shi Jinghai a écrit :
>>>
>>>> +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
>>>>
>>>>
>>>

[taher]

Hello Folks,

We are ready now to finally restructure our subversion repositories. This
requires the following:

- Move everything except plugins from
http://svn.apache.org/repos/asf/ofbiz/trunk to
http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk
- Move the plugins directory to a new repository in
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk
- Update the references in the website
https://ofbiz.apache.org/source-repositories.html
- Update the buildbot scripts (we might as well figure out why it fails
constantly lately)

Any volunteers to help?

Cheers,

Taher Alkhateeb

On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux <
[hidden email]> wrote:

> Thanks Taher,
>
> Jacques
>
>
>
> Le 31/01/2017 à 15:12, Taher Alkhateeb a écrit :
>
>> The plugins are already published as zip archives in the implementation
>>
>> On Jan 31, 2017 5:09 PM, "Jacques Le Roux" <[hidden email]>
>> wrote:
>>
>> Hi Jinghai, Taher,
>>>
>>> Taher, what do you think agout Jinghais proposition?
>>>
>>> Jinghai, if nobody opposes the idea, would you mind creating a Jira?
>>>
>>> Thanks
>>>
>>> Jacques
>>>
>>>
>>> Le 13/01/2017 à 11:09, Jacques Le Roux a écrit :
>>>
>>> That's an interesting proposition ans should be considered indeed
>>>>
>>>> Thanks Jinghai
>>>>
>>>> Jacques
>>>>
>>>>
>>>> Le 12/01/2017 à 02:01, Shi Jinghai a écrit :
>>>>
>>>> +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]

Hi Taher,

I am willing to help, Please let me know how can I help in this effort?

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

On Sat, Feb 11, 2017 at 7:18 PM, Taher Alkhateeb <[hidden email]
> wrote:

> Hello Folks,
>
> We are ready now to finally restructure our subversion repositories. This
> requires the following:
>
> - Move everything except plugins from
> http://svn.apache.org/repos/asf/ofbiz/trunk to
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk
> - Move the plugins directory to a new repository in
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk
> - Update the references in the website
> https://ofbiz.apache.org/source-repositories.html
> - Update the buildbot scripts (we might as well figure out why it fails
> constantly lately)
>
> Any volunteers to help?
>
> Cheers,
>
> Taher Alkhateeb
>
> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux <
> [hidden email]> wrote:
>
> > Thanks Taher,
> >
> > Jacques
> >
> >
> >
> > Le 31/01/2017 à 15:12, Taher Alkhateeb a écrit :
> >
> >> The plugins are already published as zip archives in the implementation
> >>
> >> On Jan 31, 2017 5:09 PM, "Jacques Le Roux" <
> [hidden email]>
> >> wrote:
> >>
> >> Hi Jinghai, Taher,
> >>>
> >>> Taher, what do you think agout Jinghais proposition?
> >>>
> >>> Jinghai, if nobody opposes the idea, would you mind creating a Jira?
> >>>
> >>> Thanks
> >>>
> >>> Jacques
> >>>
> >>>
> >>> Le 13/01/2017 à 11:09, Jacques Le Roux a écrit :
> >>>
> >>> That's an interesting proposition ans should be considered indeed
> >>>>
> >>>> Thanks Jinghai
> >>>>
> >>>> Jacques
> >>>>
> >>>>
> >>>> Le 12/01/2017 à 02:01, Shi Jinghai a écrit :
> >>>>
> >>>> +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
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >
>

[taher]

Hi Deepak,

Thank you for helping out! To me the challenge now is figuring out how to
do the restructure. Do we move? copy and dump? or some other strategy [1].
What happens to the subversion history? Should we add a tag that perhaps
says "before_restructuring_svn" for example? We also need to figure the
actual command itself to create the new repositories.

If you can help in this area it would be great, and I can focus on perhaps
making sure the plugin API works correctly and updating buildbot. I already
have OFBIZ-9182 setup for this task, so perhaps you can work over there on
the actual restructuring, putting the commands and your thoughts in place
on how to do it exactly.

[1]
http://stackoverflow.com/questions/360758/moving-a-subversion-repository-to-another-server#360829

Cheers,

Taher Alkhateeb

On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit <
[hidden email]> wrote:

> Hi Taher,
>
> I am willing to help, Please let me know how can I help in this effort?
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
>
> On Sat, Feb 11, 2017 at 7:18 PM, Taher Alkhateeb <
> [hidden email]
> > wrote:
>
> > Hello Folks,
> >
> > We are ready now to finally restructure our subversion repositories. This
> > requires the following:
> >
> > - Move everything except plugins from
> > http://svn.apache.org/repos/asf/ofbiz/trunk to
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk
> > - Move the plugins directory to a new repository in
> > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk
> > - Update the references in the website
> > https://ofbiz.apache.org/source-repositories.html
> > - Update the buildbot scripts (we might as well figure out why it fails
> > constantly lately)
> >
> > Any volunteers to help?
> >
> > Cheers,
> >
> > Taher Alkhateeb
> >
> > On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux <
> > [hidden email]> wrote:
> >
> > > Thanks Taher,
> > >
> > > Jacques
> > >
> > >
> > >
> > > Le 31/01/2017 à 15:12, Taher Alkhateeb a écrit :
> > >
> > >> The plugins are already published as zip archives in the
> implementation
> > >>
> > >> On Jan 31, 2017 5:09 PM, "Jacques Le Roux" <
> > [hidden email]>
> > >> wrote:
> > >>
> > >> Hi Jinghai, Taher,
> > >>>
> > >>> Taher, what do you think agout Jinghais proposition?
> > >>>
> > >>> Jinghai, if nobody opposes the idea, would you mind creating a Jira?
> > >>>
> > >>> Thanks
> > >>>
> > >>> Jacques
> > >>>
> > >>>
> > >>> Le 13/01/2017 à 11:09, Jacques Le Roux a écrit :
> > >>>
> > >>> That's an interesting proposition ans should be considered indeed
> > >>>>
> > >>>> Thanks Jinghai
> > >>>>
> > >>>> Jacques
> > >>>>
> > >>>>
> > >>>> Le 12/01/2017 à 02:01, Shi Jinghai a écrit :
> > >>>>
> > >>>> +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
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>
> > >
> >
>

[Jacques Le Roux]

Hi,

As it was discussed, I assume ofbiz-framework contains also applications.

So I agree with the proposed structure and the move. I note that the proposed structure is also good for next created branches for releases and such.

If we use svn move we should not lose history. This explains it: "svn help rename". So we should use

svn move -m "Moves plugins and creates the new structure" https://svn.apache.org/repos/asf/ofbiz/trunk 
http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk

svn move -m "Moves plugins and creates the new structure" https://svn.apache.org/repos/asf/ofbiz/trunk/plugins 
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk

Delete plugins from a "trunk" working copy checked out from the new trunk location (http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk) and
commit this change using the same "Moves plugins and creates the new structure" comment

Adds and a svn:externals for the plugins using the same "Moves plugins and creates the new structure" comment.

By adding a svn:externals, I mean committing, from the "trunk" working copy this svn:externals root properties (a line) with a relative path to the
common parent directory (http://svn.apache.org/repos/asf/ofbiz)

../../ofbiz-plugins/trunk plugins

I can do it. Please check and confirm my assertions before I do, by reading http://svnbook.red-bean.com/en/1.8/svn.advanced.externals.html

Thanks to the svn:externals, we'll have no problems with Buildbot and other aspects. Like committing to ofbiz-plugins from the integrated whole.
Though not recursively, which means committing twice if you have changes in ofbiz-framework AND ofbiz-plugins. It's not a big deal IMO, you just have
to remember it...

Jacques



Le 12/02/2017 à 09:15, Deepak Dixit a écrit :

> Hi Taher,
>
> I am willing to help, Please let me know how can I help in this effort?
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
>
> On Sat, Feb 11, 2017 at 7:18 PM, Taher Alkhateeb <[hidden email]
>> wrote:
>> Hello Folks,
>>
>> We are ready now to finally restructure our subversion repositories. This
>> requires the following:
>>
>> - Move everything except plugins from
>> http://svn.apache.org/repos/asf/ofbiz/trunk to
>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk
>> - Move the plugins directory to a new repository in
>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk
>> - Update the references in the website
>> https://ofbiz.apache.org/source-repositories.html
>> - Update the buildbot scripts (we might as well figure out why it fails
>> constantly lately)
>>
>> Any volunteers to help?
>>
>> Cheers,
>>
>> Taher Alkhateeb
>>
>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux <
>> [hidden email]> wrote:
>>
>>> Thanks Taher,
>>>
>>> Jacques
>>>
>>>
>>>
>>> Le 31/01/2017 à 15:12, Taher Alkhateeb a écrit :
>>>
>>>> The plugins are already published as zip archives in the implementation
>>>>
>>>> On Jan 31, 2017 5:09 PM, "Jacques Le Roux" <
>> [hidden email]>
>>>> wrote:
>>>>
>>>> Hi Jinghai, Taher,
>>>>> Taher, what do you think agout Jinghais proposition?
>>>>>
>>>>> Jinghai, if nobody opposes the idea, would you mind creating a Jira?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Jacques
>>>>>
>>>>>
>>>>> Le 13/01/2017 à 11:09, Jacques Le Roux a écrit :
>>>>>
>>>>> That's an interesting proposition ans should be considered indeed
>>>>>> Thanks Jinghai
>>>>>>
>>>>>> Jacques
>>>>>>
>>>>>>
>>>>>> Le 12/01/2017 à 02:01, Shi Jinghai a écrit :
>>>>>>
>>>>>> +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]

Hi Taher,

We can directly use svn mv command to restructure. It will retail svn
history. It will automatically create new directory/folder in destination
if not present.

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

On Sun, Feb 12, 2017 at 2:44 PM, Taher Alkhateeb <[hidden email]
> wrote:

> Hi Deepak,
>
> Thank you for helping out! To me the challenge now is figuring out how to
> do the restructure. Do we move? copy and dump? or some other strategy [1].
> What happens to the subversion history? Should we add a tag that perhaps
> says "before_restructuring_svn" for example? We also need to figure the
> actual command itself to create the new repositories.
>
> If you can help in this area it would be great, and I can focus on perhaps
> making sure the plugin API works correctly and updating buildbot. I already
> have OFBIZ-9182 setup for this task, so perhaps you can work over there on
> the actual restructuring, putting the commands and your thoughts in place
> on how to do it exactly.
>
> [1]
> http://stackoverflow.com/questions/360758/moving-a-subversio
> n-repository-to-another-server#360829
>
> Cheers,
>
> Taher Alkhateeb
>
> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit <
> [hidden email]> wrote:
>
> > Hi Taher,
> >
> > I am willing to help, Please let me know how can I help in this effort?
> >
> > Thanks & Regards
> > --
> > Deepak Dixit
> > www.hotwaxsystems.com
> >
> > On Sat, Feb 11, 2017 at 7:18 PM, Taher Alkhateeb <
> > [hidden email]
> > > wrote:
> >
> > > Hello Folks,
> > >
> > > We are ready now to finally restructure our subversion repositories.
> This
> > > requires the following:
> > >
> > > - Move everything except plugins from
> > > http://svn.apache.org/repos/asf/ofbiz/trunk to
> > > http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk
> > > - Move the plugins directory to a new repository in
> > > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk
> > > - Update the references in the website
> > > https://ofbiz.apache.org/source-repositories.html
> > > - Update the buildbot scripts (we might as well figure out why it fails
> > > constantly lately)
> > >
> > > Any volunteers to help?
> > >
> > > Cheers,
> > >
> > > Taher Alkhateeb
> > >
> > > On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux <
> > > [hidden email]> wrote:
> > >
> > > > Thanks Taher,
> > > >
> > > > Jacques
> > > >
> > > >
> > > >
> > > > Le 31/01/2017 à 15:12, Taher Alkhateeb a écrit :
> > > >
> > > >> The plugins are already published as zip archives in the
> > implementation
> > > >>
> > > >> On Jan 31, 2017 5:09 PM, "Jacques Le Roux" <
> > > [hidden email]>
> > > >> wrote:
> > > >>
> > > >> Hi Jinghai, Taher,
> > > >>>
> > > >>> Taher, what do you think agout Jinghais proposition?
> > > >>>
> > > >>> Jinghai, if nobody opposes the idea, would you mind creating a
> Jira?
> > > >>>
> > > >>> Thanks
> > > >>>
> > > >>> Jacques
> > > >>>
> > > >>>
> > > >>> Le 13/01/2017 à 11:09, Jacques Le Roux a écrit :
> > > >>>
> > > >>> That's an interesting proposition ans should be considered indeed
> > > >>>>
> > > >>>> Thanks Jinghai
> > > >>>>
> > > >>>> Jacques
> > > >>>>
> > > >>>>
> > > >>>> Le 12/01/2017 à 02:01, Shi Jinghai a écrit :
> > > >>>>
> > > >>>> +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]

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 <
[hidden email]> wrote:

> Hi Taher,
>
> We can directly use svn mv command to restructure. It will retail svn
> history. It will automatically create new directory/folder in destination
> if not present.
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
>
> On Sun, Feb 12, 2017 at 2:44 PM, Taher Alkhateeb <
> [hidden email]> wrote:
>
>> Hi Deepak,
>>
>> Thank you for helping out! To me the challenge now is figuring out how to
>> do the restructure. Do we move? copy and dump? or some other strategy [1].
>> What happens to the subversion history? Should we add a tag that perhaps
>> says "before_restructuring_svn" for example? We also need to figure the
>> actual command itself to create the new repositories.
>>
>> If you can help in this area it would be great, and I can focus on perhaps
>> making sure the plugin API works correctly and updating buildbot. I
>> already
>> have OFBIZ-9182 setup for this task, so perhaps you can work over there on
>> the actual restructuring, putting the commands and your thoughts in place
>> on how to do it exactly.
>>
>> [1]
>> http://stackoverflow.com/questions/360758/moving-a-subversio
>> n-repository-to-another-server#360829
>>
>> Cheers,
>>
>> Taher Alkhateeb
>>
>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit <
>> [hidden email]> wrote:
>>
>> > Hi Taher,
>> >
>> > I am willing to help, Please let me know how can I help in this effort?
>> >
>> > Thanks & Regards
>> > --
>> > Deepak Dixit
>> > www.hotwaxsystems.com
>> >
>> > On Sat, Feb 11, 2017 at 7:18 PM, Taher Alkhateeb <
>> > [hidden email]
>> > > wrote:
>> >
>> > > Hello Folks,
>> > >
>> > > We are ready now to finally restructure our subversion repositories.
>> This
>> > > requires the following:
>> > >
>> > > - Move everything except plugins from
>> > > http://svn.apache.org/repos/asf/ofbiz/trunk to
>> > > http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk
>> > > - Move the plugins directory to a new repository in
>> > > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk
>> > > - Update the references in the website
>> > > https://ofbiz.apache.org/source-repositories.html
>> > > - Update the buildbot scripts (we might as well figure out why it
>> fails
>> > > constantly lately)
>> > >
>> > > Any volunteers to help?
>> > >
>> > > Cheers,
>> > >
>> > > Taher Alkhateeb
>> > >
>> > > On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux <
>> > > [hidden email]> wrote:
>> > >
>> > > > Thanks Taher,
>> > > >
>> > > > Jacques
>> > > >
>> > > >
>> > > >
>> > > > Le 31/01/2017 à 15:12, Taher Alkhateeb a écrit :
>> > > >
>> > > >> The plugins are already published as zip archives in the
>> > implementation
>> > > >>
>> > > >> On Jan 31, 2017 5:09 PM, "Jacques Le Roux" <
>> > > [hidden email]>
>> > > >> wrote:
>> > > >>
>> > > >> Hi Jinghai, Taher,
>> > > >>>
>> > > >>> Taher, what do you think agout Jinghais proposition?
>> > > >>>
>> > > >>> Jinghai, if nobody opposes the idea, would you mind creating a
>> Jira?
>> > > >>>
>> > > >>> Thanks
>> > > >>>
>> > > >>> Jacques
>> > > >>>
>> > > >>>
>> > > >>> Le 13/01/2017 à 11:09, Jacques Le Roux a écrit :
>> > > >>>
>> > > >>> That's an interesting proposition ans should be considered indeed
>> > > >>>>
>> > > >>>> Thanks Jinghai
>> > > >>>>
>> > > >>>> Jacques
>> > > >>>>
>> > > >>>>
>> > > >>>> Le 12/01/2017 à 02:01, Shi Jinghai a écrit :
>> > > >>>>
>> > > >>>> +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]

Hi Jacques,
We don't need to delete plugins from trunk as svn move will move this to
destination. So first move plugins from trunk to new structure and then
move trunk to new location.

So sequence should be like following:

svn move -m "Moves plugins and creates the new structure"
https://svn.apache.org/repos/asf/ofbiz/trunk/plugins
http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk


svn move -m "Moves plugins and creates the new structure"
https://svn.apache.org/repos/asf/ofbiz/trunkhttp://svn.apache.org/repos/as
f/ofbiz/ofbiz-framework/trunk



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

On Sun, Feb 12, 2017 at 2:48 PM, Jacques Le Roux <
[hidden email]> wrote:

> Hi,
>
> As it was discussed, I assume ofbiz-framework contains also applications.
>
> So I agree with the proposed structure and the move. I note that the
> proposed structure is also good for next created branches for releases and
> such.
>
> If we use svn move we should not lose history. This explains it: "svn help
> rename". So we should use
>
> svn move -m "Moves plugins and creates the new structure"
> https://svn.apache.org/repos/asf/ofbiz/trunk
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk
>
> svn move -m "Moves plugins and creates the new structure"
> https://svn.apache.org/repos/asf/ofbiz/trunk/plugins
> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk
>
> Delete plugins from a "trunk" working copy checked out from the new trunk
> location (http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk)
> and commit this change using the same "Moves plugins and creates the new
> structure" comment
>
> Adds and a svn:externals for the plugins using the same "Moves plugins and
> creates the new structure" comment.
>
> By adding a svn:externals, I mean committing, from the "trunk" working
> copy this svn:externals root properties (a line) with a relative path to
> the common parent directory (http://svn.apache.org/repos/asf/ofbiz)
>
> ../../ofbiz-plugins/trunk plugins
>
> I can do it. Please check and confirm my assertions before I do, by
> reading http://svnbook.red-bean.com/en/1.8/svn.advanced.externals.html
>
> Thanks to the svn:externals, we'll have no problems with Buildbot and
> other aspects. Like committing to ofbiz-plugins from the integrated whole.
> Though not recursively, which means committing twice if you have changes in
> ofbiz-framework AND ofbiz-plugins. It's not a big deal IMO, you just have
> to remember it...
>
> Jacques
>
>
>
>
> Le 12/02/2017 à 09:15, Deepak Dixit a écrit :
>
>> Hi Taher,
>>
>> I am willing to help, Please let me know how can I help in this effort?
>>
>> Thanks & Regards
>> --
>> Deepak Dixit
>> www.hotwaxsystems.com
>>
>> On Sat, Feb 11, 2017 at 7:18 PM, Taher Alkhateeb <
>> [hidden email]
>>
>>> wrote:
>>> Hello Folks,
>>>
>>> We are ready now to finally restructure our subversion repositories. This
>>> requires the following:
>>>
>>> - Move everything except plugins from
>>> http://svn.apache.org/repos/asf/ofbiz/trunk to
>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk
>>> - Move the plugins directory to a new repository in
>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk
>>> - Update the references in the website
>>> https://ofbiz.apache.org/source-repositories.html
>>> - Update the buildbot scripts (we might as well figure out why it fails
>>> constantly lately)
>>>
>>> Any volunteers to help?
>>>
>>> Cheers,
>>>
>>> Taher Alkhateeb
>>>
>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux <
>>> [hidden email]> wrote:
>>>
>>> Thanks Taher,
>>>>
>>>> Jacques
>>>>
>>>>
>>>>
>>>> Le 31/01/2017 à 15:12, Taher Alkhateeb a écrit :
>>>>
>>>> The plugins are already published as zip archives in the implementation
>>>>>
>>>>> On Jan 31, 2017 5:09 PM, "Jacques Le Roux" <
>>>>>
>>>> [hidden email]>
>>>
>>>> wrote:
>>>>>
>>>>> Hi Jinghai, Taher,
>>>>>
>>>>>> Taher, what do you think agout Jinghais proposition?
>>>>>>
>>>>>> Jinghai, if nobody opposes the idea, would you mind creating a Jira?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Jacques
>>>>>>
>>>>>>
>>>>>> Le 13/01/2017 à 11:09, Jacques Le Roux a écrit :
>>>>>>
>>>>>> That's an interesting proposition ans should be considered indeed
>>>>>>
>>>>>>> Thanks Jinghai
>>>>>>>
>>>>>>> Jacques
>>>>>>>
>>>>>>>
>>>>>>> Le 12/01/2017 à 02:01, Shi Jinghai a écrit :
>>>>>>>
>>>>>>> +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
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>

[Jacques Le Roux]

Hi Taher,

I think adding a tag is a good idea which missed in my proposition

Jacques


Le 12/02/2017 à 10:14, Taher Alkhateeb a écrit :

> Hi Deepak,
>
> Thank you for helping out! To me the challenge now is figuring out how to
> do the restructure. Do we move? copy and dump? or some other strategy [1].
> What happens to the subversion history? Should we add a tag that perhaps
> says "before_restructuring_svn" for example? We also need to figure the
> actual command itself to create the new repositories.
>
> If you can help in this area it would be great, and I can focus on perhaps
> making sure the plugin API works correctly and updating buildbot. I already
> have OFBIZ-9182 setup for this task, so perhaps you can work over there on
> the actual restructuring, putting the commands and your thoughts in place
> on how to do it exactly.
>
> [1]
> http://stackoverflow.com/questions/360758/moving-a-subversion-repository-to-another-server#360829
>
> Cheers,
>
> Taher Alkhateeb
>
> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit <
> [hidden email]> wrote:
>
>> Hi Taher,
>>
>> I am willing to help, Please let me know how can I help in this effort?
>>
>> Thanks & Regards
>> --
>> Deepak Dixit
>> www.hotwaxsystems.com
>>
>> On Sat, Feb 11, 2017 at 7:18 PM, Taher Alkhateeb <
>> [hidden email]
>>> wrote:
>>> Hello Folks,
>>>
>>> We are ready now to finally restructure our subversion repositories. This
>>> requires the following:
>>>
>>> - Move everything except plugins from
>>> http://svn.apache.org/repos/asf/ofbiz/trunk to
>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk
>>> - Move the plugins directory to a new repository in
>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk
>>> - Update the references in the website
>>> https://ofbiz.apache.org/source-repositories.html
>>> - Update the buildbot scripts (we might as well figure out why it fails
>>> constantly lately)
>>>
>>> Any volunteers to help?
>>>
>>> Cheers,
>>>
>>> Taher Alkhateeb
>>>
>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux <
>>> [hidden email]> wrote:
>>>
>>>> Thanks Taher,
>>>>
>>>> Jacques
>>>>
>>>>
>>>>
>>>> Le 31/01/2017 à 15:12, Taher Alkhateeb a écrit :
>>>>
>>>>> The plugins are already published as zip archives in the
>> implementation
>>>>> On Jan 31, 2017 5:09 PM, "Jacques Le Roux" <
>>> [hidden email]>
>>>>> wrote:
>>>>>
>>>>> Hi Jinghai, Taher,
>>>>>> Taher, what do you think agout Jinghais proposition?
>>>>>>
>>>>>> Jinghai, if nobody opposes the idea, would you mind creating a Jira?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Jacques
>>>>>>
>>>>>>
>>>>>> Le 13/01/2017 à 11:09, Jacques Le Roux a écrit :
>>>>>>
>>>>>> That's an interesting proposition ans should be considered indeed
>>>>>>> Thanks Jinghai
>>>>>>>
>>>>>>> Jacques
>>>>>>>
>>>>>>>
>>>>>>> Le 12/01/2017 à 02:01, Shi Jinghai a écrit :
>>>>>>>
>>>>>>> +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
>>>>>>>>
>>>>>>>>
>>>>>>>>