|
From: Marziou, G. <gae...@hp...> - 2007-06-07 12:28:24
|
OK, thanks I agree that your approach is safer. it's just that when you browse the repository inside artifactory you can't see the exclude patterns, so some users can be confused when seeing the artifacts. =20 Gael ________________________________ From: art...@li... [mailto:art...@li...] On Behalf Of Yoav Landman Sent: Wednesday, June 06, 2007 10:20 PM To: art...@li... Subject: Re: [Artifactory-users] excludePatterns and previously cachedartifacts =09 =09 Just to clarify - artifactory will not serve you back an artifact that has become excluded or went outside the include scope, even if it has been previously cached. =09 =09 On 6/6/07, Jorg Heymans <jor...@gm...> wrote:=20 On 6/6/07, Marziou, Gael <gae...@hp... > wrote:=20 So, the question is now what should be ArtiFactory behavior: should it flush the excluded artifacts (org/springframework/**) from repo1? =09 >From my experience it does not but I think it should. I don't think flushing is necessary. The exclude filter will make sure that the configured repo1 is never contacted for org/springframework requests. If you reenable it afterwards it has to go and search the artifacts again, suboptimal.=20 =09 Also imagine company internal artifacts that have been published there, if someone makes a typo on an exclude filter all your artifacts might get zapped ! =09 Regards Jorg =09 =09 ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now.=20 http://sourceforge.net/powerbar/db2/ _______________________________________________ Artifactory-users mailing list=20 Art...@li... =09 https://lists.sourceforge.net/lists/listinfo/artifactory-users =09 =09 |