[MNG-5158] Make loading of extensions from lib/ext more robust with regard to existence of ext directory

• Type: Improvement
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 3.0.3
• Fix Version/s: 3.0.4
• Component/s: Command Line
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 19/Aug/11 02:25
• Updated: 19/Aug/11 02:28
• Resolved: 19/Aug/11 02:27

Description

Someone who tries to delete or temporarily rename lib/ext will get rewarded with an error:

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)

Classworlds provides a means to handle a missing dir more gracefully which fits the idea of optional extensions better.

Issue Links

• is related to: MNG-4984 Simplify drop in of 3rd party extensions for Maven core