[
https://issues.apache.org/jira/browse/MCLEAN-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961032#comment-14961032
]
Brian Bohl commented on MCLEAN-70:
----------------------------------
I should have started with the mailing list, as obviously my knowledge of how
Maven works is/was lacking. And I made a stupid mistake. The problem appears
to be with the default lifecyle, not clean. I could have sworn I ran just "mvn
clean", but I must have been running with verify. In reality I wanted to do
this in the validate phase.
What's happening is described nicely in the [this mailing list
discussion|http://maven.40175.n5.nabble.com/Why-is-quot-mvn-validate-compile-quot-different-from-quot-mvn-validate-mvn-compile-quot-td5774550.html].
Frankly after reading that, along with your comment, I am having a hard time
seeing the usefulness of the maven-install plugin. Closing the issue.
> conflict with maven-install-file plugin
> ---------------------------------------
>
> Key: MCLEAN-70
> URL: https://issues.apache.org/jira/browse/MCLEAN-70
> Project: Maven Clean Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Brian Bohl
> Priority: Minor
>
> Clean resolves dependencies before executing any lifecycle phase. This
> conflicts with the maven-install-file plugin, as usually this plugin is used
> to install a dependency.
> I am not sure why it needs to download dependencies (I realize it needs to
> resolve plugins), but at the very least it would be nice to delay dependency
> resolution until the clean phase, allowing me to configure the
> maven-install-file plug to execute in the pre-clean phase.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
