On Sep 10, 2008, at 12:09 AM, David Jencks wrote:
On Sep 9, 2008, at 11:56 PM, David Jencks wrote:
I looked at the new plugin groups stuff and have a couple ideas/
suggestions.
I'm going to create a framework plugin group. Is there some reason
this won't work?
I'd like to see the plugin groups distributed closer to where their
components are found, e.g. web-jetty in plugins/jetty. Does this
seem reasonable?
I think the car-maven-plugin can use another packaging style for
these plugin groups that will mean we don't have to configure much
of anything for the c-m-p. Maybe we won't need the empty plan
either.
I thought the idea was to use only the plugin groups when
assembling our actual servers. Is this work still in progress? It
looks to me as if we have both a complete list of plugins plus the
plugin groups that would also pull them in.
Also I think we can modify the assemble-server lifecycle to use the
no-dependency-change mojo to check when stuff changes-- in
particular when we just use plugingroups for (most) servers.
Maybe I messed something up but in my new server constructed using my
new framework plugin group the plugin group itself is started. I
think we need to prevent this.... anyone know how?
thanks
david jencks
david jencks
Are there any jiras for this work?
thanks
david jencks
