(Getting annoyed by everyone replying to each other across 3 threads,
so picking this one to move forward from)
On 06/06/2007, at 5:29 AM, Jason van Zyl wrote:
Here is my reasoning as the Embedder as the only form we should be
exposing in the short term (the emphasis being on short term)
http://docs.codehaus.org/display/MAVEN/The+Embedder+for+all+client
+use+in+2.1
I think we all have some fundamental points of agreement:
- the embedder is the only thing we can publish as a documented
integration point (at this time)
- we would like a documented artifact and project API aside from the
embedder in the future (currently an unspecified timeframe)
- the split packaging we have is a symptom of problems in the design
and should be resolved somehow
- we will have to retain runtime compatibility in 2.1, but not
necessarily API compatibility which is fine
I agree that making wholesale package changes now is not the right
way to go - it seemed to be avoiding the real problem in most cases.
However:
- some things already depend on the artifact code alone, etc., and if
someone is able to and is prepared to live with adjusting to future
changes, I don't see a problem with it.
- John makes a good point that we can try and achieve some small wins
in this space as well without going the whole hog on redesign
Given that, if Carlos has a use case for using the individual
packages instead of the embedder and can make incremental
improvements in line with that, I think we should look at it on a
case by case basis here and move forward.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
