check the settings.XML into svn and use the custom settings.XML option. On Jul 31, 2011, at 4:25 AM, Mark Struberg <[email protected]> wrote:
> Hi folks! > > First, a big thanks to Gav and others for the upfront support on IRC :) > > Oki, here comes my problem in a hopefully bit more structured form: > > The maven plugin build is failing since a few months > https://builds.apache.org/job/maven-plugins-ITs-3.x/ > > We are working on getting this finally fixed since a few days and Dennis > Lundberg yesterday discovered that our build also fails locally if > -Dmaven.repo.local gets used. > > The reason is that we heavily do dirty tricks and use the -Dmaven.repo.local > inside our own integration test setup sometimes. This might not be the > utterly cleanest way to do it, but it's that way since years. Another project > would not do this, but we need it to test Mavens internal core stuff. > > > Now my pledge: > > Is it possible to assign the maven-plugins-ITs-3.x an own maven installation > with a slightly tweaked settings.xml? > It should have the following tag enabled (is disabled by default) and > pointing to the same location as the -Dmaven.repo.local currently points to: > > <localRepository>/path/to/special/local/repo</localRepository> > > The -Dmaven.repo.local must get removed from this build. > > > Is this possible? > > txs in advance and LieGrue, > strub
