Hi Eugene, I think i can summarize the issues i had down to 3 points:
1) Generated source files are not included in the project classpath. I have got round this by manually adding the jar to the project libraries. 2) Maven executed from eclipse seems to run differently from maven on the command line. If you could just confirm that the actual build process is the same but with different logging output i'd be happy with that. 3) Can't do recursive builds on multi-module projects. I'm guessing this has definitely been answered before but i just threw it in. I'm not really too bothered about 2 & 3 but was looking for confirmation on the behavior seen in 1 and whether this was already known about or whether a jira should be opened. More than happy to open one but didn't want to until i'd checked with you first. Thanks Ca, On 7/27/07, Eugene Kuleshov <[EMAIL PROTECTED]> wrote: > Cameron, > > I am having hard time to crawl trough all your issues, but some of > this stuff seem familiar. So, first of all please try the last dev > build, because some things could be already fixed there. Also, some of > your questions already answered in the project FAQ. > > For the other unresolved issues please fill in bugs in project JIRA. > See some hints up here: > http://docs.codehaus.org/display/M2ECLIPSE/How+To+Report+Issues > > Thanks > > Eugene > > > Cameron Jones wrote: > > Hi, > > > > I've setup an eclipse project using maven for some simple web > > services, i have a web module which contains the services themselves, > > a client module which generates the stubs using the wsdl and i have my > > first subscriber of the client module for interacting with the > > service. > > > > This all works great outside eclipse and the whole project builds, > > tests and installs correctly, the problem i have is that the > > subscriber module which depends on the client module does not pick up > > the generated classes in the client jar, they definitely exist and are > > present on the classpath when using maven on the command line but > > eclipse can never resolve them. I think this is because the eclipse > > maven plugin is using the source directory of the client for the > > classpath (which is empty) instead of the generated jar file. > > > > This is a pretty convoluted case which is why i'm not that surprised > > that it appears unsupported, i guess i'm wondering if this is expected > > behavior and if you plan to change it at any point in the future? > > Without being an arse, i've found that the eclipse plugin uses maven > > differently than on the command line... to such an extent that quite > > regularly operations which work on the command line fail in eclipse. I > > now only use maven on the command line so i know it's the same as the > > build machines. Is this expected or have i got the wrong end of the > > stick? > > > > One thing that's a bit annoying is how you can't do a full install > > from a parent module in the eclipse plugin - it defaults to > > non-recursive and there doesn't seem to be a way to override it. > > > > Thanks, > > Cam > > > > --------------------------------------------------------------------- > > To unsubscribe from this list please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
