On 05/06/2007, at 11:01 AM, Carlos Sanchez wrote:
I noticed the issue with duplicated packages while playing with OSGi but is not directly related. The fact that we have same packages in different modules is just a bad practice, for architectural and easier development issues. If I see an org.apache.maven.project class I'd look into maven-project without having to search all the sources
Thinking purely from a packaging perspective, I agree with the principle but not the implementation. I didn't like the look of a 'core' package and was planning on commenting myself. (I only had a brief look at the commits didn't spend any more time with it after it was reverted until the discussion came up).
I think we need to take a more critical look at how the packages are structured to make sure each module is properly self-contained and has a well-defined public API. I think this should this be an architectural goal for 2.1.
I think it's great that we have things like the embedder which can be a simple, single point of entry for someone that uses all of Maven, but I don't ever want to lose the ability to consume discreet pieces of functionality like the artifact mechanism.
- Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
