coderplus/copy-rename-maven-plugin

m2e compatible maven plugin for renaming/copying

copy-rename-maven-plugin

The copy-rename-maven-plugin helps in copying files or renaming files or directories during the Maven build lifecycle.

How do I use it?

Head over to the Project Website for usage instructions

How can I help the project?

Thanks for asking...

• If you use this plugin
  • Test this out. File an issue if it doesn't work for you. File an issue if you think it should do something more, or something different.
• If you would like to contribute
  • Do let me know and you can always fork the project.

copy-rename-maven-plugin's Issues

Ignores maven variables

The plugin ignores maven variables such as ${parent.basedir}. If that is placed at the beginning of sourcePath it will assume the current directory and will place the path to the current directory in front of ${parent.basedir}. With the following configuration

${parent.basedir}/base-share-amp/src/main/resources/META-INF/share-config-custom.xml

the final sourceFile path ends up

/Users/cwhite/GitWorkingCopies/alfresco/share/brand-share/angularui-share-amp/${parent.basedir}/base-share-amp/src/main/resources/META-INF/share-config-custom.xml

and the file is not found. It should respect all maven variables.

Add configuration to the "rename" goal so build does not fail if source file doesn't exist

This plugin (version 1.0.1) currently fails the build when the "rename" goal is used to rename a file but the source file doesn't exist. It would be nice to have a way to control this behavior with configuration, e.g. setting strict to false to make it ignore nonexistent source files.

Plugin fails for folders, if at destination a folder with same exists.

If at destination the folder with same name is present, Plugin is not able to overWrite folders or merge it.
It is set true, then it is expected that qat least contents should get merged.

Recursively copy a directory without specifying every file in it

Right now, rename supports directories, but copy for some reason doesn't. This means, the only way to copy a directory is by listing every file inside individually in the POM, which is prone to breakage when new files are added.

@kohlschuetter may be interested as well, but https://github.com/kohlschutter/copy-rename-maven-plugin doesn't have issues enabled.

Add support for wildcards

Would be an incredible feature to support something like this:

<configuration>
    <sourceFile>${project.build.outputDirectory}/*_abc.properties</sourceFile>
    <destinationFile>${project.build.outputDirectory}/*_xyz.properties</destinationFile>
</configuration>

This is especially helpful when you integrate dependencies and need to rename files from them because your file name pattern differs.

The feature could be restricted, e.g. to only support a single asterisk for starters. But that should help in most cases already.

Version 1.0.1 seems to be broken somehow

Version 1.0.1 seems to be broken somehow.
Not sure what the code for it is but the release exist
https://mvnrepository.com/artifact/com.coderplus.maven.plugins/copy-rename-maven-plugin/1.0.1
but there is no corresponding tag/branch here.
The plugin itself seems to produce filenames where the plugin name is included by accident.

Add support for skipping execution (parent POM)

I would like to use this plug-in in a parent POM. I have several plug-ins configured in the build-section and all are "disabled" when mvn installing the parent POM itself. All plug-ins support something like:

....
${disable_parent_functionality}
....
</configuration

Please add support for skipping execution.

Is this project abandoned? (new fork available)

There hasn't been an update in a while, and the coderplus.com domain appears to be abandoned.
Can I assume this project is abandoned as well?

If so, I'd encourage everyone to move over to my fork at https://github.com/kohlschutter/copy-rename-maven-plugin

Copy-rename is performing a move

I am trying out the plugin but the plugin is actually moving my file instead of copying it. I assumed it would leave my file and copy and rename it.

Add support for <fileMode>

add support to set the file mode, for example 0755, in the same manner that the assembly plugin.

Build fails when overwrite is false and file already exists

Please provide an option to not fail the build if the target file already exists and is set to false.

Does it work in package phase?

Need to rename the tar file from Maven Assembly to a proprietary naming convention (incl. extension).
Thanks!

support for resource filtering

Add support for resource filtering while copying or renaming files

rename fails for directory with content

I tried to use the plugin to rename a directory that contains some other directories and files, but get the error

[ERROR] Failed to execute goal com.coderplus.maven.plugins:copy-rename-maven-plugin:1.0:rename (normalize-hyperv-structure) on project infra: could not rename D:\Stuff\git-ws\st33.net\target\output-le vel4 to D:\Stuff\git-ws\st33.net\target\hyper-v -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.coderplus.maven.plugins:copy-rename-maven-plugin:1.0:rename (normalize-hyperv-structure) on project infra: could not rename D:\Stuff\git-ws\st33.net\target\output-level4 to D:\Stuff\git-ws\st33.net\target\hyper-v at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) .....

If I empty the directory the rename succeeds.

Would it be possible to implement support for moving of directories with content?

(As of now I must fall back to the Antrun plugin, but I would rather use this plugin as it is more "Mavenish")

Allow to delete the original file

Hello,

It would be nice if the plugin delete the old file when it has been renamed.
I have a lot of modules of maven generating a file with same name (legacy code...) and before the pack of jar i use the plugin to rename the file according to the module, but it keeps the old file. It could be nice if the pluging has an option to delete the old file.

Add suport for <overWriteIfNewer>

User Story:
As a plugin user I want to be able to configure a file copy to only happen when the source file is newer than the destination file in order to avoid undesired side effects.

In some cases, overwriting a file can generate undesired side effects, like restarting Tomcat or taking too much time due to file size and/or network speed.

I propose to use to maintain compatibility with maven-dependency-plugin.

License confusion

Hey!
On your webpage, and on maven central there is stated that license is MIT, while in repository there is commited Eclipse license, and in pom there is MIT licence.

Could you please clarify the confusion?

http://coderplus.github.io/copy-rename-maven-plugin/license.html
https://mvnrepository.com/artifact/com.coderplus.maven.plugins/copy-rename-maven-plugin/1.0