Thanks guys. That's really a neat solution. To give the real context, the problem is we do it for one of google appengine (test) jar that's not pushed to repository by them for some reasons. We use a maven appengine plugin that unpacks automatically the appengine SDK to local repository and that particular jar gets extracted to some fixed location in local repo and it's been resolved via system scope path.
We don't have a repo that's been set up, but will see to set one up, however whenever new version comes up, i need to manually push that particular jar to repo. Will see whether that also can be automated. Meanwhile if you have any other points, pls share. Hari On Tue, Jan 25, 2011 at 10:43 PM, Wayne Fay <[email protected]> wrote: > >> Can anyone please suggest a good workaround other than specifying a hard > >> coded path or passing -DlocalRepository flag, if one exists. > > > The solution is then to get a repository manager and upload the "missing" > > artifact to it (making it available to all your developers). Then you > just > > declare your dependency the normal Maven way. > > I agree with Anders. IMO system scope is a (buggy) hack and should not > be used except in very few circumstances, and this is most likely not > one of them. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
