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 <
[email protected]> 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 <
[email protected]
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
