Make each module into a maven project and release them to your local artifact repository... Then you can define the dependencies just like all the other projects.
On Thursday, 21 November, 2002 22:56, Ciaran Treanor wrote: > Hi, > I'm completely new to Maven so I hope I'm not way off track. > > I've got a project with a number of elements (each in a separate CVS > modules). Here's an example: > - mod-database: > The abstract database model. It's used by the rest of > the system to communicate with the database (regardless of the > specific database server). > - mod-sqlserver: > This is a concrete instance of the abstract model (mod-database) > that is tuned specificall for MS SQLserver. > - mod-mysql: > Ditto, but for MySQL. > > Now, mod-sqlserver (and mod-mysql) require mod-database in order to > compile. Using Maven is it the responsibility to ensure that the > latest mod-database.jar is always available in the Maven repository > *or* > is there some way to specify a <dependency> in the Maven project.xml > for mod-sqlserver that identifies another CVS module (mod-database) > that must be checked out in order to build mod-sqlserver. > > For example: > # cvs co mod-sqlserver > # cd mod-sqlserver > # maven jar > INFO: mod-sqlserver requires mod-database > INFO: Checking mod-database out from cvs > INFO: cd ../mod-database > INFO: maven jar > INFO: cd ../mod-sqlserver > INFO: maven jar > > You get the idea? Is there any way of doing this kind of thing? > > Thanks, > ct -- Michael McCallum Software Engineer SnapHire Inc. http://www.SnapHire.com/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
