Re: [Artifactory-users] excludePatterns and previously cached artifacts

[Yoav L. <yla...@gm...>]

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.

On 6/6/07, Jorg Heymans <jor...@gm...> wrote:
>
>
> On 6/6/07, Marziou, Gael <gae...@hp...> wrote:
> >
> >
> > So, the question is now what should be ArtiFactory behavior: should it
> > flush the excluded artifacts (org/springframework/**) from repo1?
> >
> > >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.
>
> 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 !
>
> Regards
> Jorg
>
>
> -------------------------------------------------------------------------
> 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.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Artifactory-users mailing list
> Art...@li...
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>