If worst comes to worst, modify the POM. It's your local repository. You can do whatever you want to those files. Perhaps you should start by removing the parent's pom parent.
Of course, this will be a routine to repeat when you get the vendor's latest POM. Cheers, Paul On Thu, May 15, 2014 at 3:31 AM, Dariusz Jurojć <dariusz.jur...@daprog.pl>wrote: > Sure, i have software vendor's poms in my local repository. But I can't > modify them (mostly because vendor releases new version of poms, so I will > have to change every version of their pom - it doesn't have any sense). And > I can't force vendor to add site configuration to their poms. So I have to > do it in my pom. And I tried various methods and in every one of them maven > tried to download site configuration from parent pom. And I'm trying to > avoid this. > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/How-to-avoid-checking-parent-project-in-maven-site-plugin-tp5792945p5793085.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
