Tuesday July 11, 2017
Apache OFBiz News - June 2017
Apache OFBiz News June 2017Welcome to our regular monthly round-up of OFBiz news. This month we have news about yet another OFBiz release, our new website is close to being finished, we discover what 11 years of OFBiz development looks like, we look for volunteers to help us improve our code using Code Analysis tools and OFBiz gets mentioned in the ASF annual report.
Apache OFBiz 16.11.03 ReleasedDuring this month the community announced the release of 16.11.03. The new release consolidates all work done since the previous release in November last year. The release file can be downloaded following the instructions in the OFBiz Downloads page. Please refer to the Release Notes for more details of the changes introduced with this new version. Thanks very much to Scott Provost for highlighting a bug in our recent 16.11.02 release and to the OFBiz community for working together to fix the reported problem and getting the new release out so quickly to users.
Initial Draft of New OFBiz WebsiteOur community has been looking at and talking about changing our project website for quite a while. After some discussions on our mailing lists the structure was agreed and an initial template draft has been loaded into our code repository. We would like to finalise the site and hopefully change over to using the new site over the next month. If you would like take a look at a preview of the work done so far then please use the link below:
Draft OFBiz Website page.
We hope that the new website will be easier to navigate and will also align with our new OFBiz project logo.
Removing OFBiz SnapshotsFor a long while, folllowing the way other ASF projects do, the OFBiz project has been providing nightly snapshots of the latest codebase. This was setup so that developers of our community could download and use the latest updates for the branch releases. Providing these snapshots takes time and effort and does not add much, if any, in the case of OFBiz. And we have found that this is almost not utilised so has now been discontinued. It's not much different from using the SVN repository to download (check out) and it's the same after to run things with Ant or Gradle. If you are annoyed by the .svn folder created by the check out, simply drop it or use svn export. But that should not even be an issue, most of the time it's even convenient because you can then easily update, compare, etc., when you want...
OFBiz Development History on GourceDuring this month Gource was mentioned as a way to visualise the development of the OFBiz project. Gource is a tool that displays software projects as an animated tree. Various directories are shown as branches and individual files are displayed as leaves. Also details of the developers who have worked on or updated the branches and leaves can be seen over time through an animation sequence. Thanks to Jacques Le Roux for highlighting the tool and also to Michael Brohl for generating a history of 11 years of OFBiz development from 2006 until 2017. The Gource animation Michael generated is available on Youtube via the following link
OFBiz through the years
We hope our community enjoys watching the evolution of the project.
Using Code Analysis Tools to Improve OFBizIf you are interested in helping improve OFBiz but a little unsure how to get started then defects reported by code analysis tools could help.
A while ago we had a discussion on the development mailing list mentioning that we could help improve and clean up our codebase by running Code Analysis tools on our codebase and using the reports as a guide to provide patches. Doing this can be a good way to get started with the project that also delivers great benefits.
Details of the discussions and instructions for how to get started can be found at the following thread Call to action: fixing defects reported by code analysis tools.
Everyone is welcome to help out so please feel free to ask for any advice or additional information on our development mailing list
OFBiz and the ASF Annual ReportIn June the Apache Software Foundation published its regular Annual Report.. If you take a look at the report, you will see that on page 25 our OFBiz development list has been listed as one of the most active Apache project mailing lists and on page 26 Deepak Dixit is listed as one of the top 5 issue closers!
It is great to see OFBiz so active and also congratulations to Deepak.
New features and improvementsFunctional enhancements and improvements as well as updates of third party libraries and source code refactoring:
- Improve closing of Objects for the case of an exception In case of an exception after the EntityListIterator or Writer creation and before it's closed, the EntityListIterator or Writer remains in memory. Improve by using try-with-ressources where possible.
- Update geo data for India (OFBIZ-9406)
India currently has 29 states and 7 Union Territories.
- Update geoTypeId for 7 union territories from STATE to TERRITORY
- Correct several geoName territory names
- Add data for new state Telangana
- Rename Gradle task "loadDefault" to "loadAll" (OFBIZ-9411) As of OFBiz 16.12 the Gradle task has the new name and the documentation, such as README.md, has been adjusted accordingly. Discussion on this topic: https://s.apache.org/xjFj
- Add numericCode for Currency UOM (OFBIZ-9409)
The three-digit numeric code is useful when currency codes need to be understood in countries that do not use Latin scripts and for computerised systems.
- Set 3 digit numeric code the same as the numeric country code where possible.
- Update some old currency UOM, as uomId has been updated. (https://www.iso.org/iso-4217-currency-codes.html)
- Removed unused entity uiLabels for removed currency UOM (OFBIZ-9413)
- Convert RateServices.xml from miniLang to groovyDSL (OFBIZ-9381)
- Refactor and Improve Code for the following:
- Upgrade Groovy to 2.4.12 (OFBIZ-9430)
- Upgrade Tomcat to 8.5.16 (OFBIZ-9437)
- Improve closing performFindResults.listIt for the case of an exception in 3 Scrum Groovy files (OFBIZ-9389) In case of an exception after the call to the performFind service and before it's closed, the EntityListIterator remains in memory. The solution is to use a try-catch-finally because Groovy does not have try-with-ressources blocks.
BugfixesFunctional and technical bugfixes:
- Report issues with the Wiki restructuring to this ticket: (OFBIZ-9416)
- CostServices.xml#getProductCost fails currency conversion (OFBIZ-9387)
- Simple method in shipment services not terminating on error condition (OFBIZ-9407) Add a <check-errors/> to the method.
- RequestHandlerException on request link of Quote Profit page (OFBIZ-9386) Change the link to QuoteProfit from inter-app to simple. The Quote Price page has the same problem and solution (OFBIZ-9384).
- Error when creating new blog article entry (OFBIZ-9373) Change mode of auto-attributes for service createElectronicText from INOUT to IN.
- Unit test fails when "verbose" logging is turned on (OFBIZ-9305) Fix by temporarily disabling the verbose logging during the EntitySaxReaderTests.parse unit test.
- CreateShipment code logic error (OFBIZ-9425) The service createShipment creates both sales and purchase shipment with workeffort. Details on the fix can be found in the ticket.
- Cannot create a new GL Account (OFBIZ-9429) Change the service definition of createGLAccount so that it uses the pk attributes as OUT instead of INOUT. In this way, the glAccountId will be generated by OFBiz instead of being provided to the service.
- Screen broken on click ThirdPartyLogin, OAuth2GitHub, GitHubUser, OAuth2LinkedIn and LinkedInUser entities (OFBIZ-9390)
- Birt plugin depends on example plugin (OFBIZ-9383) The BIRT demo data for flexible reports depends on the Example entity from the Example plugin. Put a gradle dependency on the Example plugin. If the Example plugin misses, the birt component can't build.
- Error running the simple-method and groovy script in file QuickAnonCustomerEvents.xml (OFBIZ-9432) The script is unable to resolve the class CartItemModifyException. Add complete path to CartItemModifyException for Groovy and remove trailing semicolons. This error also concerns CustomerEvents.xml.
- Lucene tests fail due to problems in the test data (OFBIZ-9439) The Lucene test data refers to the ownerContentId "CNTGIZMOS" which is not defined in the Lucene demo data. It was instead defined in the ecommerce demo data in the file DemoWebsitePublishPointData.xml. The data is rewritten so that it reflects the test code and adds missing content associations.