Don't think it's a bug, it's you using it the wrong way. As I understand you, you have a dependency to some archive which you unpack. In the same project you have a system scope dependency which points at some jar that gets unpacked from the dependency above. Don't think that would work and I frankly don't understand what you're doing. That is not the Maven way. You should add the jar (artifact) extracted from the archive to you (corporate) repository instead.
/Anders On Mon, Nov 9, 2009 at 18:07, EJ Ciramella <[email protected]> wrote: > Sorry - and thank you! > > Any suggestions or is this (confirmed as a) a bug? > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Anders Hammar > Sent: Saturday, November 07, 2009 2:07 AM > To: Maven Users List > Subject: Re: system scoped dependencies are attempted to be downloaded > > Ok. In the future, it would be great if you include this kind of info when > you ask about a problem. You need to provide all info for us to be able to > help. > > /Anders > > On Fri, Nov 6, 2009 at 23:47, EJ Ciramella <[email protected]> > wrote: > > > Yeah, we have a pretty out-of-the-ordinary build process using > > jboss/atg/etc. > > > > Try this - zip up any jar and try to both unpack that AND put that jar as > a > > dependency with a system scope. > > > > This won't work. It will try to resolve the dependency and fail so it > > never unpacks the zip. > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] On > > Behalf Of Anders Hammar > > Sent: Friday, November 06, 2009 4:20 PM > > To: Maven Users List > > Subject: Re: system scoped dependencies are attempted to be downloaded > > > > Sorry, I don't know. > > I take it your setup is a little bit more complicated than your initial > > posts indicated? > > > > /Anders > > > > On Fri, Nov 6, 2009 at 22:12, EJ Ciramella <[email protected]> > > wrote: > > > > > Hmm - here's a question - if the jar I'm looking for exists inside a > zip > > > file that needs to be downloaded, unpacked and then and only then will > > > systemPath actually point at a jar - will that fail? > > > > > > When does dependency resolution happen - at the validate stage? If so, > > the > > > zip won't be downloaded and unpacked by then resulting in a systemPath > > that > > > doesn't exist. > > > > > > > > > -----Original Message----- > > > From: [email protected] [mailto:[email protected]] On > > > Behalf Of Anders Hammar > > > Sent: Friday, November 06, 2009 3:41 PM > > > To: Maven Users List > > > Subject: Re: system scoped dependencies are attempted to be downloaded > > > > > > And you have tried the very simplest project, containing just the > > > dependencies section with just this dependency? And no parent pom which > > > could hide something not obvious. For example, use the quickstart > > > archetype. > > > Also, have you tried it in a different environment (computer)? > > > If that still reproduces the issue, I suggest you create a jira and > > attach > > > that project. > > > > > > /Anders > > > > > > On Fri, Nov 6, 2009 at 21:33, EJ Ciramella <[email protected]> > > > wrote: > > > > > > > We're not using a version range. The numbers I'm speaking of below > is > > > the > > > > range of maven 2 versions I tried and had this problem. > > > > > > > > -----Original Message----- > > > > From: Wayne Fay [mailto:[email protected]] > > > > Sent: Friday, November 06, 2009 3:29 PM > > > > To: Maven Users List > > > > Subject: Re: system scoped dependencies are attempted to be > downloaded > > > > > > > > > It's simple - if you have a dependency with a system scope, maven > > 2.0.9 > > > - > > > > 2.2.1 tries looking up that dependency in any repos you may have > > mapped. > > > > > > > > > > Shouldn't it just skip that part? > > > > > > > > What happens when you change the version range to a fixed value eg > > > > >2.1.3< or >[2.1.3]<? Or if you remove the version stanza entirely > > > > since it does not apply to system scoped artifacts? > > > > > > > > Wayne > > > > > > > > --------------------------------------------------------------------- > > > > 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] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
