Hi,
> You can always add dependencies directly to the plugin node, but this
> assumes that you have the artifacts available in your repo.
>
thats no opinion, because there are no artifacts available (but I could
possibly create some...)
> You're going to need to provide more information about these external
> jars, I think, for us to help you much.
>
I'm creating a bunch of eclipse plugins for a rcp application packaged
in an ear application for glassfish. When keeping this parts (client and
server) seperated it is quite easy. Build eclipse parts with eclipse and
the ear with maven, but I woule like to create everything with maven.
My idea was to add the eclipse install directory to a custom mojo which
consists of two goals:
1) In phase process-resources the plugin.xml, MANIFEST.MF and other
plugin resources would be copied to the target location.
2) During the compile phase the jars from <eclipse-root>/plugins would
be added to the compiler. (It could be extended to only add the plugins
required by the plugin).
When adding the eclipse dependencies to the POM (statically) and then
recreating the eclipse project, the dependencies are duplicated. Once in
plugins-dependencies (managed by ecipse throught the manifest) and once
because maven adds them to the eclipse dependencies.
Is there a way to accomplish what I want to do?
Thanks
Markus
--
__________________________________
Markus Wolf
Wedeler Landstrasse 63
22559 Hamburg
tel: (+49) 40 / 550 083 70
mob: (+49) 177 / 288 48 67
web: http://www.matrixweb.de
icq: #109622365
pgp: http://wwwkeys.de.pgp.net
__________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
