Depends, seems that Ingo Wolfmayr got some success with the SEO branch
https://issues.apache.org/jira/browse/OFBIZ-5312
And even with a released package, or whatever coming from the project, you
always have the need to adapt to your specific needs.
When compared to a release branch, I don't see the released package as at benefit for users, more a dogma (and a license guarantee) from the ASF, and
not fitting very well in case of OFBiz.
Jacques
Le 13/11/2014 15:48, Pierre Smits a écrit :
Hi all,
Putting special purpose components (and others) in separate development
branches is in effect the same as creating svn sub projects for those
components.
As Jacques pointed out, this is not equal to making them available to the
user in a released form. The user still has to undertake (quite some) extra
steps to get something to be able to work with it in a production
environment.
Regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
On Thu, Nov 13, 2014 at 9:58 AM, Jacques Le Roux <
[email protected]> wrote:
The official decision is not done, but we have already kinda decided to
put them back in the branch. The idea is of course to make them work again
in the branch.
They would though not be available in the next 13.07 release (ie
R13.07.0.2), but in sync in the release branch since, after reintroduction,
there will not be any new features in the branch, but as normal only bug
fixes.
http://markmail.org/message/fmmnvpzrf4sxmnvy
So it would be easy and safe to integrate them in a released package using
a simple copy.
Or to keep in sync with bug fixes svn external like I did for the demo
(not at the moment) https://svn.apache.org/viewvc/
ofbiz/trunk/tools/demo-backup/branch13.7-demo.patch?
revision=1613049&view=markup
(the port.https.enabled=N property is only for the demo)
This also suggest that it's easier to work from the branch than from a
released package, think about it
This is not how things are normally handled at the ASF (other projects
are often actually libs).
So we could suggest this way to do in our download page?
As discussed in above thread, another possibility is to create sub
projects.
But for now the most active committers are rather against. Which does not
mean it will never happen...
Jacques
Le 13/11/2014 01:48, Ron Wheeler a écrit :
Another reason to get them into sub-projects.
