Is there a strong reason anymore to have this class? It is heavily used so we're stuck with it for a while, but for new code DirectoryStream is in the JDK 7+ and is likely to be better supported, less buggy, and more familiar to new developers.
If there's an actual bug or missing documentation in DirectoryScanner, then we can fix it. Otherwise I'm inclined to leave it alone. https://docs.oracle.com/javase/7/docs/api/java/nio/file/DirectoryStream.html On Tue, Jun 9, 2020 at 3:54 AM Romain Manni-Bucau <[email protected]> wrote: > > Hi everyone, > > As you know, DirectoryScanner is used a lot in plugins. > Today I realized that plexus impl does not respect exclusions in the visit > but only in the result, it means if you exclude **/target/** and include > **/*.java, it will visit target to see if there is any java (cause ** means > java can be in target). > I did a quick fix for license-maven-plugin ( > https://github.com/mycila/license-maven-plugin/pull/172) but discussion on > the PR we wonder if it is something to consider in maven shared utils. > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> -- Elliotte Rusty Harold [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
