There are quite a number of users who want this functionality and the corresponding ability to build a plugin from the same reactor as it is consumed in.
Usually this is due to lazyness, ie not wanting to cut a release of a plugin/extension just to make the build... Iow the use case were somebody "would like to write a one off script, but instead does the maven way and writes a one off plugin/extension" The other use case is eg openejb/tomee who have a plugin tied to their release version and don't want to split the build into three release roots (stuff that plugin depends on; the plugin; stuff that needs the plugin) I think we should allow this kind of thing with certain very strict bounds, but I am happy to push back to a new model version (which would allow expressing such stricter bounds) and ok with saying wontfix if we are ok potentially alienating the users who feel they need this (could live with a way to provide a workaround though) On Sunday, 19 January 2014, Jason van Zyl <[email protected]> wrote: > I don't think there are really any valid use cases for trying to build an > extension where it is used in the same reactor. Extensions really need to > be present before the reactor starts and trying to do this is a contortion > I really don't want to support. > > I would like to close this as won't fix. Anyone object? > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > --------------------------------------------------------- > > We know what we are, but know not what we may be. > > -- Shakespeare > > > > > > > > > -- Sent from my phone
