[
https://issues.apache.org/jira/browse/JENA-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14187176#comment-14187176
]
Rob Vesse commented on JENA-807:
--------------------------------
Something strange is going on here, I was certain that [~andy.seaborne] had
already fixed this a while back and certainly in my local environment when I
run {{mvn test}} on the jena-text module I do not get a {{DB/}} directory
However on Jenkins one is generated - see
https://builds.apache.org/user/rvesse/my-views/view/Jena/job/Jena_Development_Deploy/ws/jena-text/
Can't see anything obvious as to why this is happening on the build server. It
is also happening in some peoples environment as evidenced by the pull request
mentioned in the bug description. I have asked for more details on the exact
maven invocations needed to reproduce the problem
> jena-text places testing DB directory under module directory and not under
> target
> ---------------------------------------------------------------------------------
>
> Key: JENA-807
> URL: https://issues.apache.org/jira/browse/JENA-807
> Project: Apache Jena
> Issue Type: Bug
> Components: Text
> Affects Versions: Jena 2.12.2
> Reporter: Rob Vesse
>
> The {{jena-text}} module creates a temporary testing {{DB/}} directory but
> does this under its module directory and not inside the {{target/}} directory.
> This means that on subsequent runs it can cause the RAT checks to fail
> because while RAT ignores the contents of the {{target/}} directory it will
> look in a top level {{DB/}} directory. There it will find some files it
> doesn't expect resulting in a RAT check failure and a failed build.
> Note that there is a related pull request
> (https://github.com/apache/jena/pull/9) which adds {{DB/}} to the exclusion
> list but really the directory should be placed in {{target/}} regardless
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
