maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Williams <>
Subject Re: [PROPOSAL] Capture all plugin-friendly APIs/facades in single maven-api artifact
Date Fri, 17 Aug 2007 12:29:00 GMT
I agree also, publicising a restricted API has got to be a useful  
thing for outside developers.
I was trying to do the same with the plexus container but clearly  
that did not go so well!


On 15 Aug 2007, at 16:13, John Casey wrote:

> The only problem here is that the expression evaluator is meant to  
> give access to build state, not components in the system...which is  
> why the @component annotation is handled in a completely parallel  
> subsystem.
> Obviously, plugins _can_ access basically any component in the  
> container (which I'm a little queasy about too, I'll admit)...but  
> it's much, much harder to document a free-for-all system like this,  
> rather than restricting the documentation and interfaces of  
> approved components to a distinct artifact/sub-website/etc.
> -john
> On Aug 15, 2007, at 10:59 AM, Brian E. Fox wrote:
>> The
>> expressionEvaluator already has a decent api for getting at most  
>> stuff
>> (as demonstrated in the enforcer rules...especially the
>> requirePluginVersionDefined rule), the trouble is you have to know  
>> what
>> component you want or expression is available. Currently this is only
>> accessible by reading the code and/or debugging maven itself.
> ---
> John Casey
> Committer and PMC Member, Apache Maven
> mail: jdcasey at commonjava dot org
> blog:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message