RE: [Clirr-devel] deploy trouble

[Vincent M. <vma...@pi...>]

Hi Lars,

> -----Original Message-----
> From: cli...@li... [mailto:clirr-devel-
> ad...@li...] On Behalf Of Lars K=FChne
> Sent: dimanche 5 septembre 2004 17:33
> To: cli...@li...
> Subject: [Clirr-devel] deploy trouble
>=20
> Hi,
>=20
> I have updated our web site with the 0.4 docs, but I'm getting errors
> when I try to deploy the binaries:
>=20
>  > cd core; maven -Dmaven.username=3Dlkuehne dist:deploy;
>=20
> [...]
> dist:deploy-bin:
>     [echo] maven.repo.list is not set - using legacy deploy mode
>     [echo] DEPRECATED: use of deploy:artifact tag and the legacy =
deploy
> method are deprecated
>     [echo]
>         Copying project.xml to the
> /home/groups/c/cl/clirr/htdocs/builds//clirr/poms on =
shell.sourceforge.net
>=20
>     [echo]
>           Executing [...]; chgrp maven clirr-core-0.4.pom [...]
>=20
>     [exec] chgrp: changing group of `clirr-core-0.4.pom': Operation =
not
> permitted
>=20
> BUILD FAILED
>=20
>=20
> Questions:
>=20
>     * Where can I tell Maven to use the unix group name 'clirr' or
>       prevent the chgrp call completely?

Hmm... I don't know anything about the dist plugin but I wouldn't use it =
if
I were you. If you wish to update the web site, you should use the
"site:deploy" goal.

For the binaries, we need to check it. I have never done it. I always =
deploy
to the Maven repositories using the scm plugin (see the reference page =
on
the Maven web site for deploying plugins). I think we can use that if =
you
wish to deploy the binaries to SF. That said we'll need to decide =
whether we
want them on ibiblio or on SF...

>     * If I use maven.repo.list (from the artifact plugin) instead of =
the
>       'legacy deploy mode', it seems I need to put my sourceforge
>       password in a file that is publically accessible via CVS ?!?

You should use the scm plugin (after reading the doc on maven site as it
does quite a lot of things that needs to be understood).

Thanks
-Vincent