[jira] [Commented] (YETUS-5) Support per-instance maven repos

["Sean Busbey (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YETUS-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946366#comment-14946366 ] 

Sean Busbey commented on YETUS-5:
---------------------------------

+1 

nit: please attach in future as format-patch (for consistency and so we can also see the commit message)

fine to fix on commit:

{code}
+`settings.xml` uses the Maven default of `${HOME}/.m2/settings.xml`.
{code}

since the patch now handles custom settings.xml, should also update this doc line. I'm fine with either fixing the doc or pushing custom settings.xml handling over to YETUS-4.

{code}
yetus busbey$ for script in `git diff --name-only | grep -E ".*\.sh"`; do shellcheck "${script}"; done

In dev-support/test-patch-docker/test-patch-docker.sh line 351:
    extraargs=$(cat ${PATCH_DIR}/buildtool-docker-params.txt)
                    ^-- SC2086: Double quote to prevent globbing and word splitting.

{code}

> Support per-instance maven repos
> --------------------------------
>
>                 Key: YETUS-5
>                 URL: https://issues.apache.org/jira/browse/YETUS-5
>             Project: Yetus
>          Issue Type: New Feature
>          Components: Test Patch
>    Affects Versions: 0.1.0
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>         Attachments: YETUS-5.00.patch, YETUS-5.01.patch
>
>
> On busy jenkins servers, it only takes one bad apple doing a dependency:purge-local-repository to wreak havoc on other projects. In order to protect against this, test-patch should have some way to overlay the .m2 directory with something that is (minimally) per-project and maximally per run.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)