EnforcerRuleHelper#getComponent() throws exception

I don't believe that's a standard component that can be pulled...hence the lookup exception. Can you just instantiate a singleton in your rule?

Sure, that's not a problem, I could just create an instance of the DefaultProjectDependencyAnalyzer. Would it be possible to add documentation somewhere that mentions that only standard components can be pulled in using getComponent()? I was under the impression that any component could be found using getComponent().

It actually turns out that the DefaultProjectDependencyAnalyzer is depending on being started through the container and have its dependencies injected.

based on a conversation I had in IRC on this, it looks like you could put that component jar on the classpath of the enforcer and then try to load it.

This doesn't appear to work. I added the following dependency to the POM of the project the rule should run against and I still get a ComponentLookupException.

<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<dependencies>
.....
<dependency>
<groupId>org.apache.maven.shared</groupId>
<artifactId>
maven-dependency-analyzer
</artifactId>
<version>1.0-alpha-3-SNAPSHOT</version>
</dependency>
</dependencies>
....
</plugin>
</plugins>
</build>

Refactored the api to allow better access and used contextualize to get the real plugin container. I tested this with the dependency analyzer as a dependency in my plugin config and it's working now.