You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Karl Heinz Marbaise <kh...@gmx.de> on 2020/04/21 17:38:32 UTC
Stumbled upon a strange thing
Hi,
currently I'm working on that project
https://github.com/khmarbaise/maven-it-extension and realized that if I do:
mvn clean
[INFO] Reactor Summary for itf-extension 0.5.0-SNAPSHOT:
[INFO]
[INFO] itf-extension ...................................... SUCCESS [
0.193 s]
[INFO] itf-executor ....................................... SUCCESS [
0.004 s]
[INFO] itf-extension-maven ................................ SUCCESS [
0.008 s]
[INFO] itf-assertj ........................................ SUCCESS [
0.009 s]
[INFO] itf-jupiter-extension .............................. SUCCESS [
0.017 s]
[INFO] itf-maven-plugin ................................... SUCCESS [
0.038 s]
[INFO] itf-examples ....................................... FAILURE [
0.011 s]
[INFO] itf-documentation .................................. SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 0.491 s
[INFO] Finished at: 2020-04-21T19:11:59+02:00
[INFO]
------------------------------------------------------------------------
[ERROR] Plugin
com.soebes.itf.jupiter.extension:itf-maven-plugin:0.5.0-SNAPSHOT or one
of its dependencies could not be resolved: Failure to find
com.soebes.itf.jupiter.extension:itf-maven-plugin:jar:0.5.0-SNAPSHOT in
http://localhost:8081/nexus/content/groups/public was cached in the
local repository, resolution will not be reattempted until the update
interval of nexus has elapsed or updates are forced -> [Help 1]
[ERROR]
If I use "mvn compile" or "mvn clean package" or "mvn verify" also
doing a complete release via release plugins everything is working fine.
The feuture is that the "itf-maven-plugin" is being built in that multi
module build and is being used in "itf-examples"..
As far as I understand the whole thing is that during "clean" cycle it
is tried to resolve the jar which obviously does not exist at this
time...and fails...But I don't understand why it's needed to resolve
the plugin at that time?
The question is:
* Why is there a difference between clean and "compile" etc. cycle?
because at compile there has no jar being built at that time but does
not fail.
* Every lifecycle phase from validate...process-resources is failing
but beginning with "compile" everything works.
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Stumbled upon a strange thing
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
So,
The solution is simple. I have to add the bound life cycle phase in the
module which uses the plugin.
If it's not there Maven needs to figure out the default phase which
means need to lookup for the plugin and that's the cause for the fail
"mvn clean". After adding that. A "mvn clean" works now fine.
Thanks to Robert to enlighten me...
Kind regards
Karl Heinz Marbaise
On 21.04.20 19:38, Karl Heinz Marbaise wrote:
> Hi,
>
> currently I'm working on that project
> https://github.com/khmarbaise/maven-it-extension and realized that if I do:
>
> mvn clean
>
> [INFO] Reactor Summary for itf-extension 0.5.0-SNAPSHOT:
> [INFO]
> [INFO] itf-extension ...................................... SUCCESS [
> 0.193 s]
> [INFO] itf-executor ....................................... SUCCESS [
> 0.004 s]
> [INFO] itf-extension-maven ................................ SUCCESS [
> 0.008 s]
> [INFO] itf-assertj ........................................ SUCCESS [
> 0.009 s]
> [INFO] itf-jupiter-extension .............................. SUCCESS [
> 0.017 s]
> [INFO] itf-maven-plugin ................................... SUCCESS [
> 0.038 s]
> [INFO] itf-examples ....................................... FAILURE [
> 0.011 s]
> [INFO] itf-documentation .................................. SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 0.491 s
> [INFO] Finished at: 2020-04-21T19:11:59+02:00
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Plugin
> com.soebes.itf.jupiter.extension:itf-maven-plugin:0.5.0-SNAPSHOT or one
> of its dependencies could not be resolved: Failure to find
> com.soebes.itf.jupiter.extension:itf-maven-plugin:jar:0.5.0-SNAPSHOT in
> http://localhost:8081/nexus/content/groups/public was cached in the
> local repository, resolution will not be reattempted until the update
> interval of nexus has elapsed or updates are forced -> [Help 1]
> [ERROR]
>
>
> If I use "mvn compile" or "mvn clean package" or "mvn verify" also
> doing a complete release via release plugins everything is working fine.
>
>
> The feuture is that the "itf-maven-plugin" is being built in that multi
> module build and is being used in "itf-examples"..
>
> As far as I understand the whole thing is that during "clean" cycle it
> is tried to resolve the jar which obviously does not exist at this
> time...and fails...But I don't understand why it's needed to resolve
> the plugin at that time?
>
> The question is:
> * Why is there a difference between clean and "compile" etc. cycle?
> because at compile there has no jar being built at that time but does
> not fail.
>
> * Every lifecycle phase from validate...process-resources is failing
> but beginning with "compile" everything works.
>
>
>
> Kind regards
> Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org