Firstly, I hope you're not ever running "mvn clean install deploy" since
"mvn clean deploy" is sufficient the first one runs the entire install
cycle twice.
Second, according to the Clover Plugin doc (
http://maven.apache.org/plugins/maven-clover-plugin/), one of its stated
features is "Generation of Clovered artifacts into your local repository".
It looks like you have to "instrument" the project first... so, perhaps you
do not have the "clover:instrament" goal execution in the pom?
http://maven.apache.org/plugins/maven-clover-plugin/usage.html
Just a guess... I don't use clover.
Eric
On 1/30/07, jp4 <[EMAIL PROTECTED]> wrote:
The first question I have is whether or not clovered artifacts are
supposed
to be deployed to the remote repo when running mvn clean install
deploy? I
do not see these clovered artifacts being deployed and wonder if they
should
be.
The reason I ask this is because I am running into a anomoly with my
build.
I run my build locally and it pulls clovered dependencies from the local
repo. When I run it on our build server with the same exact
configuration,
it attempts to find the clovered artifacts from our development repository
instead of the local repo? As a result, the build fails since clovered
files are not deployed to the development repo.
Any insight would be greatly appreciated.
Thanks,
jp4
--
View this message in context:
http://www.nabble.com/Are-clovered-files-supposed-to-be-deployed-to-the-remote-repo--tf3143783s177.html#a8714082
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Eric Redmond
http://codehaus.org/~eredmond
