Proper configuration of the Maven phases

Description

On install create all artifacts (javadoc, site, tests, ...) and install locally.
On deploy, deploy all these artifacts to the maven repository.

Environment

None

Activity

Show:
Florian Huonder
October 4, 2010, 12:35 PM

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)

Florian Huonder
July 2, 2011, 7:15 PM

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.

Discussion needed.

Colm O hEigeartaigh
November 20, 2012, 10:13 AM

> 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.

Colm.

Florian Huonder
January 2, 2013, 9:46 AM

The behavior is already so that install only creates the artifact.
For further stuff as javadoc.jar etc. it is autmatically generated while deployment.

Assignee

RenéR

Reporter

Florian Huonder

Labels

None

Time tracking

0m

Time remaining

1h 30m

Fix versions

Priority

Major
Configure