Eventually, I got it...
The solution was to use backslashes (we are on Windows!) instead of slashes.
So I now have something like
<repository>
<id>central</id>
<name>FJA Internal Repository</name>
<url>file:\\\\xxx\\yyy\\maven2-server\\target\\repo-local</url>
</repository>
I thought the URL should rather be in an OS independent format (using
slashes) and Maven/Java would expand to specific file path format... but
this seems not to work properly.
Boy, this was a tough one. At least, this should be documented in the guides
or BBwM book!!!
Thanx,
Christoph.
> -----Ursprüngliche Nachricht-----
> Von: Doug Douglass [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 25. August 2006 20:51
> An: Maven Users List
> Betreff: Re: [M2] Problem deploying to filesystem on remote server
>
>
> Hmmm, the deploy succeeds but the artifact is neither local
> (like before)
> nor on the specified remote host?
>
> Perhaps running maven with -X will give some more detail on
> where the deploy
> is actually going. You might also try running the deploy
> manually via the
> deploy:deploy-file goal with the same URL and see what happens.
>
> Also, maybe try a different remote file:// location, just to
> make sure it's
> not something "funny" with file://xxx/yyy.
>
> Doug
>
> On 8/25/06, "Amshoff Christoph, Köln"
> <[EMAIL PROTECTED]> wrote:
> >
> > Doug,
> >
> > thanks for your reply... I was a bit surprised to get none up to now
> > ;o) So
> > thanks a lot.
> >
> > Well, you are right, the file was put into a local
> directory. So I changed
> > the URL to the file://host/share/some/path style:
> >
> > <snapshotRepository>
> > <id>central</id>
> > <name>FJA Internal Repository</name>
> > <url>file://xxx/yyy/maven2-server/target/repo-local</url>
> > <uniqueVersion>false</uniqueVersion>
> > </snapshotRepository>
> >
> > And now the file is not in the local directoy anymore
> (except my local M2
> > repository, of course) -- but not on the server either!
> > Any ideas?
> >
> > Thanks,
> > Christoph.
> >
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Doug Douglass [mailto:[EMAIL PROTECTED]
> > > Gesendet: Freitag, 25. August 2006 16:06
> > > An: Maven Users List
> > > Betreff: Re: [M2] Problem deploying to filesystem on remote server
> > >
> > >
> > > Christoph,
> > >
> > > Have you resolved this problem yet?
> > >
> > > I think you may find that maven deployed your artifact
> into a local
> > > directory. Look for a directory in the root of your local
> > > filesystem with
> > > the same name as the remote host. I say this because your
> > > file url doesn't
> > > appear to be correct for a remote location. I think it should be "
> > > file://host/some/path", or if the remote location is a
> > > windows share the url
> > > should be " file://host/share/some/path".
> > >
> > > HTH,
> > > Doug
> > >
> > > On 8/23/06, "Amshoff Christoph, Köln" <
> > > [EMAIL PROTECTED]> wrote:
> > > >
> > > > Hi,
> > > >
> > > > I'm new to Maven2 and trying to deploy my first JAR...
> alas without
> > > > success
> > > > up to now.
> > > >
> > > > We are running an internal repository using Maven-Proxy
> > > (using it as a
> > > > proxy
> > > > to "central" and for hosting our own artifacts).
> > > > This is working well, and now I would like to put my
> JARs (snapshot
> > > > version)
> > > > onto this server using the deploy goal with file system
> > > configuration.
> > > >
> > > > In my POM, I configured the settings like this:
> > > >
> > > > <snapshotRepository>
> > > > <id>central</id>
> > > > <name>xxx</name>
> > > >
> <url>file:///[a_server]/maven2-server/target/repo-local</url>
> > > > <uniqueVersion>false</uniqueVersion>
> > > > </snapshotRepository>
> > > >
> > > > The output seems to be ok, it says "551 K uploaded", but
> > > the file has NOT
> > > > been copied. Even with enabled debug information (see
> > > below) I don't see
> > > > any
> > > > problems... or is this "not adding permissions to wagon
> connection"
> > > > telling
> > > > me anything? And yes, I have full access to the specified
> > > folder on the
> > > > remote computer.
> > > >
> > > > Is file system deploy only working locally?
> > > > What else should I use to deploy to Maven-Repo?
> > > >
> > > > Any help is appreciated...
> > > >
> > > > Thanks in advance,
> > > > Christoph.
> > > >
> > > > --- snip ---
> > > > [INFO] [deploy:deploy]
> > > > [INFO] Retrieving previous build number from central
> > > > [DEBUG] repository metadata for: 'snapshot
> > > sss:foundation:4.3.2-SNAPSHOT'
> > > > could not be found on repository: central
> > > > [DEBUG] not adding permissions to wagon connection
> > > > Uploading:
> > > >
> > > >
> > > file:///[a_server]/maven2-server/target/repo-local/xxx/yyy/4.3
> > .2-SNAPSHOT/yy
> > > y-4.3.2-SNAPSHOT.jar
> > >
> > >
> >
> >
> <file:///[a_server]/maven2-server/target/repo-local/xxx/yyy/4.
3.2-SNAPSHOT/y
> > yy-4.3.2-SNAPSHOT.jar >
> > 551K uploaded
> > [INFO] Retrieving previous metadata from central
> > [DEBUG] repository metadata for: 'artifact sss:foundation' could not be
> > found on repository: central
> > [INFO] Uploading repository metadata for: 'artifact sss:foundation'
> > [DEBUG] not adding permissions to wagon connection
> > [INFO] Retrieving previous metadata from central
> > [DEBUG] repository metadata for: 'snapshot sss:foundation:4.3.2-SNAPSHOT
> '
> > could not be found on repository: central
> > [INFO] Uploading repository metadata for: 'snapshot
> > sss:foundation:4.3.2-SNAPSHOT'
> > [DEBUG] not adding permissions to wagon connection
> > [INFO] Retrieving previous metadata from central
> > [DEBUG] project information for foundation 4.3.2-SNAPSHOT could not be
> > found
> > on repository: central
> > [INFO] Uploading project information for foundation 4.3.2-SNAPSHOT
> > [DEBUG] not adding permissions to wagon connection
> > --- snap ---
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
