are available in the ${maven.home}/site-configuration directory

+-----+
${maven.home}
     |
     +--- maven.properties
+-----+

* Group configuration

 As far as properties go for an entire build the maven.properties could be placed at
 the top of the group but I'm not really sure how this might work. There could probably
 also be a directory for plugins.xml and maven.properties.

* Project configuration

#*    *##end
#*    *###
#*    *### Classworlds is in boot directory, not in lib
#*    *##if ( $project.artifact.artifactId == "plexus-classworlds" )
#*      *##set ( $directory = 'boot' )
#*    *##end
#*    *###
#*    *### copy license file to lib/$artifactId.license
#*    *##set ( $licFile = $directory + '/' + $project.artifact.artifactId + '.license' )

  If it is not possible or desirable to put the notice in a particular
  file, then You may include the notice in a location (such as a LICENSE
  file in a relevant directory) where a recipient would be likely to
  look for such a notice.