You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tamás Cservenák (Jira)" <ji...@apache.org> on 2022/05/04 11:59:00 UTC

[jira] [Comment Edited] (MNG-7078) The integration tests use the user maven settings

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

Tamás Cservenák edited comment on MNG-7078 at 5/4/22 11:58 AM:
---------------------------------------------------------------

On related note: IF no user settings.xml present, then Central is redefined (by IT env I guess) as `central:[file://|file:///]...` repository. This implies, that our IT suite is NOT testing maven in a way, that all our users use it, by getting dependencies via HTTP protocol, but by getting them via [file://|file:///] protocol...

And I find it kinda awkward, as it implies that HTTP bugs cannot be revealed with IT suite?

For some context: there is MNG-7471 that is triggered ONLY if remote download happens via HTTP transport (wagon or native, does not matter). How to write IT for it?


was (Author: cstamas):
On related note: IF no user settings.xml present, then Central is redefined (by IT env I guess) as `central:file://...` repository. This implies, that our IT suite is NOT testing maven in a way, that all our users use it, by getting dependencies via HTTP protocol, but by getting them via file:// protocol...

And I find it kinda awkward, as it implies that HTTP bugs cannot be revealed with IT suite?

> The integration tests use the user maven settings
> -------------------------------------------------
>
>                 Key: MNG-7078
>                 URL: https://issues.apache.org/jira/browse/MNG-7078
>             Project: Maven
>          Issue Type: Improvement
>          Components: Integration Tests
>            Reporter: Guillaume Nodet
>            Priority: Major
>
> I have a profile that caused one integration test to fail, but it took me some time to realise the problem came from my {{~/.m2/settings.xml}} file.  It would be better to have the tests use an empty settings file.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)