I'm guessing that there is some jar missing in remote (Internet) repositories, which you're adding to your local repo to solve this. And then using system scope for your dependency. Right? 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.
/Anders On Tue, Jan 25, 2011 at 09:19, Hari shankar <harsha...@gmail.com> wrote: > I have hit this bug > > http://jira.codehaus.org/browse/MNG-4809 > > Quoting it, > > We cannot specify variables to define a system path. Maven complains about > absolute path. This is a pain which forces us to either hard code the path > or use -DlocalRepository flag. > > Is there a way to use settings from settings.xml to refer to this property? > > <systemPath>${settings.localRepository}/my.jar</systemPath> > Am using, > > Apache Maven 3.0-beta-2 (r983206; 2010-08-07 16:30:51+0530) > > Can anyone please suggest a good workaround other than specifying a hard > coded path or passing -DlocalRepository flag, if one exists. > > Thanks much, > Hari >
