Re: [Clirr-devel] deploy trouble

[<lak...@t-...>]

Vincent Massol wrote:

>Hi Lars,
>  
>
>>[...]
>>    
>>
>>Questions:
>>
>>    * 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.
>
>  
>

Yes, I did that and it worked.

>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...
>
>  
>

What provides the best user experience for the users of the maven 
plugin? Should we upload to both? What are the advantages/disadvantages 
of each?

Maybe we should discuss that on irc to get it sorted out quickly. I'll 
be on #clirr most of this afternoon. If you can't make it, let me know 
when you're available ...

>>    * 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).
>
>  
>

Currently reading the scm docs - looks good. (BTW: The Maven docs really 
could be clearer about what is recommended, which modules are 
deprecated, etc.)

Thanks,
Lars