Am 26.11.2013, 22:02 Uhr, schrieb Robert Scholte <[email protected]>:
In addition to this story: There's an open issue called MDEPLOY-118 which describes a related issue: how to release the same version for different platforms?
Related there is also the need for "features". Larger projects typically have a lot of optional dependencies but dont help to requesat a specific subset. For example a Scheduler like Quartz offers a core engine but also EJB APIs or a Servlet manager implementation. In an ideal world the project would be split into multiple artifacts, but even then there can be a complexity explosion. Depending on the "core scheduler" feature of "quartz" would then skip all optional dependencies (like servlet and EJB API).
(This is similiar to the testing scope, which could be implemented as a well known "feature"). And this also goes in line with platforms/implementations: the "jdk1.4" feature can depend on a concurrent-backport wherees the java7 does not.
Gruss Bernd --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
