Plutext

When testing docx4j using the blog sample project provided under http://muammeryucel.blogspot.com/2011/01/manipulating-microsoft-docx-files-with.html, I recognized that the maven configuration provided with docx4j 2.6.0 does not match the files provided: it depends on org.apache.commons:commons-vfs-patched:1.9.1, however, only versions 1.1 and 1.1a are provided. The following maven configuration on a client project gives a work around which builds and runs correctly with the sample code mentioned above:

Code: Select all

   <dependencies>
      <dependency>
         <groupId>org.docx4j</groupId>
         <artifactId>docx4j</artifactId>
         <version>2.6.0</version>
         <scope>compile</scope>
         <exclusions>
            <exclusion>
               <groupId>org.apache.commons</groupId>
               <artifactId>commons-vfs-patched</artifactId>
            </exclusion>
         </exclusions>
      </dependency>
      <dependency>
         <groupId>org.apache.commons</groupId>
         <artifactId>commons-vfs-patched</artifactId>
         <version>1.1a</version>
      </dependency>
   </dependencies>


In my opinion, patches versions should generally use derived version ids, e.g. 1.9.1-1.1a or the like.