Ah, that sounds reasonable! I think that must be exactly what the problem is. Thanks a lot for all of the responses, they were all helpful and in the right direction.
Matt -----Original Message----- From: Stephen Duncan [mailto:[EMAIL PROTECTED] Sent: 23. februar 2006 12:36 To: Maven Users List Subject: Re: Multi-project woes A thought (hope I didn't miss this in the discussion somewhere): is your parent version a SNAPSHOT? The "central" repository you are mirroring isn't defined to have snapshots enabled, I think, and therefore your mirror might not work, where a separately defined <repository> would. -Stephen On 2/23/06, Koranda Matthew James <[EMAIL PROTECTED]> wrote: > Yes but my settings.xml is set up with our internal repository as a mirror. I > would think that maven would first check the project path, then the local > repository, and then central and mirrors. Is this incorrect? Should I have > set it up as a repository with a certain profile in my settings.xml instead > of as a mirror? > > Matt > > -----Original Message----- > From: Du,Guo [mailto:[EMAIL PROTECTED] > Sent: 23. februar 2006 11:05 > To: Maven Users List > Subject: Re: Multi-project woes > > I don't think it is a bug. First of all, you need resolve the local parent > project if exist, so you need tell the maven where to look at. The solution > in maven2 is setting the repository in your local settings file, it would > also work without the repository define in every poms. But you will rely on > settings file and cannot running elsewhere without the settings. > > > > Kind regards, > > Du, Guo > > ----- Original Message ----- > From: "Koranda Matthew James" <[EMAIL PROTECTED]> > To: "Maven Users List" <[email protected]> > Sent: Thursday, February 23, 2006 9:45 AM > Subject: RE: Multi-project woes > > > This is actually what made it work! I added a repository tag with our > internal repository to each subproject and it is now working! > > According to the documentation it seems as if this shouldn't be > needed. Is this a bug? > > Matt > > > -----Original Message----- > From: Du,Guo [mailto:[EMAIL PROTECTED] > Sent: 22. februar 2006 12:59 > To: Maven Users List > Subject: Re: Multi-project woes > > You may add your internal repository defination to all the poms so you > could always resolve the dependency and it doesn't depends on the local > settings. > You can easily build all the project any where inside your company. > This would also works well for m2eclipse because it cannot read local > settings by now:( > > > > Kind regards, > > Du, Guo > > ----- Original Message ----- > From: "Koranda Matthew James" <[EMAIL PROTECTED]> > To: "Maven Users List" <[email protected]> > Sent: Wednesday, February 22, 2006 11:46 AM > Subject: RE: Multi-project woes > > > I have a mirror in my settings.xml as follows: > > <mirror> > <id>maven-proxy</id> > <name>Maven-Proxy Mirror</name> > <url>http://mydomain:9999/repository/</url> > <mirrorOf>central</mirrorOf> > </mirror> > > This points to my internal repository which is served by maven-proxy. > The poms and jars are deployed to this installation from source > control on the remote server and other jar dependencies are resolving > correctly from this repo. > > I don't have a <repositories> tag in any of my poms. Is this asn > incorrect way to set it up? > > Matt > > -----Original Message----- > From: Stephen Duncan [mailto:[EMAIL PROTECTED] > Sent: 22. februar 2006 12:27 > To: Maven Users List > Subject: Re: Multi-project woes > > Is the repository information defined in the parent POM? Do the child > POMs have all the information they need to retrieve the parent POM > from your remote repository? > > Usually my parent POM has the definition of the repositories, so, to > get the parent the first time, I have to define the repositories in my > settings.xml. > > See: > http://maven.apache.org/guides/mini/guide-multiple-repositories.html > > -Stephen > > On 2/22/06, Koranda Matthew James <[EMAIL PROTECTED]> wrote: > > 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] > > > > > > > -- > Stephen Duncan Jr > www.stephenduncanjr.com > > --------------------------------------------------------------------- > 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] > > > --------------------------------------------------------------------- > 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] > > -- Stephen Duncan Jr www.stephenduncanjr.com --------------------------------------------------------------------- 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]
