I got myself a fresh clean checkout of trunk and built just the modules. I encountered the following problems -
1. The j2ee module compilation failed due to a dependency on ejb spec jar. 2. The web-builder modules failed compilation due to a dependency on servlet spec jar. I have attached a patch to resolve 1 & 2 above. If others see the same problem too, then we should open a JIRA and apply this patch. 3. All builder modules fail the first time on dependency xmlbeans:xmlbeans-jsr173-api:jar:2.0-dev. The second attempt will succeed. I thought it's exclusion from the stax:stax-api would take care of that. Right now, I don't know why it fails. The build is successful the second time. Cheers Prasad On 6/12/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
Please see comments inline - On 6/11/06, David Jencks <[EMAIL PROTECTED]> wrote: > I'm finding it a bit hard to keep track of the m2 migration status, > so I thought I'd try to put it all on one page. > > > http://issues.apache.org/jira/browse/GERONIMO-1737 : assembly plugin: > no patch. I understand our assembly plugin working requires some bug > fixes in maven. > http://jira.codehaus.org/browse/MASSEMBLY-45 is needed to "flatten" dir structures during assembly. I'll work on this patch. http://jira.codehaus.org/browse/MASSEMBLY-41 can help us extract *-builder-* artifacts for our schemas. Jason to look at this. http://jira.codehaus.org/browse/MWAR-45 is needed to jar up classes into web-inf/lib/classes.jar Patch submitted and applied. http://jira.codehaus.org/browse/MASSEMBLY-116 - ability to use a temp dir and discard it (not include it in zip). Ability to unpack <fileset> too. > assemblies: no assembly plugin, none built. > > I think we're getting moderately close to having a working m2 build. > We currently have our version info hardcoded in all our (150+) pom.xml. Maven JIRA http://jira.codehaus.org/browse/MNG-624 should help us solve that problem. > thanks > david jencks > > > > > > >
missing-deps.patch
Description: Binary data
