David Jencks wrote:
>> I'm not sure I agree that this is easiest or best. I think I would be >> interested in getting others' input on this as well. One of the >> problems we have now is the chicken/egg issue with the plugin being in >> the build itself. I think this would be alleviated by moving the plugin >> to its own project and push it out as a reliable dependency for the >> geronimo project. I have tried the internal plugin thing on a few >> projects, and it always ended up making life easier having the plugin as >> its own project. > > Aren't all these problems due to maven not handling this rather obvious > and important use case of building a plugin and then using it in the > same build? If a tool is broken you have to do something to fix it.... > but often fixing the tool works best. Have you opened a JIRA over on the maven side of the house? > > thanks > david jencks >> >>> --jason
