Sure, I was going to add that, as well as update the README.txt...
pending approval of the changes.
That script would just facilitate the multi-stage build... and is not
intended to be a replacement for invoking mvn directly.
BUT, we can use build[.bat] to provide users with a one command
method to execute a full build.
--jason
On Jul 1, 2006, at 2:58 AM, Aaron Mulder wrote:
Call me crazy, but cant we have a build.bat and build.sh in the root
directory that executes the multi-stage builds (modules, plugins,
OpenEJB if present, apps, assemblies, etc.)?
Thanks,
Aaron
On 6/30/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
I also think we need another pre-stage that will build a few tiny
extensions used by the other stages. Specifically a test-config
module that sets up a common log4j.properties that is used by all
tests. When we get a site build running then we also will need
something similar for clover and checkstyle and other plugins.
NOTE: This can be a pre-stage or can be the start of the separate
build-support (or whatever we call it) tree, which will contain the
standalone plugins and other modules that our builds need to
function.
--jason
> So, my proposed build procedure:
>
> build modules + plugins
> go somewhere else and build openejb
> build apps + configs + assemblies
>
> The proposal of using snapshots of openejb from a repo prevents you
> from doing a clean build and finding out that in fact you created a
> problem in either openejb or configs/assembly.
>
> This 3 step process will prevent us from interspersing the modules
> and configs builds which might be highly desirable to make our
> dependency tracking the same as the maven dependency tracking.
> Cant get everything :-(
>
> thanks
> david jencks
>
>>
>> --jason
>>
>>
>
