On install create all artifacts (javadoc, site, tests, ...) and install locally.
On deploy, deploy all these artifacts to the maven repository.
Maybe we could think of simplifying the maven stuff with removing all the release-stuff.
Alternatively we could use th Bamboo Artifactory Plugin (http://wiki.jfrog.org/confluence/display/RTF/Bamboo+Artifactory+Plug-in)
I think this is not correct (now).
install is for installing this artifact. And this is only the core jar.
All the related stuff such as javadoc, tests etc. are part of the deployment and shall only be created in this case.
But what is the correct phase?
Maven has only ..., install, deploy.
There is no pre-deploy or something.
> install is for installing this artifact. And this is only the core jar.
> All the related stuff such as javadoc, tests etc. are part of the deployment and shall only be created in
> this case.
+1. I don't really see the problem here - javadoc etc. are run as part of the "-Pdeploy" profile, and so "mvn -Pdeploy deploy" will deploy all of the generated jars.
The behavior is already so that install only creates the artifact.
For further stuff as javadoc.jar etc. it is autmatically generated while deployment.