That would be the idea, yes (not sure if we need to fork lifecycles though). Get the "trunk" of any given plugin and have all dependencies checked out and compiled at trunk too seems to be the default mode of operation.
As for source, there is none, we're still cooking the ideas. But I expect to start coding something soon ;) Kristian 2012/9/16 Mark Derricutt <[email protected]>: > A thought... > > If I run "mvn clean install" from the top-level pom containing the > git-workspace-plugin, are we intending to fork each of those lifecycles in > reactor-resolved-order for all the modules in the git-workspace? > > That would be uber-awesome. > > On 14/09/2012, at 2:16 AM, Kristian Rosenvold <[email protected]> > wrote: > >> I have just added wiki document to discuss the design of a totally new >> plugin I have dubbed the "git-workspace-plugin". >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
