Bug 728830 - Maven should try to avoid know version control file.
Maven should try to avoid know version control file.
Status: CLOSED CURRENTRELEASE
Product: Zanata
Classification: Community
Component: Component-Maven (Show other bugs)
unspecified
Unspecified Unspecified
high Severity high
: ---
: ---
Assigned To: Alex Eng
Ding-Yi Chen
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-08-08 00:15 EDT by Ding-Yi Chen
Modified: 2011-10-28 04:15 EDT (History)
2 users (show)

See Also:
Fixed In Version: f3a57b9e7621e0a1e2220d18e319804d3b901ad2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-10-28 04:15:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ding-Yi Chen 2011-08-08 00:15:34 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

This causes:
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


How reproducible:
Always

Steps to Reproduce:
1. Push project that use svn. such as http://anonsvn.jboss.org/repos/hibernate/core/trunk/documentation/manual/src/main/docbook/
  
Actual results:
Files inside .svn is searched and pushed


Expected results:
Files inside .svn is ignored.
Comment 1 Ding-Yi Chen 2011-08-08 23:45:54 EDT
VERIFIED with commit f3a57b9e7621e0a1e2220d18e319804d3b901ad2

Note You need to log in before you can comment on or make changes to this bug.