Hi Svante, I did an svn update and could see several files updated. I then ran mvn package to rebuild and test.
[INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Apache ODF Toolkit ................................. SUCCESS [ 3.489 s] [INFO] ODF Custom Javadoc Taglets ......................... SUCCESS [ 13.887 s] [INFO] XML Schema to Template Mapping Tool: Parent POM .... SUCCESS [ 0.051 s] [INFO] XML Schema to Template Mapping Tool: Library ....... SUCCESS [ 38.607 s] [INFO] XML Schema to Template Mapping Tool: Maven2 Plugin . SUCCESS [ 8.818 s] [INFO] ODFDOM ............................................. SUCCESS [03:51 min] [INFO] ODF XSLT-Runner .................................... SUCCESS [ 3.893 s] [INFO] ODF XSLT-Runner Ant Task ........................... SUCCESS [ 0.589 s] [INFO] ODF Validator ...................................... SUCCESS [ 31.236 s] [INFO] Simple Java API for ODF (Simple ODF) ............... SUCCESS [01:59 min] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 07:33 min [INFO] Finished at: 2016-01-30T16:26:03+08:00 [INFO] Final Memory: 89M/438M [INFO] ------------------------------------------------------------------------ OS was Fedora 21. So all looks good. On Sat, Jan 30, 2016 at 4:16 AM, Svante Schubert <[email protected]> wrote: > Hello odf users, > > I would like to ask you to test the latest sources with your environment as > there had been several updates. > > While working on the patch for > https://issues.apache.org/jira/browse/ODFTOOLKIT-413 > over the holiday season, I have started to add several other fixes to it, I > like to mention: > > 1. The main fix of https://issues.apache.org/jira/browse/ODFTOOLKIT-413 > The representation of the ODF manifest.xml was held twice at > run-time. Once as DOM tree and the children of the root element (file > entries) as well within a hash map for fast access. Those two instances > were once not in synch. Fixed this. > 2. There was one fix missing for applying the same solution of > https://issues.apache.org/jira/browse/ODFTOOLKIT-396. > Fix now applied at ..pkg.OdfElement method public Node cloneNode(boolean > deep) another differentiation of attribute with and without namespace > was > missing. > 3. When building under Ubuntu, I had to update the > multi-schema-validator implementation in the pom.xml as the prior was no > longer able to be downloaded. > 4. As I often work offline, I have enabled the offline build without > Internet by adding the missing ODF schema > 5. To be able to run/debug only one test from the context menu in > Netbeans, I had to update the version of the maven-wagon in the pom.xml > of > various projects. > 6. In addition many fixes for the OdfPackage class based on my prior > work on the fork of Open-XChange were added. Sorry, it was too time > consuming to split those in a clean way into separate patches, while > working at the solution and stumbling over and over again of a small > problem with an easy solution: > 1. Splitting Exception into IOException and SAXException > 2. Applying JDK 5 Generics several times > 3. Removing potential vulnerability: see > > https://www.owasp.org/index.php/XML_External_Entity_%28XXE%29_Processing > 4. Several minor fixes.. > 7. Finally, I am sorry there is quite some line changing noise due to an > accidentally used format function of my Netbeans IDE, which seems to > use a > different format algorithm to the one being used in Eclipse. Does > anybody > have a solution to this format problem? Shall we use a Maven plugin for > this automatically normalizing the source code during build time? > > The build of the patch was tested under Ubuntu and Windows10. > > Best regards, > Svante > -- Cheers, Ian C
