title: Is there a naming convention for @ComponentScan basePackageClasses?
body: <p>Spring's @ComponentScan offers a type-safe <a href="http://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/context/annotation/ComponentScan.html#basePackageClasses--"><code>basePackageClasses</code></a> attribute - seems a good thing to use especially as it isn't uncommon for packages to be renamed on the project I'm working on. The documentation says:</p>
  
  <blockquote>
    <p>Consider creating a special no-op marker class or interface in each package that serves no purpose other than being referenced by this attribute.</p>
  </blockquote>
  
  <p>... but offers no further guidance on the name of such a class. Am wondering if there are any conventions around this. <code>package-info.java</code> already exists in all packages (as enforced by Checkstyle) - would have preferred to reuse this but sadly Java doesn't allow a class of this name.</p>
  
  <p>(If no such standards exist am thinking perhaps <code>PackageInfo</code>, <code>BasePackage</code>, <code>PackageMarker</code> or similar but would prefer to follow convention if there is one.)</p>