int-accounting-pgsql - Build # 1826 - Fixed:

Check console output at https://ci.openbravo.com/job/int-accounting-pgsql/1826/ 
to view the results.


Committers since last success:

Changes for Build #1825

    David Miguelez <[email protected]> null
    Related to Issue 36878. Code Review Fixes

* In ReportValuedStock.java, when looking for the last costing rule
  filter by validated costing rules
* In queries, check that the warehouses are equal only when the warehouse
  dimension is Y
* Use left join with the M_Costing subqueri instead of a join
        src/org/openbravo/erpCommon/ad_reports/ReportValuationStock.java
        src/org/openbravo/erpCommon/ad_reports/ReportValuationStock_data.xsql

    David Miguelez <[email protected]> null
    Related to Issue 36878. Code Review fixes:

* Removed query to retrieve last M_Costing in Consolidated with cost query
  for the group of Transactions without Cost calculated. This must be null
* Take into account Warehouse Dimension in both queries that look for costs
   - In not consolidated, if the Warehouse Dimension is checked, the Warehouse
     of the Costing record must be the same one as the Transaction
   - In the consolidated, the Organization of the Warehouse of the Costing 
record
     must belong to the Organization of the filter of the Report. In this case,
     the average of the Costing records must be returned as the last costing 
record
        src/org/openbravo/erpCommon/ad_reports/ReportValuationStock.java
        src/org/openbravo/erpCommon/ad_reports/ReportValuationStock_data.xsql

    Mark <[email protected]> null
    Fixes issue 36878: [Valued Stock Report]: Wrong Actual Cost and Valuation
if the costing rule is validated with warehouse dimension.

Incorrect computation was made because costs related to transactions were not
grouped by warehouse and more than one cost could be showed with the cost of the
current line related to it. To fix this issue were took into account that if the
costing rule has the warehouse dimension activated, costs will be related to 
them
and calculated taking into account the transaction's warehouse. If the costing 
rule
hasn't the Warehouse dimension activated, then cost doesn't has the warehouse 
column
filled. Both cases are taken into account to a correct computation of costs.

Also was fixed when Consolidated warehouse option is choosed.
        src/org/openbravo/erpCommon/ad_reports/ReportValuationStock_data.xsql

Changes for Build #1826

    Inigo Sanchez <[email protected]> null
    Fixed issue 37051: Rich text area fields causes visibility problems in the 
grid

The problem was that the rich text area fields generated visibility problems in 
the grid under some circumstances.
(e.g. when a rich text area field has a carriage return or html tags such as 
div, br,etc.). A common usecase could
be when a text is copied from a website.

This visibility problems occurred because in form view this type of fields are 
visualized as a rich text editor and
html tags are supported but in grid view are visualized as a normal field in 
the grid and this html tags are not
properly handled by SC.

In order to avoid this grid visibility problems, when showing a rich text area 
field in grid view, now it is escaped
the html code. Visibility in form view is not changed. Now the problem has been 
fixed by taking account this situation
in getGridFieldProperties method of the RichTextUIDefinition reference.
        
modules/org.openbravo.client.kernel/src/org/openbravo/client/kernel/reference/RichTextUIDefinition.java




Last 20 lines of the console output:

[...truncated 1250 lines...]
  [ "$(jps | grep Bootstrap || true)" = "" ] && break
  sleep 5
done
[ "$(jps | grep Bootstrap || true)" != "" ] && echo "Tomcat has fail to stop" 
&& exit 1 || true
[ "$i" != "0" ] && secs=$(echo "$i * 5" | bc) && echo "Waiting for $secs secs 
for tomcat to stop"

echo
fi

[int-accounting-pgsql] $ /bin/bash -xe /tmp/hudson1607475442047620523.sh
++ jps
++ grep Bootstrap
++ true
+ '[' '' '!=' '' ']'
POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 0
Email was triggered for: Fixed
Trigger Success was overridden by another trigger and will not send an email.
Sending email for trigger: Fixed
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openbravo-builds mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openbravo-builds

Reply via email to