My apologies about the site plugin, I will look into adding a check to the release plugin to prevent that in future.
As soon as the hardware outage is over, I will fix the doxia problem. The Jetty problem should be referred to the Jetty team (they are a codehaus project). - Brett On 5/15/06, Borut Bolčina <[EMAIL PROTECTED]> wrote:
This hack works, but not all the way! There is another reference to http://snapshots.maven.codehaus.org/maven2 in .m2\repository\org\mortbay\jetty\jetty\6.0.0beta12\jetty-6.0.0beta12.pom <pluginRepositories> <pluginRepository> <id>snapshots</id> <url>http://snapshots.maven.codehaus.org/maven2</url> </pluginRepository> </pluginRepositories> but jetty-6.0.0beta12.jar did not make it to ibiblio yet. Does anybody has this jar? Is this to be reported too? Regards, Borut Olivier Lamy pravi: > Try the hack, add this in your settings.xml > > <mirror> > <mirrorOf>snapshots</mirrorOf> > <name>snapshots codehaus hack</name> > <id>snapshots codehaus hack</id> > <url>http://www.ibiblio.org/maven2/</url> > </mirror> > > It's a temporary solution. (not tested but AFAIK should work because doxia-site-renderer-1.0-alpha-8 is a release and all needed artifacts must be in ibiblio). > > Perso, I have made : > <mirror> > <mirrorOf>snapshots</mirrorOf> > <name>proxy maven2 snapshots</name> > <url>http://${ip}:${port}/maven-proxy-snapshots/maven2/</url> > </mirror> > > http://${ip}:${port}/maven-proxy-snapshots/maven2/ is a internal corporate maven-proxy wich has link to : > - codehaus snapshots > - cargo snapshots > - apache snapshots > - corporate snapshots > > This is a better solution. > > - Olivier > > -----Message d'origine----- > De : Weichsel, Ingo [mailto:[EMAIL PROTECTED] > Envoyé : lundi 15 mai 2006 12:56 > À : Maven Users List > Objet : RE: repo down? > > > Hi, > > the doxia-site-renderer-1.0-alpha-8.pom does defines repositories, > > <repositories> > <repository> > <id>snapshots</id> > <url>http://snapshots.maven.codehaus.org/maven2</url> > </repository> > </repositories> > > which can't be resolved. Any idea, if this will be fixed quickly, or do we have to stick to the older plugin versions? > > Ingo > > >> -----Original Message----- >> From: Xavier Frisaye [mailto:[EMAIL PROTECTED] >> Sent: Monday, May 15, 2006 12:00 PM >> To: Maven Users List >> Subject: RE : repo down? >> >> In my case, this is doxia referenced by the new site plugin >> (2.0-beta-5) that causes the problem and i solved by adding >> this to my pom : >> >> <plugin> >> <groupId>org.apache.maven.plugins</groupId> >> <artifactId>maven-site-plugin</artifactId> >> <version>2.0-beta-1</version> >> </plugin> >> >> Xavier >> >> -------- Message d'origine-------- >> De: Emmanuel Venisse [mailto:[EMAIL PROTECTED] >> Date: lun. 15/05/2006 11:52 >> À: Maven Users List >> Cc: >> Objet: Re: repo down? >> >> >> >> >> >> Markus Reinhardt a écrit : >> > Am Montag, den 15.05.2006, 11:20 選 schrieb Jörg Schaible: >> > >> >>Geoffrey De Smet wrote on Monday, May 15, 2006 10:26 AM: >> >> >> >>> Ibiblio is up, but the dns server of maven.org >> seems to be down. >> >>> >> >>> Brett Porter wrote: >> >>>> >> http://maven.apache.org/guides/mini/guide-mirror-settings.html >> >>>> >> >>>> Yes, it's down. Unscheduled, and beyond our control, sorry. >> >> >> >>But, since the new plugin releases refer to artifacts >> only available in snapshots.maven.codehaus.org/maven2, our >> complete development comes to a sudden stop, because of the >> automated update. Please, make sure for such releases, that >> all artifacts are available at ibiblio (which is at least mirrored). >> >> >> > Who do I to tell maven not to search for updates? >> Neither -o nor -npu >> > switches help. All needed plugins >> (tomcat-maven-plugin:pom:1.0-SNAPSHOT) >> > are located in my local repo. >> >> You should add <updatePolicy>never</updatePolicy> in >> repository definition in your pom or in a profile. >> >> http://maven.apache.org/ref/current/maven-model/maven.html#cla >> ss_snapshots >> >> Emmanuel >> >> >> >> --------------------------------------------------------------------- >> 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] > > > > This e-mail, any attachments and the information contained therein ("this message") are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. > -------------------------------------------------------------------------------------------------------------- > Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après "le message" ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. > ------------------------------------------------------------------------------------------------------------- > > > --------------------------------------------------------------------- > 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]
