I'm still trying to put a rough shape on a new artifact API for Maven
(been slammed at work this week). I think I'm leaning toward the notion
of separating the API(s) from the implementation(s) and putting them on
separate release cycles. This way, we can publish a stable set of
interfaces, exceptions, etc. for working with the implementation, and
not release new versions of the API with each new release of the
implementation.
It seems to me that we've seen three major API changes for working with
artifacts so far in Maven, between Maven 1.x, 2.x, and now 3.x...but in
between these major changes, there has been inevitable drift. I'm
interested in pinning down the API so we can provide alternate
implementations and adapters into/out of other systems more safely.
Thoughts?
--
John Casey
Developer, PMC Chair - Apache Maven (http://maven.apache.org)
Blog: http://www.johnofalltrades.name/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
