[technology-pmc] [CQ 5629] plexus-component-annotations Version: 1.5.5 (

[emo-ip-team@xxxxxxxxxxx]

http://dev.eclipse.org/ipzilla/show_bug.cgi?id=5629





--- Comment #7 from Benjamin Bentmann <bentmann@xxxxxxxxxxxx>  2011-09-29 06:51:41 ---
(In reply to comment #6)
> Or can an adopter use Aether in the absence of this library, but Aether
> provides extended functionality if this library is present?

Exactly. Instead of re-paraphrasing my previous two attempts to describe the
dependency relationship, let me retry with the following comparison:
plexus-component-annotations is similar to the annotations of the Java
Persistence API. A domain model gets annotated with JPA to help JPA providers
handle the ORM bits. Still, it is possible to use the beans of such an
annotated domain model in a context where the JPA library is not present and no
JPA provider is actually used. And again much like with JPA or at least some of
its vendor-specific ancestors, plexus-component-annotations could be completely
replaced by XML files embedded into Aether that carry the equivalent metadata.


-- 
Configure CQmail: http://dev.eclipse.org/ipzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the CQ.