Red Hat Bugzilla – Bug 728830
Maven should try to avoid know version control file.
Last modified: 2011-10-28 04:15:15 EDT
Description of problem:
Currently, maven client will try to push files inside version control directory, such as HibernateCore/trunk/pot/content/.svn/text-base/filters.pot.svnbase
1. It may push in out-dated or removed pot/po files.
2. From above example, zanata maven client actually looking for HibernateCore/trunk/pot/content/.svn/text-base/filters.pot.pot
which does not exist. Thus cause java.io.FileNotFoundException
Version-Release number of selected component (if applicable):
client API timestamp is 20110808-0952, but server API timestamp is 20110808-0601
Steps to Reproduce:
1. Push project that use svn. such as http://anonsvn.jboss.org/repos/hibernate/core/trunk/documentation/manual/src/main/docbook/
Files inside .svn is searched and pushed
Files inside .svn is ignored.
VERIFIED with commit f3a57b9e7621e0a1e2220d18e319804d3b901ad2