[MNG-885] no project definition leads to NPE in plugin parameter expression evaluator

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0-beta-3
• Component/s: Plugins and Lifecycle
• Assignee: John Dennis Casey
• Reporter: Brett Porter
• Created: 14/Sep/05 01:20
• Updated: 01/Feb/06 14:41
• Resolved: 26/Sep/05 15:57

Description

there are two places this can occur:
1) calculation of ${basedir} ro a path derived from it
2) missing values that go to check project properties

Should project be null, or should it be a skeleton instance? Either the expression evaluator needs to be fixed (set basedir to user.dir, don't look for properties), or the project needs to be populated.

I encountered this attempting to use scm:checkout.

Issue Links

• is duplicated by: MNG-893 NPE in PluginParameterExpressionEvaluator when a mojo need the basedir and pom.xml doesn't exist
• is duplicated by: MNG-906 Running an M2 goal in a directory not containing a POM generates confusing messages.