How does Maven depend on Plexus components?
plexus consists of a myriad of components
extensively used in core, every plugin, Modello and generated code, ...
Final Proposal : maven-shared-util
used in Maven core.
replaced in Maven 3 by guice + sisu + sisu-inject-plexus
plugin used in Maven 3 and every Plexus component like maven-shared: any replacement from sisu available? any migration to do?
dependency used in Maven 3 and every Plexus component like maven-shared: any replacement from sisu available? any migration to do?
used in maven-parent pom for reference, but since components migrate from Plexus javadoc tags to plexus-component-annotations, we should probably not really need this javadoc doclet any more
used in a lot of core plugins (assembly, dependency, ear, jar, javadoc, site, war, ...)
used in maven-indexer
used in maven-compiler-plugin
used in doxia-site-renderer and some plugins: changes, doap, invoker, linkcheck, pdf, project-info-reports, site
used in wagon-ssh (then Maven core), and in plugins: archetype, release, compiler, eclipse, help, repository
used in Maven core (model and settings builders) and many plugins: assembly, change, checkstyle, dependency, invoker, resources, war...
used in plugins: assembly, dependency, war
used in plugins: checkstyle, eclipse, pmd, remote-resources
used in doxia-site-renderer, and plugins: changes, checkstyle, site
(*) contributors are counted by gitstats: some contributors are counted twice since they have different ids
Other external Codehaus dependencies
- Modello: site, github, 35 contributors