I don't think org.apache.maven.toolchain.java should ever have been in maven-toolchain, it should have lived in its own artifact.
maven-toolchain was tied to core, and AFAIK the core classloader will always win in such cases, so the net result is it is not possible to add the extra methods that were planned for JavaToolChain, e.g. getBootstrapLibraries(), etc [not that those methods are necessarily the ones we'd want] Still, we have org.apache.maven.toolchain.java in core and in maven-toolchain, but I would like to extend it... except that it basically forces a new version of maven to be able to do that, or else we have a new set of classes, e.g. org.apache.maven.toolchain.jdk which duplicate what is in core but add the extras and mark the stuff in org.apache.maven.toolchain.java as deprecated -Stephen On 5 August 2010 15:37, Benjamin Bentmann <[email protected]> wrote: > Stephen Connolly wrote: > > So if I want to add more core toolchains I now have to push the changes to >> core, or will the classloader always take from core and not from a newer >> maven-toolchains dep of a plugin? >> > > Not sure what you mean with "core toolchain" here, at least in M3 you > should be free to add new toolchains as plugin dependencies or build > extensions dependending on the scope of use. > > > > Benjamin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
