[
https://issues.apache.org/jira/browse/SCM-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964417#comment-17964417
]
Olivier Lamy commented on SCM-233:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#993|https://github.com/apache/maven-scm/issues/993].
> maven-scm-api bug in test cases
> -------------------------------
>
> Key: SCM-233
> URL: https://issues.apache.org/jira/browse/SCM-233
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-api
> Affects Versions: 1.0-beta-4
> Reporter: Ernesto S. Tolentino Jr.
> Assignee: Ernesto S. Tolentino Jr.
> Priority: Major
> Fix For: 1.0-beta-4
>
> Attachments: SCM-233-maven-scm-api.diff
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Doing a release of an application using maven-scm will create an error when
> executing the tests for the maven-scm-api
> When it did the checkout the source was placed into the
> foo/target/foo-1.0/maven-scm-api directory and the test cases where
> executed...this resulted in an error in the ScmFileSetTest which appeared to
> come from the test case using */target/* in an execludes and a file not being
> removed or something... perhaps because of the directory path looking like
> /home/user/src/foo-trunk/target/foo-1.0/maven-scm-api/target/foo
> we need to make sure that */target/* is treated right when there are two
> "target" tokens in the path
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
