the reason to make module name to have the same name as artifactId is so that you dont have define your scm element in every child pom. All Maven needs to the top pom.xml's scm to figure out out scm element of the child module. this is crucial when cutting a release the maven way using its infamous maven-release-plugin
if you have lots of modules, this convention is very handy. -Dan On Wed, Dec 2, 2009 at 9:33 PM, Alexander <[email protected]> wrote: > Yeah, thats right. > > There are some problems? > > 2009/12/3 maven apache <[email protected]> > >> 2009/12/3 Alexander <[email protected]> >> >> > Maven way is to name module directory as module artifact id. >> > >> I want to rename the module since the old project are not well named.So I >> should rename both the module directory and module artifact id? >> >> > >> > 2009/12/3 maven apache <[email protected]> >> > >> > > Hi: >> > > I want to know how do maven find the module of the parent project: >> > > for example in the root project whose packaging is pom and the >> directory >> > is >> > > C:/project, I define the following modules: >> > > ----- >> > > <module>maven</module> >> > > <module>platform</module> >> > > <module>main</module> >> > > -------------- >> > > So the module "maven" should be a directory under the C:/project/maven >> or >> > > the directory contains module "maven" can be named as others and its >> > > artifactId should be "maven"? >> > > >> > >> > >> > >> > -- >> > Regards, >> > Alexander >> > >> > > > > -- > Regards, > Alexander > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
