maven-file-management seems much more broadly used. I'm not sure we can get rid of it. I tried pulling it out of maven-jar-plugin but it seems more critical there, unless there's some other way to manage filesets and patterns I don't know about.
INFO] +- org.apache.maven.shared:file-management:jar:3.0.0:compile [INFO] | \- org.apache.maven.shared:maven-shared-io:jar:3.0.0:compile [INFO] | +- org.apache.maven:maven-compat:jar:3.0:compile [INFO] | \- org.apache.maven.wagon:wagon-provider-api:jar:2.10:compile [INFO] +- org.apache.maven:maven-archiver:jar:3.5.0:compile Possibly we can remove its dependency on shared-io. On Fri, Jul 3, 2020 at 5:13 PM Robert Scholte <[email protected]> wrote: > > That good news. Call me Dr Deprecator of Maven Git Repos, I can call a vote > soon. > > Robert > On 3-7-2020 21:56:40, Elliotte Rusty Harold <[email protected]> wrote: > Indeed it does seem possible to remove maven-assembly-plugin's > dependency on maven-shared-io by copying a few classes from one into > the other and making them non-public. > > Removing file-management from the maven-dependency-plugin was even easier. > > We should probably formally deprecate maven-shared-io so it doesn't > accidentally propagate into any other projects. > > > -- > Elliotte Rusty Harold > [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Elliotte Rusty Harold [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
