This seems to be working fine actually - as I can set up a repository on the
machine running resin and deploy the artifact directly to the server and it
gets picked up and redeployed fine.

Now to hope I don't hit any permgen problems which seem to plague my hot
redeploys in the past.

On 10/26/07, Mark Derricutt <[EMAIL PROTECTED]> wrote:
> That may actually solve my problem, but what the jetty maven deployer does
> is take the war file from remote repositories based on:
>   - Repository URL (http resource, thou maven supports ftp, scp, sftp
> etc.)
>   - groupid
>   - artifactid
>   - version number
> These values 'describe' the artifact rather than point to a physical file
> location.
> I should be able to do a mix of archive-path pointing at a .war file in
> the local maven cache, and a separate process which manually does the maven
> update.
> Cheers,
> Mark
> On 10/26/07, Scott Ferguson <[EMAIL PROTECTED]> wrote:
> >
> >
> > I'm not sure that's what he wants.  The archive-path is probably the
> > right attribute:
> >
> >

It`s not the tree that forsakes the flower, but the flower that forsakes the
Someday I`ll learn to love these scars - Bye Bye Beautiful
resin-interest mailing list

Reply via email to