What is your use case?
These two plugins have different target.

I'm having the same issue. I need to save the artifacts on either the slave that ran the build job or at least a machine on the local network and not across a WAN which adds a lot of time to build job. I've tried using the ArtifactDeployer plugin, which works great, but downstream jobs using the CopyArtifact plugin are still looking to the Jenkins server for the artifacts, which is located in a different country.

I would very much like this same functionality. I'm looking at using ArtifactDeployer instead of the internal code - to allow easily archiving artifacts to a separate file server not part of the jenkins build agent host - but would hate to lose the functionality of being able to refer/copy those artifacts in other builds.

I realize I could copy explicit file paths, or I could rig up something like an extra publish action - to publish to both a "by build number" as well as "last successful" directory, but that seems a bit hackish.

Suggestions?

We need to extend ArtifactDeployer or develop an other plugin with copy artefact plugin features but with remote artifacts location storage.

You should use ArtifactManager which is designed for this purpose.