I just downgraded to m2 alpha-3 and everything works just like before.
I would like to isolate the problem, but don't know where to start.
Is it possible to force m2 beta-1 to use maven-deploy-plugin alpha-3?
Cheers,
-Ralph.
On 21.09.2005, at 16:15, Yann Le Du wrote:
I worked around by using <repositories> in my POM.
Now :
* my settings.xml is empty of <mirrors> and <*repositories>
* my POM contains :
~ <project>
~ ...
~ <repositories>
~ <repository>
~ <id>central</id>
~ <url>http://ricfiled.as.asd.asf/maven/repository</url>
~ <snapshotPolicy>always</snapshotPolicy>
~ </repository>
~ </repositories>
~ ...
~ </project>
I manage to access all artifacts, releases (plains) and snapshots.
Ralph, I don't know if it can help you, because your problem seems
to be
happening at a later phase than mine (could be a network/proxy
problem, but you
said it was working in alpha-3...) but give it a shot :)
Anyway, the fact that I can't access snapshots by mirroring central in
settings.xml sounds like a regression to me. Shall I file in JIRA ?
Yann
--- Ralph Pöllath <[EMAIL PROTECTED]> a écrit :
On 20.09.2005, at 14:39, Yann Le Du wrote:
I'm also having troubles accessing artifacts from my corp
repository. More
exactly, I can access plain versions (e.g. 1.0.3), but not
snapshots (e.g.,
1.0.4-SNAPSHOT).
I noticed that after changing the version from 0.1-SNAPSHOT to 0.1,
m2 -X deploy prints
[INFO] [deploy:deploy]
Uploading: scp://maven.example.com/home/maven/maven2/blah/blah/0.1/
blah-0.1.jar
and then hangs forever. I tried deleting ~/.m2/repository, but that
didn't make any difference at all.
Any ideas on how to diagnose the problem? I'd really appreciate it if
someone could help, since this is a real show stopper for me.
Everything worked with m2 alpha-3, and I'd hate having to downgrade.
Thanks,
-Ralph.
--- Ralph Pöllath <[EMAIL PROTECTED]> a écrit :
since I upgraded to m2 beta 1, I'm having trouble accessing
artifacts
in my internal company-wide repository.
m2 -X deploy prints
...
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from internal-repo
and then hangs forever. I assume it's not an authentication
problem,
because changing the password in settings.xml fails immediately
with
an AuthenticationException.
Any ideas?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
