I'm about to start releasing plugins and libraries, and I have come to realize I'm a terrible neat-nick ;)
I look at the dependencies on maven-archiver and I see that several of them appear unused, and some can be trimmed down to less invasive scopes, such as provided. Is there any reason why: A) org.apache.maven:maven-project and it's likes cannot have scope "provided" in a plugin/library ? B) org.codehaus.plexus:plexus-container-default (picked up transitively from numerous sources or included directly in some poms) cannot have scope provided ? (Or excluded when not actually used...) C) An artifact should be included when it seems unused ? (We chatted about plexus-utils on #maven-dev yesterday and there might be something there) I have this terrible hang-up with minimizing dependency profiles. ( I promise it's *not* because there's a lot of thread contention going on in DefaultMavenPluginManager - I will fix the real cause of that ;) Will I be "acting responsibly" if I clean up dependencies and test with 2.0.11, 2.2.1 and 3.0-beta and then go for release ? Kristian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
