[NPANDAY-374] Respect 'build.finalName' when compiling using the maven-compile-plugin

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.4-incubating
• Fix Version/s: Backlog
• Component/s: Maven Plugins
• Assignee: Unassigned
• Reporter: Lars Corneliussen
• Created: 01/Mar/11 16:09
• Updated: 27/Jun/14 07:12

Description

Usually a compiler uses

{finalName}

.

{packaging-extension}

for the artifact to be produced into target-directory.

NPanday should rather override the finalName (configurable) using project.getBuild().setFinalName() as long as it has not been set to anything else but the default.
If a user chooses the name himself, NPanday should respect that wish.

Example: I'm creating a Console-App with a nice ArtifactId (HelloNPanday.Console), but I want it to be named 'hello-npanday.exe' in my target folder.

Of course, when deployed, the default Name will be applied.