Excluding system scoped dependencies for site generation?

[Jim Bethancourt]

Hi all,
I've got some system scoped dependencies that I'm using in my project, which
works fine for the default and clean lifecycles, but it falls apart when I
do a mvn site.  Is there any way to have the site generation ignore these
jars and have maven move on with the site generation, or ignore the
dependency management part of site generation all together?

For example

   <dependency>
     <groupId>org.myapp</groupId>
     <artifactId>myjar</artifactId>
     <version>1.0</version>
     <scope>system</scope>
     <systemPath>${basedir}/lib/myjar.jar</systemPath>
   </dependency>

makes site generation fall apart because it's not in the repo (it's a jar
that was previously generated by XMLBeans and may change again)

Thanks,
Jim