We're moving toward integrating mojos as first-class plexus components, while
at the same time avoiding introducing required plexus dependencies into the
@@ -22,9 +22,9 @@
there, we need to do several things to add capability to the default
configuration of plexus. This document will detail those changes.
-* Container Enhancements
Currently, the expression evaluator used to resolve configuration values
is the DefaultExpressionEvaluator, which is a local variable within the
@@ -36,7 +36,7 @@
We need a replacement for DefaultExpressionEvaluator that is capable of
traversing an object graph and extracting Object values, not just Strings.
Currently, the container uses BasicComponentConfigurator, to configure
components. This wouldn't be a problem, except for the local instance of
@@ -45,7 +45,7 @@
implementation under a different roleHint, or else replace the
We may need to define a new lifecycle/phase to contextualize a mojo right
before it's used, and reset it's state afterward. Up to now, the approach
@@ -55,9 +55,9 @@
run a reactorized project...the successive calls may leave behind configuration
artifacts from invocation to invocation.
-* Maven Modifications
@@ -66,17 +66,17 @@
some way of recontextualizing the mojo, and all we would need to do is inject
POM configuration via the lookup method or something.