Hi all, I have been trying to investigate how practical it is to build eclipse plugins using maven, and have run into some conceptual issues which are not explained at all in any of the docs I have found.
So far, the pde-maven-plugin shows the most promise in building an eclipse rcp application. Trouble is, the plugin docs include no explanation whatsoever how dependencies are handled from the maven world to the eclipse world. Maven dependencies are specified in pom files, and maven will eventually build a list of dependent jars, and make these available to the build. What is the eclipse equivalent of dependencies? All docs I have read to date suggest that all eclipse dependencies need to be deployed as plugins, bundled into features. This implies that for every one of my 50 or so dependencies, I have to somehow convert these jars into eclipse plugins. This seems way wrong. I have seen eclipse plugins containing other jars, which starts making more sense. The trouble is that the pde-maven-plugin seems to contain no mechanism to include maven dependency jars into an eclipse plugin, or if this mechanism does exist, it is undocumented. Can anyone shed more light on how this all works? Regards, Graham -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
