Hi Dan,
can you create an Jira ticket? I agree that it is very unlikely that
maven-artifact-transfer causes this, it's either Maven Core or maybe Maven
Artifact Resolver (fka Aether)
Robert
On Mon, 03 Apr 2017 08:57:35 +0200, Dan Tran <dant...@gmail.com> wrote:
yes snapshots: [enabled => false, update => daily] is the problem.
I ended up to hack by enable it before pass over to
maven-artifact-transfer
The question here why it is disabled at the first place
Thanks
-Dan
On Sun, Apr 2, 2017 at 11:38 PM, Karl Heinz Marbaise <khmarba...@gmx.de>
wrote:
Hi Dan,
On 03/04/17 07:54, Dan Tran 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]
I'm not sure but maybe this is the problem ?
not enabled to allow having snapshots ?
Kind regards
Karl Heinz
releases: [enabled => true, update => daily]
What could have caused this?
I am seeing this issue on all maven 3.1+
Thanks
-Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
