FWIW...
I have faced this and variety of other issues with mvn -U install
I never get a working build with a freshly checked out workspace, cd v3,
and mvn -U install (including a mvn -U install in javaee-api)
What seems to work consistently though is mvn -U install in individual
subdirectories (yes, repeated attempts are required for dependencies)
And then a mvn install (forget the -U) in the root /v3 dir. The flag -U
in v3 dir always ends with one or the other issue either
dowloading/releading jars
and it fails at random places.
Kin-man Chung wrote:
> When I did a "mvn -U install" I seemed to get into an infinite loop:
>
> INFO] Reloading plugin container for:
> com.sun.enterprise:hk2-maven-plugin. The plugin artifact has changed.
> [INFO] Reloading plugin container for:
> com.sun.enterprise:hk2-maven-plugin. The plugin artifact has changed.
> [INFO] Reloading plugin container for:
> com.sun.enterprise:hk2-maven-plugin. The plugin artifact has changed.
> [INFO] Reloading plugin container for:
> com.sun.enterprise:hk2-maven-plugin. The plugin artifact has changed.
> [INFO] Reloading plugin container for:
> com.sun.enterprise:hk2-maven-plugin. The plugin artifact has changed.
> [INFO] Reloading plugin container for:
> com.sun.enterprise:hk2-maven-plugin. The plugin artifact has changed.
> [INFO] Reloading plugin container for:
> com.sun.enterprise:hk2-maven-plugin. The plugin artifact has changed.
> [INFO] Reloading plugin container for:
> com.sun.enterprise:hk2-maven-plugin. The plugin artifact has changed.
> ...
>
> Anyone else ran into the same problem?
>
> -Kin-man
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>