On 12-02-09 12:09 PM, [email protected] wrote:
I'm trying to figure out how to best handle a .run binary as a maven artifact. My build produces a
single binary executable, a ".run" file. Currently this is done with a maven exec plugin
firing off an script, all tied to the install phase. The package type of the pom is
"pom". So, this, to my mind, isn't really doing it the maven way. Moreover, I'd like to
make that .run binary a maven artifact in my nexus repository so it can be accessed by other
projects which need it in their builds.
1) Is it wrong to handle a binary such as this via maven/nexus?
No.
2) How do I go about getting my .run binary installed into nexus by
maven, i.e. by the deploy phase? Note, I've already figured out how to
get my build to put the .run file into the target directory, so I really
just need to figure out how to get maven to deploy it, right? Thanks!
Use the build helper plugin with the attach-artifact goal and bind it to
the appropriate life cycle phase after it is generated .. then mvn
deploy will push it to your repo.
http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html
Manfred
http://simpligility.com
