>From the responses so far, it looks like we have a go for focusing 1.4 on transitive dependency support, and also looking into OSGi support. Just to clarify a few points.
Some features are impacting: they may change how buildfiles work, change APIs, break add-ons, suggest a new way of doings things, or just require a lot of coding/testing/documenting. It's hard to make a release if we have a lot of those, so it's best to focus each major release on one (or very few) impacting features. Non-impacting features, like adding a new test framework, supporting another language or packaging type, those we can do any time. We'll probably want to roll those earlier into 1.3.x releases rather than wait for 1.4. No plan to drop support for Maven artifacts, 1.4 should handle Maven artifacts much better (transitive, for one) than 1.3. Putting OSGi ahead just means it might fell more OSGI-like than Maven-like, and might do more fancy things with OSGi bundles than Maven artifacts. Assaf
