Well, the thing about the repository is that it's stored in my user's directory, which is way too global for me. The only solution I suppose to make my local repo under my main target directory.
In the multiproject plugin, multiproject:install is not a default goal. That's pretty confusing. A. -----Original Message----- From: Milos Kleint [mailto:[EMAIL PROTECTED] Sent: Saturday, April 09, 2005 1:12 AM To: Maven Users List Subject: Re: Migrating to Maven well, AFAIK that's the way multiproject build works. I'm not aware of a way to do the build without the local repository loop. Why don't you want to install the artifacts? Milos On Apr 9, 2005 1:05 AM, Anil Arora <[EMAIL PROTECTED]> wrote: > I set up my multiproject using the dependency as specified, but I get > the following error when it's trying to build the second subproject: > > +---------------------------------------- > | Generating site for interlace.db > | Memory: 42M/55M > +---------------------------------------- > Attempting to download interlace.util-2.2-SNAPSHOT.jar. > WARNING: Failed to download interlace.util-2.2-SNAPSHOT.jar. > > The only way to fix this was to call multiproject:install, which copies > the jar file into my local repository. But I don't want it to install > the jar into the repository. > > Anil > > -----Original Message----- > From: baleineca [mailto:[EMAIL PROTECTED] > Sent: Friday, April 08, 2005 7:30 PM > To: Maven Users List > Subject: Re: Migrating to Maven > > Anil Arora wrote: > > And with multiproject, the > > dependency version should be centralized. I guess the only way to do > > this is to use the jar override mechanism. Also, I cannot figure out > > how to correctly get the dependencies between projects to work. It's > > says it cannot download the jar file. > > > > I have a project with sub projects and the version is "centralized" in a > > way, as it is defined in the top level project.xml that the sub projects > > inherit with <extend> tag (the sub projects don't define the version in > their own project.xml). > > The dependencies are defined as follows, and because the reactor > determines the order of the build (I use a custom reactor build, but I > think this should also happen with multiproject), the dependencies work > out fine. No jar override is used. > > <dependency> > <groupId>${pom.groupId}</groupId> > <artifactId>someArtifact</artifactId> > <version>${pom.currentVersion}</version> > </dependency> > > --------------------------------------------------------------------- > 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]
