Oh, I'm very sorry!
There's a little mistake in my findings, the deploy works fine with the
maven 3.0-beta-1. It doesn't work with the m2eclipse embbeded maven. This
embbeded maven is shown as 3.0-SNAPSHOT on eclipse preferences, but in the
docs (http://m2eclipse.sonatype.org/new-and-noteworthy.html) they say
3.0-alpha-6+.
I'm pretty sure it's useless to report a bug against a alpha version, even
with this alpha version being used on a stable release of m2eclipse, so I
think the best idea is to ask m2eclipse crew to update the embedded maven
version.
Do you have any ideas?
Att,
On Thu, Jul 22, 2010 at 11:54, Bruno Medeiros <[email protected]> wrote:
> Hi, Yossi!
>
> I attached the apache logs of the old deploys to you, I hope it can help. I
> just put on the files I sent you on the first time, these files now have:
> maven console output
> artifactory log
> apache log
> web interface info
>
> DAV deploys the file perfectly with maven 3, but in some tries with DAV I
> got the following error:
>
> Error deploying artifact: Failed to transfer file:
> http://dev.company.com.br:80/maven2/proprietary-releases-local/com/japisoft/jformula/3.7/jformula-3.7.jar.
> Return code is: 502 Bad Gateway -> [Help 1]
>
> I guess it's just some connection problems..
>
>
> I attached the deploy logs in the same format. If you need some extra info,
> just ask me.
>
> Thanks,
>
> --
> BrunoJCM
>
--
BrunoJCM
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
