The following document contains the listing of user tags found in the code. Below is the summary of the occurrences per tag.
Tag Class | Total number of occurrences | Tag strings used by tag class |
---|---|---|
Deprecated Work | 0 | @deprecated |
FIXME Work | 0 | fixme, @fixme |
Todo Work | 7 | todo, @todo |
Each tag is detailed below:
Number of occurrences found in the code: 7
org.apache.maven.wagon.providers.scm.ScmGitExeWagonTest | Line |
---|---|
WagonTestCase should somehow determine whether a command was unsupported and skip the test using org.junit.Assume | 44 |
org.apache.maven.wagon.providers.scm.ScmWagon | Line |
it probably creates problems if the same wagon is used in two different SCM protocols, as instance variables can keep incorrect state. | 63 |
For doing releases, we either have to be able to add files with checking out the repository structure which may not be possible, or the checkout directory needs to be a constant. Doing releases won't scale if you have to checkout the whole repository structure in order to add 3 files. | 65 |
this is less than optimal, SCM API should provide a way to add a directory recursively | 565 |
dirty fix to work around files with property svn:eol-style=native if a file has that property, first time file is added it fails, second time it succeeds the solution is check if the scm provider is svn and unset that property when the SCM API allows it | 587 |
AbstractScmProvider 6f7dd0c ignores checkOut() parameter "version" | 625 |
limitations: - destination filename must match that in the repository - should allow the "-d" CVS equiv to be passed in - we don't get granular exceptions from SCM (ie, auth, not found) - need to make it non-recursive to save time - exists() check doesn't test if it is in SCM already | 728 |