Dear Openbravo developer,
Summary:
If your instance has not installed neither the Cashflow Forecast nor the
Aging Balance Report module, you can safely discard this email. Otherwise
read it carefully!
If you update to PI using Mercurial and your instance has installed either
the Cashflow Forecast or the Aging Balance Report module, you must manually
delete these modules from the the *modules* folder and any dependent module
(like their translation) before running "*ant smartbuild -Dlocal=no*",
otherwise the update database process will fail.
If you work with Retail (which depend on these two merged modules), please
remember to update both PI and Retail modules at the same time and to
delete the merged modules and any dependent module (like their translations
if installed) as explained before.
Full explanation:
As part of the 3.0PR17Q2 release (currently PI), two external modules have
been merged into the Openbravo 3 distribution: Aging Balance Report and
Cashflow Forecast.
It means that starting from today both reports will be available in the
default Openbravo 3 installation.
During the update process from previous releases to PI (or 3.0PR17Q2 when
released) the compilation process could face problems due to dependency
issues.
All modules owned by Openbravo have been properly adapted to avoid this
kind of problems, however we can't control other external modules.
In order to detect these issues we have included a new build validation
(org.openbravo.buildvalidation.MergeDependenciesCheck) that should stop the
update process and provide a detailed description about how to fix the
detected problem.
These are the common scenarios that could create a problem:
1. *Manual update from command line with any of these merged modules
installed*. In this case the build validation will stop and forces you
to manually uninstall them (and any dependent module). On the other hand,
if the update is run from the Module Management window, the system should
automatically uninstall the modules.
2. *Instance with modules that depend on the Aging Balance or Cashflow
Forecast*. This can be a real problem usually for translations, only
when the localizer has not properly declared the translation module merge
into the Openbravo 3 translation pack. If you face this problem (due to
translation modules or any other dependent module), you just need to
manually uninstall any dependent module before proceeding with the update
process. The build validation will inform you about the affected modules
that you should uninstall.
Finally there is an optional step that you could do to clean your instances.
As you probably know, these two external modules depended on legacy API
from Openbravo 2.50. As part of the merge, we have updated the reports'
code to take advantage of the new Openbravo 3 API. If your instance has
previously installed the Aging Balance Report module, it's likely that the
"Openbravo Multi Business Partner Selector" module is not needed anymore
because no other module depends on it. If so, the build validation will
show a warning informing that you can safely delete this legacy module.
Thanks for your collaboration and sorry for the inconveniences.
Best regards,
Víctor Martínez
victor.marti...@openbravo.com
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Openbravo-development mailing list
Openbravo-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbravo-development
