So here we go again :
A patch from Harmeet Bedi "startofbiz.sh does not have a default debug flag." (https://issues.apache.org/jira/browse/OFBIZ-2059) - OFBIZ-2059
$DEBUG flag is not specified even in comments causing people to dig an find it.
JLR's comment : that's not exactly true, there is already another DEBUG "flag" used for RMI, I think both are useful. So I have moved this "new" one near the older
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@815982 13f79535-47bb-0310-9956-ffa450edef68
$DEBUG flag is not specified even in comments causing people to dig an find it.
JLR's comment : that's not exactly true, there is already another DEBUG "flag" used for RMI, I think both are useful. So I have moved this "new" one near the older
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@815974 13f79535-47bb-0310-9956-ffa450edef68
Add this feature to forms in a consistent way with existing feature in menu (enhancing this previous feature)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@815734 13f79535-47bb-0310-9956-ffa450edef68
I was planning to wait longer, but I can't wait more. I have added a lot of small trivial changes in this patch and they are blocking me to go further on other issues...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@813307 13f79535-47bb-0310-9956-ffa450edef68
[ \t]+$ => "" (empty)
Should be easier to review when committing changes with trailing spaces removed automatically by anyedit or such tool (please refer to http://docs.ofbiz.org/x/mg)
Of course this effort to remove trailing spaces has no functional implications.
Actually, I was doing a 1st commit and as it's long to upload, I got conflicts with r763135
In the meantime I did some refactoring also in *.java and *.groovy files :
){ => ) {
if( => if (
while( => while (
}else => } else
else{ => else {
switch( => switch (
try{ => try {
}catch => } catch
catch( => catch (
}finally{ => } finally {
So these changes are also in this commit, should not be a problem anyway.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@763175 13f79535-47bb-0310-9956-ffa450edef68
We continue to approach the end... But for some exceptions, more than the 2 I found before. I will write a compilation on dev ML at end
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@761261 13f79535-47bb-0310-9956-ffa450edef68
In hyperlink and sub-hyperlink elements, replacement of target parameters by parameter sub-elements
We are near the end...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@759684 13f79535-47bb-0310-9956-ffa450edef68
In hyperlink and sub-hyperlink elements, replacement of target parameters by parameter sub-elements
This one is huge, with some changes by hand, conversion from tabs to 4 spaces and some trailing spaces (I have activated it AnyEdit plugin following the changes I made in http://docs.ofbiz.org/display/OFBADMIN/Coding+Conventions but I wonder if I should not reverse all that - I mean my plugin setting and in wiki -, it's a nightmare!)
I did my best on this one, but I'm not sure some typos did not slip in. Anyway, alea jacta est
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@759666 13f79535-47bb-0310-9956-ffa450edef68
<!-- tooltip="Same as above, uses the ${'${'bsh:...} notation to call an util method to get the now timestamp}"-->
<!-- tooltip="Same as above, uses the \${bsh:...} notation to call an util method to get the now timestamp}"-->
Maybe even all the block about this bsh syntax should be dropped anyway... (but can still be used, so maybe better to keep it ?)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@737329 13f79535-47bb-0310-9956-ffa450edef68
I tried what is documented in the PDF here http://docs.ofbiz.org/download/attachments/6430/UEL.pdf, but no way.
<<To generate literal values that include the character sequence "${" or “#{“, the developer can choose to use a composite expression as shown here:
${'${'}exprA}
#{'#{'}exprB}The resulting values would then be the strings ${exprA} and #{exprB}.
Alternatively, the escape characters \$ and \# can be used to escape what would otherwise be treated as an eval-expression. Given the literal-expressions:
\${exprA}
\#{exprB}
The resulting values would again be the strings ${exprA} and #{exprB}.>>
Or maybe I'm missing something ? (Anyway it's a weird case ;o)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@737328 13f79535-47bb-0310-9956-ffa450edef68