Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Invalid value for finalName in Maven plugin parameter  RSS feed

 
Peter Johnson
author
Bartender
Posts: 5856
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have developed a Maven plugin. One of my mojos has this as a parameter:



The pom.xml that includes the plugin in the <build> section has a <finalName> entry, but the plugin reports that inputDirectory was set to "${project.build.directory}/{project.artifactId}" instead. However, if I do this:



Then inputDirectory is set to "${project.build.directory}/${project.build.finalName}" as expected.

In addition, within the plugin I looked at the value of project.getBuild().getFinalName(), and even that returned artifactId, and not finalName.

So how come finalName == finalName when evaluated within the pom.xml, but finalName != finalName when evaluated within the plugin? Googling didn't yield much help (I came across several defect reports that were variations of this, all claimed to be closed and fixed).

I'm using Maven 3.0.3, and in most cases I am specifying the latest versions of various plugins.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!