Detect failure to create ProjectVersionRef from Model...log it and don't try to proceed.
adding report for low-level errors, and fixing validation manager to avoid trying to log BOMs if the model's version is invalid (resulting in a null ProjectVersionRef)
some new protection against null ProjectVersionRef's ...not sure where these are coming from, exactly, but we need tests...
elapsed time calculation / formatting, and refining requires/build-requires reports to omit things with no relationships
fixing spurious NONE in requires/build-requires reports
don't report if there's nothing to report.
Allow reporting directory to be specified, make sure the exceptions for resolving are not only not null, but not empty...and rename modelErrors to refErrors in the session
Adding 3 new experimental reports to show impacts of missing/invalid POMs
change atlas groupId
use release of atlas (was maven-atlas)
[maven-release-plugin] prepare release repository-validator-0.1
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] rollback the release of repository-validator-0.1
adding sonatype parent to allow me to release
[maven-release-plugin] prepare release repository-validator-0.1
[maven-release-plugin] prepare for next development iteration
switch to application scope
Add ability to configure supplemental remote repositories for resolving artifacts, and settings.xml for specifying authentication for these repos. Also, factor out all the specific maven components and delegate their usage (for component init anyway) to the MavenComponentManager...would be nice to fully delegate all maven component usage across the board in this way, but may not be necessary
Add tracking for file-listing that accompanies all scanned POMs, and for repositories from which each resolved artifact is...well, resolved. Also, add reports to detail these two new properties
use release of atlas 0.2.0