Here you go. https://issues.apache.org/jira/browse/MNG-6214
Thanks On Wed, Apr 5, 2017 at 3:50 PM, Dan Tran <dant...@gmail.com> wrote: > Eric, > > looks like we are on the boat. I will file a Jira ticket > > Thanks > > -Dan > > On Wed, Apr 5, 2017 at 3:40 PM, Eric B <ebenza...@gmail.com> wrote: > >> Dan, >> >> It's this the same type of problem that I am encountering here: >> http://stackoverflow.com/q/43220923/827480 ? >> >> For me I'm not sure of the genesis of the problem, but I suspect it is >> something to do with maven not having a default snapshot repo to retrieve >> artifacts. But I don't know if you are seeing the same behaviour or if my >> issue is at all related to your question. >> >> Thanks >> >> Eric >> >> >> On Apr 3, 2017 1:55 AM, "Dan Tran" <dant...@gmail.com> wrote: >> >> Hi, >> >> I am very sure maven-artifact-transfer is not the issue. >> >> The real issue is MavenSession.ProjectBuildingRequest.RemoteRepositories, >> needed by maven-artifact-transfer, has snapshot resolution disable >> >> >> For my case, I am using maven setting's mirror to route all pom's >> repositories to my internal maven repository. >> >> This also means I have only one remoteRepository with this content from my >> debugger >> >> id: xxx >> url: http://my.internal.repo/public >> layout: default >> snapshots: [enabled => false, update => daily] >> releases: [enabled => true, update => daily] >> >> What could have caused this? >> >> I am seeing this issue on all maven 3.1+ >> >> Thanks >> >> -Dan >> > >
