Hello I am sure this question must have been asked several times but I really searched for an answer in here as well as with google etc and found nothing sophisticating. It might be related with me being quite new in the maven world and maybe do not really know what I want to know :-)
But now to my question: In our project we have a classic server client application (nothing special on server side .. pure old java with tibco for our communication). The client is an Eclipse RCP application built on version 3.3.1 which has several plugins. Here are my fist difficulties: Is the client one project in maven or a multi module project which has for each plugin a project like it is in eclipse itself? I choose the second choice because the first would end in a huge project which will make testing a pain in the *** and with the second one we can add common projects which are shared between server and client easily as plugin in the client and as jar in the server. With the maven-eclipse-plugin it works just fine with the manifest generation but I have real difficulties with the dependencies to the RCP Libraries/Plugins ... I tried the way explained on codehaus (http://docs.codehaus.org/display/MAVENUSER/Eclipse+Plugin) but it did not work :-( Is this the correct way to go and I just have to solve my last dependency problem or am I completely off? I ask this because I have seen solutions which only use the pde build which is in my opinion the wrong stage: The pde build is something for installation/deployment and should be used at the end for integration tests AFTER compilation and unit tests. Why? Unit tests should be quite fast (just several seconds) which is not possible if they depend on the pde build. I hope somebody can point me the right direction or could show me an other project with a similar build up. thanks in advance greets Michael --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
