Re: Remove the 91% message from gradle when running tasks (ofbiz, ofbizDebug, etc) or altogether

Hi, I think it is better to explicitly inform the user in the log message that OFBiz has started after all the components are loaded. Something like this, but can be improved with some ANSI/ASCII artwork. ## ## OFBiz has started and ready for use

Re: svn commit: r1787047 - /ofbiz/ofbiz-framework/trunk/framework/webtools/src/main/java/org/apache/ofbiz/webtools/labelmanager/LabelManagerFactory.java

How do you know that this does not crash existing code? You are switching from an ignore behavior to throwing an exception! Did you check all reference and calls to it? On Wed, Mar 15, 2017 at 4:56 PM, wrote: > Author: jleroux > Date: Wed Mar 15 13:56:38 2017 > New Revision:

Re: Remove the 91% message from gradle when running tasks (ofbiz, ofbizDebug, etc) or altogether

By that logic we should include in README.md things like: - ignore the warnings from the log file - ignore the exceptions thrown because we have some faulty forms - ignore the system crashing if you don't load data - ignore all anomalies and corner cases This is a trivial issue that is being

Remove the 91% message from gradle when running tasks (ofbiz, ofbizDebug, etc) or altogether

Hi, Do you agree about https://issues.apache.org/jira/browse/OFBIZ-9263 ? Thanks Jacques

Re: Plugins: skipped obstructing working copy (error message)

Le 15/03/2017 à 16:21, Jacques Le Roux a écrit : Le 15/03/2017 à 15:10, Jacques Le Roux a écrit : In other words, because of the plugins/README.txt file when you create a working copy from the ofbiz-framework/trunk branch you generate a .svn in root folder where there is a "knowledge" of this

Re: Plugins: skipped obstructing working copy (error message)

Le 15/03/2017 à 15:10, Jacques Le Roux a écrit : In other words, because of the plugins/README.txt file when you create a working copy from the ofbiz-framework/trunk branch you generate a .svn in root folder where there is a "knowledge" of this file and the plugins directory. So, we can't

Re: Plugins: skipped obstructing working copy (error message)

Taher, Deepak, I already explained the reason of the problem in the initial thread message. <(plugins folder) and the main .svn gets confused (in root) >> In other words, because of the plugins/README.txt file when you create a working copy from the ofbiz-framework/trunk branch you generate a

buildbot failure in on ofbiz-trunk-framework

The Buildbot has detected a new failure on builder ofbiz-trunk-framework while building . Full details are available at: https://ci.apache.org/builders/ofbiz-trunk-framework/builds/28 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: silvanus_ubuntu Build Reason: The

Re: Confusion in labels with the separator used between languages and countries

I confirm this is handled in LabelManagerFactory.java Element valueElem = (Element) valueNode; // Support old way of specifying xml:lang value. // Old way: en_AU, new way: en-AU String

buildbot exception in on ofbiz-trunk-framework

The Buildbot has detected a build exception on builder ofbiz-trunk-framework while building . Full details are available at: https://ci.apache.org/builders/ofbiz-trunk-framework/builds/27 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: silvanus_ubuntu Build Reason: The

Confusion in labels with the separator used between languages and countries

Hi committers, This is mostly for Chinese committers who are the most active in this area at the moment, but others could be interested also... I know it's confusing because Java uses underscore to separate languages from countries

buildbot success in on ofbiz-branch16

The Buildbot has detected a restored build on builder ofbiz-branch16 while building . Full details are available at: https://ci.apache.org/builders/ofbiz-branch16/builds/13 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: orcus_ubuntu Build Reason: The AnyBranchScheduler

Re: svn commit: r1786919 - in /ofbiz/ofbiz-framework/trunk/applications/accounting/widget: FieldLookupForms.xml LookupScreens.xml

Hi Taher, Common grid functionalities include pivots, sorting columns, multiple-row header, aggregate functions, in-grid editing etc. IMO, these should be standard grid features for modern ERP. I see the value of the extraction. It would be difficult to innovate in the future if lists are still

Re: svn commit: r1786919 - in /ofbiz/ofbiz-framework/trunk/applications/accounting/widget: FieldLookupForms.xml LookupScreens.xml

Still seems unclear. What is the value of this extraction? How is it implemented? Who intends on implementing the new features if any? What are the new features? How does that play into the UI refactoring intended within themes? What do we gain by this whole exercise? Given that we lost Adrian,

Re: Plugins: skipped obstructing working copy (error message)

Hi Deepak, Just to be on the safe side though, do you think that would solve the subversion issue? I mean does subversion complain because of folder deletion and then creation? or does it complain because of move a .svn based repo from one subdirectory to another? Also what about the idea of

Re: Welcome James Yong as a new committer

Many congratulations James!!! Best regards, Pranay Pandey HotWax Systems http://www.hotwaxsystems.com/ On Tue, Mar 14, 2017 at 2:26 PM, Jacopo Cappellato < jacopo.cappell...@hotwaxsystems.com> wrote: > The OFBiz PMC has invited James Yong to become a new committer and we are > happy to

Re: svn commit: r1786919 - in /ofbiz/ofbiz-framework/trunk/applications/accounting/widget: FieldLookupForms.xml LookupScreens.xml

That is what you get in transitional stages. But then again, OFBiz offers lots of flexibility in order to get from A to Z. As I read it, it was the intention of Adrian to simplify (I would like to extract list functionality from the form widget and create a new grid widget). But you can't remove

Re: Plugins: skipped obstructing working copy (error message)

Thanks Taher, Make sense, I am fine with following approach. > Would that solve the subversion problem? Let me just reiterate the steps: - checkout plugins into /temp - delete everything _inside_ /plugins - move everything (including .svn) from /temp to /plugins - delete /temp Thanks &

Re: Plugins: skipped obstructing working copy (error message)

Hi Deepak, So there are multiple issues with this code that I attempt summarize below: - First, you are directly using the subversion command in an "exec" block. We used the subversion plugin to avoid having gradle depend on anything other than gradle. I think it might be better to try and list

Re: Plugins: skipped obstructing working copy (error message)

Oh, and just for completeness, maybe another solution is to instruct subversion to ignore /plugins completely? or even delete it altogether, but make gradle create the directory if missing? On Wed, Mar 15, 2017 at 10:36 AM, Taher Alkhateeb < slidingfilame...@gmail.com> wrote: > Hi Deepak, > > So

Re: Plugins: skipped obstructing working copy (error message)

Hi Taher, I tried to change it with following bug not able to run sub process. {code} task pullAllPluginsSource(group: ofbizPlugin, description: 'Download and install all plugins from source control.') { def svnOutput = new ByteArrayOutputStream() exec { commandLine

Re: Plugins: skipped obstructing working copy (error message)

From my view, gradle is a simplified maven, is it possible to use version/snapshot way to bring the plugins in? -邮件原件- 发件人: Jacques Le Roux [mailto:jacques.le.r...@les7arts.com] 发送时间: 2017年3月15日 14:13 收件人: dev@ofbiz.apache.org 主题: Re: Plugins: skipped obstructing working copy (error

Re: Plugins: skipped obstructing working copy (error message)

What I fear (still not looked into it) is that Taher did it that way because he (rightly) wanted to have the same structure than before, ie the possibility to commit a change in a plugin from the root of the project. So I fear that another solution will impose to have as much as working copies

Re: OFBIZ-3972

It's OK with me, I was just asking a question and it seems it has been answered Jacques Le 15/03/2017 à 05:10, Deepak Dixit a écrit : Can we conclude this? Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Tue, Feb 28, 2017 at 2:27 PM, Rishi Solanki wrote: