On 20/03/2009, James Carman <ja...@carmanconsulting.com> wrote: > On Fri, Mar 20, 2009 at 10:31 AM, sebb <seb...@gmail.com> wrote: > > My bad, sorry. > > > > The scope "provided" is what is required. > > > > I misunderstood the documentation to mean that the user had to provide > > the jar at compile-time, however it only requires the user to provide > > the jar at run-time. > > > > "provided" does cause Maven to check the repository at compile-time, > > which should solve the Maven issues raised in the thread. > > > > I have now tried it (after I deleted jar from repo) and it all worked well. > > Sorry for the noise. > > > > > What's wrong with just marking it as optional?
See post from Niall - it causes problems with OSGI bundles. If anything, I see that as an abuse of optional, because it's not optional. > This is an abuse of the "provided" scope, IMHO. Why? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
