Well for whatever reason it didn't work for me and I don't use a proxy. I'll try to find and fetch the docs for my jarjar solution shortly.
On Aug 21, 2012, at 1:29 PM, Kalle Korhonen <[email protected]> wrote: > On Tue, Aug 21, 2012 at 10:05 AM, Lenny Primak <[email protected]> wrote: >> I don't think Maven works that way. The jar dependencies are just that, jar >> dependencies. >> Maven doesn't look and bring in the dependencies <repository> information. >> I believe that it's done by design that way. > > It does. Since the beginning of times, you've been able to specify > additional repositories in the pom. However the issue is that > nowadays, most people use a Maven proxy repository, which is according > to Maven best practices. You have to configure your proxy separately > with all the repos you want to use so you are back to square one. One > of the primary use cases for using a Maven proxy is exactly to prevent > Maven going out on the open Internet and fetching libraries from repos > of unknown quality. > > Kalle > > >> >> On Aug 21, 2012, at 12:57 PM, Howard Lewis Ship wrote: >> >>> See https://issues.apache.org/jira/browse/TAP5-1992 >>> >>> I don't understand why Maven doesn't pick up the <repository> element >>> in the tapestry-yuicompressor POM. >> \ >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
