FYI, when we start pushing this pom.xml to central it shouldn't contain any <repositories> or <pluginRepositories> because it's recommended that central poms don't refer to other repos.
The usual practice is to put all repository information in your settings.xml (you can use profiles to switch between settings) so that the actual project remains clean and portable. This does mean that developers need to follow an extra step... On 26/03/2008, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Author: [EMAIL PROTECTED] > Date: Tue Mar 25 18:39:41 2008 > New Revision: 11272 > > Log: > Add OPS4j repos > > Modified: > projects/pax/poms/project/pom.xml > > Modified: projects/pax/poms/project/pom.xml > > ============================================================================== > --- projects/pax/poms/project/pom.xml (original) > +++ projects/pax/poms/project/pom.xml Tue Mar 25 18:39:41 2008 > @@ -75,6 +75,29 @@ > <url>scpexe://www.ops4j.org/var/http/www.ops4j.org/projects</url> > </site> > </distributionManagement> > + > + <repositories> > + <repository> > + <id>ops4j.releases</id> > + <name>The OPS4J Release Repository</name> > + <url>http://repository.ops4j.org/maven2/</url> > + <snapshots> > + <enabled>false</enabled> > + </snapshots> > + </repository> > + <repository> > + <id>ops4j.snapshots</id> > + <name>The OPS4J Snapshot Repository</name> > + <url>http://repository.ops4j.org/mvn-snapshots/</url> > + <snapshots> > + <enabled>true</enabled> > + </snapshots> > + <releases> > + <enabled>false</enabled> > + </releases> > + </repository> > + </repositories> > + > <pluginRepositories> > <pluginRepository> > <id>ops4j.snapshots</id> > > _______________________________________________ > notify mailing list > [EMAIL PROTECTED] > http://lists.ops4j.org/mailman/listinfo/notify > -- Cheers, Stuart
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
