Martijn Dashorst wrote on Wednesday, July 05, 2006 4:58 PM: > All, > > If you have a project setup where all your projects have a common > parent project, and some are dependend on the others, how can you > accomodate the downloaders of your assemblies such that they still can > build your project using maven if/when they are offline? > > Example setup: > <project> > <groupId>foo</groupId> > <artifactId>foo-parent</artifactId> > <version>1.0-SNAPSHOT</version> > <packaging>pom</packaging> > </project> > > <project> > <parent> > <groupId>foo</groupId> > <artifactId>foo-parent</artifactId> > <version>1.0-SNAPSHOT</version> > </parent> > <artifactId>bar</artifactId> > <packaging>jar</packaging> > </project> > > The first problem is the parent pom. Is the snapshot version of the > parent pom updated when I build the bar project?
No. Currently no SNAPSHOT is *ever* updated (parent or dependency) if one is available locally. Vote for MNG-1908 ;-) > > How should I construct my (source) assembly for bar, such that it can > be compiled using maven, even when the foo-parent pom is not available > on the central repo (usually the case for snapshot versions)? Add > (somehow) the foo-parent.pom to the assembly and provide README > instructions to perform an install first on the parent pom? > > Martijn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
