deploy-file incorrectly deploys attached artifacts

When using the deploy-file goal in a Maven pom (not from the command-line), the deploy-file goal will attempt to additionally deploy all attached artifacts, instead of the individually specified file.

The point of the deploy-file goal is to deploy the specified artifact and optionally the specified source, javadoc and other classified files.

Due to this issue it will unfortunately attempt to deploy other artifacts, like -test.jars that may have been generated.

The following lines in DeployFileMojo should be conditional, perhaps based on a property "includeAttachedArtifacts".

        List<Artifact> attachedArtifacts = project.getAttachedArtifacts();

        for ( Artifact attached : attachedArtifacts )
        {
            deployableArtifacts.add( attached );
        }