FWIW, Maven, Nexus and probably Archiva also do the same if you enable strict checksum checking. It can be debated which default is less disruptive but ultimately the choice is up to the user to set it the way they prefer.
On Fri, Nov 13, 2009 at 4:07 PM, Yoav Landman <[email protected]> wrote: > When using Artifactory this scenario can be circumvented, as we never let > bad poms pass through, so you won't end up with html pages in your > repository when a remote repository is broken. > > On Thu, Nov 12, 2009 at 11:53 AM, Lahiru Gunathilake <[email protected]>wrote: > >> Hi Stephan, >> >> Actually this is not about building the products in my machine, we are >> suppose to host our source packs and let users to download it and build it >> in their machines. So a the build should go smoothly and should not stuck >> due to relocation of java.net repository. >> >> Let me explain the situation, before that I would say this is a kind of a >> bug in maven, simply because maven does not skip taking an artifact if one >> of the maven repo sends a 301(MOVED PERMANANTLY) and it simply take that >> message and write it as the pom file. Simply if the maven repo sends 404 it >> skip that repo and go for another, but here with 301 it just dump the >> message as the pom file and later on this failes. >> >> In our build system we are not refering this java.net repository in any >> location but maven itself go for the java.net repo, so please be kind >> enough >> to help to fix this. >> >> I have only one solution for the time being, which is configuring >> java.netrepository not to send 301 and send 404. I can simply patch >> the maven, to >> handle this scenario but we are stuck with our release process due to this >> issue since our products are open source. >> >> Lahiru >> >> On Thu, Nov 12, 2009 at 2:10 PM, Stephen Connolly < >> [email protected]> wrote: >> >> > Use a repository manager and have it proxy everything. that way you can >> > just to mirrorOf>*< in your settings.xml. It will merge all repositories >> and >> > everything just works(TM) >> > >> > >> > 2009/11/12 Lahiru Gunathilake <[email protected]> >> > >> >> Hi Stephen, >> >> >> >> I tried with a clean repo, but didn't worked for me. I have encountered >> >> this repository failures time to time. So we have our own repository >> where >> >> we host our artifacts. Now I want to add all these third party artifacts >> I >> >> used to build the product stack to our own repository. Is this possible >> to >> >> do and do the build products by adding our repository in to the pom.xml >> of >> >> Apache projects we are building. >> >> >> >> Can you please tell me how to host those third party artifacts in to our >> >> own repository. >> >> >> >> Lahiru >> >> >> >> >> >> On Thu, Nov 12, 2009 at 1:58 PM, Stephen Connolly < >> >> [email protected]> wrote: >> >> >> >>> >> >>> >> >>> 2009/11/12 Lahiru Gunathilake <[email protected]> >> >>> >> >>>> Hi Stephen, >> >>>> >> >>>> >> >>>> On Thu, Nov 12, 2009 at 12:10 PM, Stephen Connolly < >> >>>> [email protected]> wrote: >> >>>> >> >>>>> AFAIK, >> >>>>> >> >>>>> Axis2 is an apache project and would be deploying to repo1.maven.org >> . >> >>>>> The rules for repo1.maven.org are that you cannot rely on any >> >>>>> artifacts which are not hosted on repo1.maven.org. >> >>>>> >> >>>> I think there were artifacts hosted and now it's moved. >> >>>> >> >>>> repo1.maven.org is write-once >> >>> >> >>> artifacts cannot be removed from repo1.maven.org >> >>> >> >>> >> >>>> As such, I would expect that Axis2 _should not_ require artifacts >> from >> >>>>> java.net, and should not have any <repository> sections in their >> >>>>> pom.xml files. >> >>>> >> >>>> Yes axis2 doesn't have any repository section in it's pom files but >> when >> >>>> I manually add the relocated repo in to the Axis2 pom it successfully >> get >> >>>> some of the artifacts and later on it again refer to the wrong >> location and >> >>>> get a html content in the the pom file. please refer the error >> here[1]. >> >>>> >> >>> >> >>> sounds like your local repository is corrupted. blow away >> >>> ~/m2/repository/org/apache (or move it to a temporary location) >> >>> >> >>> >> >>>> (OK technically they are allowed ones which are only >> >>>>> enabled for -SNAPSHOTs... but it cannot be enabled for releases) >> >>>>> >> >>>>> That is the theory, now it may well be that Axis2 is being bold and >> >>>>> depending on java.net. >> >>>>> >> >>>>> To answer your question. Your best bet is to set up a maven >> >>>>> repository manager (e.g. nexus, artifactory, etc) and configure your >> >>>>> settings.xml to use that repository manager as <mirrofOf>*</mirrorOf> >> >>>>> >> >>>> I will try for this and get back to you. >> >>>> >> >>>> >> >>>> [1]http://www.pastie.org/694974 >> >>>> Thanks in advance >> >>>> Lahiru >> >>>> >> >>>>> >> >>>>> Then you can add all the repositories you want to source artifacts >> >>>>> from to your repository manager, and you should be able to build. >> >>>>> >> >>>>> Also this sounds more like a question for the Axis2 list >> >>>>> >> >>>>> -Stephen >> >>>>> >> >>>>> 2009/11/12 Lahiru Gunathilake <[email protected]>: >> >>>>> > Hi all, >> >>>>> > >> >>>>> > I am trying to build set stack of java products which fails due to >> >>>>> the >> >>>>> > relocation of >> >>>>> https://maven-repository.dev.java.net/nonav/repository/. From >> >>>>> > the product stack I am buiding Apache Axis2 very first and I cannot >> >>>>> see this >> >>>>> > repository in Axis2 pom.xml. So I tried to put the new location in >> to >> >>>>> Axis2 >> >>>>> > pom and tried to build but still it's failing with some other >> >>>>> artifacts. I >> >>>>> > wanted to change the location where we artifacts pointing to this >> >>>>> location, >> >>>>> > so I ran a grep command inside my .m2 directory but I couldn't find >> >>>>> any of >> >>>>> > the .pom file where it refer to this repository. >> >>>>> > >> >>>>> > I'm ahead of a release and have to do a clean repository build, so >> >>>>> can >> >>>>> > someone please help me to avoid this problem. >> >>>>> > >> >>>>> > Regards >> >>>>> > Lahiru >> >>>>> > >> >>>>> > -- >> >>>>> > Apache Qpid, Worlds dominant messaging middleware..!!! >> >>>>> > >> >>>>> >> >>>>> --------------------------------------------------------------------- >> >>>>> To unsubscribe, e-mail: [email protected] >> >>>>> For additional commands, e-mail: [email protected] >> >>>>> >> >>>>> >> >>>> >> >>>> >> >>>> -- >> >>>> Apache Qpid, Worlds dominant messaging middleware..!!! >> >>>> >> >>> >> >>> >> >> >> >> >> >> -- >> >> Apache Qpid, Worlds dominant messaging middleware..!!! >> >> >> > >> > >> >> >> -- >> Apache Qpid, Worlds dominant messaging middleware..!!! >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
