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
