Copy jar file maven

If you shared a bit more of your build environment, there might be a better way - there are plugins to provision a number of servers. Could you attach an assembly that is unpacked in the server's root? What server are you using? For a simple copy-tasks I can recommend copy-rename-maven-plugin. It's straight forward and simple to use:.

Furthermore you can specify multiple executions in multiple phases if needed, the second goal is "rename", which simply does what it says while the rest of the configuration stays the same. For more usage examples refer to the Usage-Page. Note : This plugin can only copy files, not directories. Thanks to james. The dependency:copy is documentend, and has more useful goals like unpack. The ant solution above is easiest to configure, but I have had luck using the maven-upload-plugin from Atlassian.

I was unable to find good documentation, here is how I use it:. This solution is not constrained to JBoss, this is just what I named my variables. I have a profile for dev, test, and live. So to upload my ear to a jboss instance in test environment I would execute:. I recommend downloading the sources and looking at the documentation inside to see all the features the plugin provides. Well, maven is not supposed to be good in doing fine granular tasks, it is not a scripting language like bash or ant, it is rather declarative - you say - i need a war, or an ear, and you get it.

However if you need to customize how the war or ear should look like inside, you have a problem. It is just not procedural like ant, but declarative. This have some pros in the beginning, and could have a lot of cons at the end. I guess the initial concept was to have fine plugins, that "just work" but the reality is different if you do non-standard stuff.

If you however put enough effort in your poms and few custom plugins, you'll get a much better build environment as with ant for example depends on you project of course, but it gets more and more true for bigger projects. I've had very good experience with copy-maven-plugin. It has a much more convenient and concise syntax in comparison to maven-resources-plugin.

A generic way to copy arbitrary files is to utilize Maven Wagon transport abstraction. There are a few plugins that provide facilities to copy files through the use of Wagon.

Most notable are:. There is the deploy-file goal. It it quite inflexible but can get the job done:. Significant disadvantage to using Maven Deploy Plugin is that it is designated to work with Maven repositories.

It assumes particular structure and metadata. There is no way around this. Use the upload-single goal :. The use of Wagon Maven Plugin for copying is straightforward and seems to be the most versatile. See the list of existing Wagon Providers. For example. The examples above pass plugin parameters in the command line. Alternatively, plugins can be configured directly in POM. Then the invocation will simply be like mvn deploy:deploy-file configured-execution-id.

Or it can be bound to particular build phase. If the destination you are copying to requires authentication, credentials can be provided via Server settings. Another way is to bundle these things into an artifact using the assembly plugin. Then you can use the dependency plugin to unpack these files where you want. There are also copy goals in the dependency plugin to copy artifacts. If someone wants total control over the path of the source and destination paths, then using maven-antrun-plugin 's copy task is the best option.

This approach will allow you to copy between any paths on the system, irrespective of the concerned paths being within the mvn project or not.

I had a situation where I had to do some unusual stuff like copy generated source files from target directory back to the src directory for further processing. Evaluate Confluence today. Apache Maven. Pages Blog.

Space shortcuts How-to articles. Child pages. New Main Site. Browse pages. A t tachments 0 Page History People who can view. Copy Page Tree. To clean up the downloaded artifacts as part the build, set localRepositoryDirectory 's value to a location in your project's target directory.

Your configuration should look like this:. Copying specific artifacts In copying specific artifacts, you need to bind the dependency:copy mojo to a lifecycle, configure the plugin and specify the artifacts you want to copy. Using an alternate local repository dependency:copy always downloads artifacts to default local repository first, and then copy the artifacts to the desired locations.