Jeremy,
Can you replace the tool used in the assembly module(s) with this
plugin, so I can revise the deploy tool to take out all the server
construction operations?
Also, once a Geronimo is released "into the wild" can this tool be
run at the command line without Maven? And if not, can you provide (or
help someone else provide) a non-Maven wrapper for it?
Thanks,
Aaron
P.S. Dain: kind words. :)
On Wed, 30 Mar 2005, Jeremy Boynes wrote:
> It is self bootstrapping. There is a released version in my home
> directory that can be used to build itself or newer versions of itself.
> Having that seed there eliminates the need to bootstrap every time.
>
> The plugin builds artifacts which are installed inot the maven repo and
> which can be used to build other configuration artifacts just like jars;
> there is no need for a "cold" config store.
>
> Configuration artifacts can be installed anywhere; typically they would
> be user applications that would be installed into a running server.
>
> When building our distribution we just need to get enough running that
> we can talk to its ConfigStore; that can be done by the assembly plugin
> that is generating the final distribution (e.g. by starting a
> LocalConfigStore in-VM pointing to the target directory).
>
> This separation of configuration packaging from assembly not only makes
> things easier for our users, it also makes the build simpler. At the
> same time it allows for multiple assemblies that can use different
> artifacts (e.g. a Jetty assembly vs. a Tomcat assembly).
>
> --
> Jeremy
>
