Allow pom module excludes to be specified in property files
Merge pull request #65 from rnc/BR33

Allow pom module excludes to be specified in property files
Preemptively load effective model along with raw model before vman execution modders get started, to avoid half-states when loading ancestry of a given child POM.

Overhauling testing to avoid using lightweight dummy project/model instances, which now fail because the effective model is missing.

Also, removing old repository-oriented test resources and test methods leftover from my last attempt to eradicate them.
Change dependency handling to use DependencyManagementKey, which uses GATC (groupId, artifactId, type, classifier) instead of just GA for matching deps in the BOMs. Also, if the specific GATC is missing, try falling back to GA and if found, inject the specific GATC one as a missing dep.
use DependencyManagementKey for dep comparison, in TestRemovalModder. Also, make scope check a little cleaner. Finally, check the BOM for a managed dep that may have a scope attached to it as well.
#53 Recursively resolve embedded expressions in output value for PropertyMappings.
Refactor to store excludedModulePoms in the session (really ManagedInfo).

Provide methods for filtering POM files based on whether they're among the excludedModulePoms using the peekedPOM coordinates map along with the excludedModulePoms set.

Switch to using a set of VersionlessProjectKey instances for excludedModulePoms to allow more than one artifactId per groupId in the spec.

Don't parse effective model for excluded module POMs.
attempting to make the console and file output both work unless turned off...file output doesn't work for some reason, but at least we have console output without so much effort now.
Fixing excludedModulePoms parsing
Move template checks to effective-pom building section.
[maven-release-plugin] prepare release pom-version-manipulator-1.2.0
[maven-release-plugin] prepare for next development iteration
Fix apparent bug where ModelBuildingResult.getRawModel() returns profile plugins that have had versions injected, which renders them non-raw and useless for our purposes. Instead, brute-forcing it by using new MavenXpp3Reader().read(..) to get the raw model.

Also, adding a little better configuration of the ModelBuildingRequest and error handling to provide the best diagnostic info we can during the effective model-reading process.
[maven-release-plugin] prepare release pom-version-manipulator-1.2.1
[maven-release-plugin] prepare for next development iteration
PomPeek now encapsulates template file checks. Minor tweak for relocate-dep so it passes the tests
Merge pull request #66 from rnc/BR35

PomPeek now encapsulates template file checks. Minor tweak for relocate-...
Don't remove developers/contributors from pom when minifying.
[maven-release-plugin] prepare release pom-version-manipulator-1.2.2
[maven-release-plugin] prepare for next development iteration