You are viewing a plain text version of this content. The canonical link for it is here.

Posted to npanday-commits@incubator.apache.org by "Lars Corneliussen (JIRA)" <ji...@apache.org> on 2011/03/01 16:10:37 UTC

[jira] Created: (NPANDAY-374) Respect 'build.finalName' when compiling using the maven-compile-plugin

Respect 'build.finalName' when compiling using the maven-compile-plugin
-----------------------------------------------------------------------

                 Key: NPANDAY-374
                 URL: https://issues.apache.org/jira/browse/NPANDAY-374
             Project: NPanday
          Issue Type: Improvement
          Components: Maven Plugins
    Affects Versions: 1.3-incubating
            Reporter: Lars Corneliussen
             Fix For: 2.0


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.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira