That's one step to change. If you want to move to m2 exclusively, then geronimo would have to <exec /> m2 instead of however it calls the original maven goals on it. shouldn't be a hard change.
I guess the issue there is complicating an already overcomplicated build process for Geronimo... Another crazy idea is to write a Maven 1 plugin that uses Jason's embedder to run m2. That's probably achievable and a preferred solution. I'll look into it. Is it the opinion of the group to switch to m2 exclusively, or is there something else that needs to happen first? Thanks, Brett Aaron Mulder wrote: >So currently the Geronimo (Maven 1) build can build OpenEJB at the >same time if you check it out and do a multiproject build. Would that >still work if OpenEJB moved to M2 exclusively? > >Aaron > >On 10/1/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > >>Hi, >> >>The Maven 2 build for OpenEJB is complete. >> >>There is a readme in the m2 subdirectory. Basically it runs some scripts >>to copy POMs and reorganise in a subdirectory. It pulls geronimo JARs >>from your maven 1 local repository. >> >>Currently a build of all of openejb (including tests) takes 1m 30s on my >>machine, 17s with tests skipped. The majority of that is the xml beans >>plugin which currently re-executes even if the schemas haven't changed. >> >>Can folks test this and see if it is complete? >> >>What should be the process be for incorporating this into the trunk as >>the primary build? Is that something wanted at this stage? >> >>- Brett >> >> >> > > >
