Doug Douglass wrote:
This may be slightly off topic, if so, any pointers to whom to ask are appreciated.
I'm trying to convert a project with a simple shell script build (producing two jar artifacts) to use maven. The project is a fairly simple proxy using RMI, so my thinking was to have three separate sub-projects:
/parent /client /common /server
Each sub-project (client, common, server) extends the parent project.xml. The common sub-project defines the interfaces for the RMI proxy objects and some utility classes, both the client and server sub-projects have the common sub-project as a dependency. The server sub-project has classes that implement the RMI interfaces and is using a postGoal in maven.xml to generate both the source and compiled classes for these remoting classes using rmic.
My problem is that the client sub-project artifact needs to include the *_Skel classes generated by rmic in the server sub-project.
If I understand you well the only problem is to to have server classes on classpath when running client. You don't have to include this classes in client jar.
Is there a better layout I should be considering for this project? I suppose I could just have two projects, client and server,
TIA, Doug
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
