RE: [Clirr-devel] deploy trouble

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

> -----Original Message-----
> From: cli...@li... [mailto:clirr-devel-
> ad...@li...] On Behalf Of Lars K=FChne
> Sent: dimanche 12 septembre 2004 14:22
> To: cli...@li...
> Subject: Re: [Clirr-devel] deploy trouble
>=20

[snip]

> >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...
> >
> >
> >
>=20
> 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?

The default Maven install is configured to use ibiblio. It only takes a =
few
seconds to add a second repository but the user has to know how to do =
it.

Thus in term of user experience, getting it on ibiblio is best. However =
this
takes a bit more of time as we have to open a JIRA issue and wait for a
Maven committer to process it.

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

Sorry I'm not available right now (I don't have an ADSL connection =
anymore
at home... :-( I'm fighting to get one but the ISPs are overwhelmed in
France and they can't satisfy user's subscriptions...). I'll be =
traveling to
India the whole week so I'm not sure I'll have the time either but I'll =
try
at least to answer some emails.

>=20
> >>    * 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).
> >
> >
> >
>=20
> Currently reading the scm docs - looks good. (BTW: The Maven docs =
really
> could be clearer about what is recommended, which modules are
> deprecated, etc.)

Yep. The Maven team needs help on the doco side. When you say "reading =
the
scm docs", you mean reading the plugin.jelly, right? ;-)

-Vincent