Make loading of extensions from lib/ext more robust with regard to existence of
ext directory
---------------------------------------------------------------------------------------------
Key: MNG-5158
URL: https://jira.codehaus.org/browse/MNG-5158
Project: Maven 2 & 3
Issue Type: Improvement
Components: Command Line
Affects Versions: 3.0.3
Reporter: Benjamin Bentmann
Priority: Trivial
Someone who tries to delete or temporarily rename {{lib/ext}} will get rewarded
with an error:
{noformat}
java.io.FileNotFoundException: D:\apache-maven-3.0.3\bin\..\lib\ext
at
org.codehaus.plexus.classworlds.launcher.ConfigurationParser.loadGlob(ConfigurationParser.java:336)
at
org.codehaus.plexus.classworlds.launcher.ConfigurationParser.parse(ConfigurationParser.java:247)
at
org.codehaus.plexus.classworlds.launcher.Configurator.configure(Configurator.java:135)
at
org.codehaus.plexus.classworlds.launcher.Launcher.configure(Launcher.java:132)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:405)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
{noformat}
Classworlds provides a means to handle a missing dir more gracefully which fits
the idea of optional extensions better.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira