No, I have the parent tag (example in my first mail), the problem is finding the parent pom if it is not available locally.
If I checkout the entire multi-project and 'mvn install' from the parent project it works as expected, all subprojects are packaged and installed in the local cache. I am able to run, for example, 'mvn compile' from any of the subprojects and the parent pom dependency will be resolved from the local cache. I can even remove all projects and then checkout only a single subproject, maven tasks still work because the parent pom is still in the local cache. What I would like to do is allow other developers to checkout just a single subproject and start working on it separately without needing to do anything else. My hope was that when 'mvn compile' would be run in this subproject, and the parent pom was not found in the local cache, that maven would then search through the repositories and mirrors. I believe that our repositories and mirrors are set up correctly because other dependencies are resolved through them. Are poms resolved differently? Is a parent pom resolved in a different way than jar or pom dependencies? Am I missunderstanding the purpose or possibilities of multi-project builds? Please note that my main goal is to centralize configuration and not necessarily trigger builds of subprojects, am I approching this wrong? Thanks again, Matt -----Original Message----- From: javed mandary [mailto:[EMAIL PROTECTED] Sent: 22. februar 2006 11:40 To: Maven Users List Subject: Re: Multi-project woes Hi Matt, if i understand correctly you have defined the child modules but have you defined the parent of of your child modules inside of the child module POM files ? In each child module POM there needs to be something like this: <project[.... ] <parent> <groupId>com.package.name.of.parent</groupId> <artifactId>parent</artifactId> <version>parentversiion</version> </parent> [....] Note: Child modules will inherit all the dependencies associated in the Parent POM. regards, Javed On 2/22/06, Koranda Matthew James <[EMAIL PROTECTED]> wrote: > > Ok, so maven will not fetch a parent pom from a repository? > > And the error is nothing fancier than the pom cannot be found in any > repository. I guess I am just using maven wrong but I would like to be > able to work on a subproject without having to fetch all of the "sibling" > projects, but still have a central place to add all of the common settings. > Is there another method for this? The projects are of a logical > grouping but don't necessarily have dependencies on one another. > > Matt > > > -----Original Message----- > From: Alexandre Poitras [mailto:[EMAIL PROTECTED] > Sent: 21. februar 2006 17:37 > To: Maven Users List > Subject: Re: Multi-project woes > > Maven should find your parent without any problem. However, you have > to understand that when you want to compile or anything, you should > run the command on your parent project so all the inter-projects > dependencies are resolved. Maven will then be able to figure the order > in wich compile the children projects. Other then that your poms files > seem fine and your directory names too. Please post the error message if you > need more help. > > On 2/21/06, Koranda Matthew James <[EMAIL PROTECTED]> wrote: > > I have made a multi-project setup with a standard structure: > > > > project > > --- subproject A > > --- subproject B > > > > The project itself is quite big and the subprojects are components > > that are usable by the main project. I have added all of the common > > information to the project pom.xml as follows: > > > > <project> > > <modelVersion>4.0.0</modelVersion> > > <groupId>com.a.b</groupId> > > <artifactId>main</artifactId> > > <packaging>pom</packaging> > > <version>1.0-SNAPSHOT</version> > > <name>Company</name> > > <url>http://www.url.com</url> > > <inceptionYear>2006</inceptionYear> > > <modules> > > <module>subprojectA</module> > > <module>subprojectB</module> > > ......... > > > > And in the subprojects: > > > > <groupId>com.a.b.subprojectA</groupId> > > <artifactId>subprojectA</artifactId> > > <packaging>jar</packaging> > > <version>1.0-SNAPSHOT</version> > > <name>Subproject A</name> > > <url>http://maven.apache.org</url> > > <parent> > > <groupId>com.a.b/groupId> > > <artifactId>main</artifactId> > > <version>1.0-SNAPSHOT</version> > > </parent> > > > > > > We are using eclipse as our IDE and the heirarchal structure is > > clumsy with so many subprojects so we are trying to check out just > > the subprojects from source control. The problem is that our > > subprojects are unable to resolve the main pom from any repository, > > is this expected with the way we are trying to use it? > > > > We are also using maven-proxy and continuum. Both continuum and our > > local workstations are able to resolve dependencies such as maven > > plugins using the maven-proxy but fail finding our internal pom. > > Both work if I install the main pom in the local cache but I would > > like to be able to checkout a subproject and "mvn compile". Is this > > possible in this way? > > > > > > Thanks in advance, > > > > Matt > > > > > > > -- > Alexandre Poitras > Québec, Canada > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
