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]
