Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat tools can I use to find out why maven3 searches for really old internal SNAPSHOTs?
    primarykey
    data
    text
    <p>I'm trying to upgrade my company from maven2 to maven3 and one blocker is a weird phenomenon whereby when I activate a certain profile the maven reactor starts searching for tons of old dependency information (for 10+ minutes until it runs out of memory).</p> <p>I've seen that kind of behavior if there's a dependency that has a range (e.g. "[3.0,)") but I'm pretty sure I've wiped all those out.</p> <p>Using mvn dependency:tree and mvn help:effective-pom won't show me if there are any range dependencies and grepping for <em>[, ], (</em> or <em>)</em> in pom.xml files turns up nothing, so I'm a little stumped at the moment about where to poke next.</p> <p>For an example of what I'm talking about, in my pom I've got this profile activation section:</p> <pre><code> &lt;profile&gt; &lt;id&gt;demo&lt;/id&gt; &lt;activation&gt; &lt;property&gt; &lt;name&gt;client&lt;/name&gt; &lt;value&gt;demo&lt;/value&gt; &lt;/property&gt; &lt;/activation&gt; &lt;dependencies&gt; &lt;dependency&gt; &lt;groupId&gt;com.mycompany&lt;/groupId&gt; &lt;artifactId&gt;client-demo&lt;/artifactId&gt; &lt;version&gt;3.32.0-SNAPSHOT&lt;/version&gt; &lt;/dependency&gt; &lt;/dependencies&gt; &lt;/profile&gt; </code></pre> <p>Then when I run this on the command line:</p> <blockquote> <p>mvn -Dclient=demo jetty:run</p> </blockquote> <p>The output is thousands and thousands of searches for pom data for every historical SNAPSHOT that's ever existed of my client-demo artifact:</p> <pre><code> ....snip..... Downloading:https://nexus.mycompany.com/nexus/content/groups/public/com/mycompany/client-demo/2.16.7-SNAPSHOT/client-demo-2.16.7-SNAPSHOT.pom [WARNING] The POM for com.mycompany:client-demo:jar:2.16.7-SNAPSHOT is missing, no dependency information available Downloading: https://nexus.mycompany.com/nexus/content/groups/public/com/mycompany/client-demo/2.16.8-SNAPSHOT/maven-metadata.xml Downloading: https://nexus.mycompany.com/nexus/content/groups/public/com/mycompany/client-demo/2.16.8-SNAPSHOT/client-demo-2.16.8-SNAPSHOT.pom [WARNING] The POM for com.mycompany:client-demo:jar:2.16.8-SNAPSHOT is missing, no dependency information available Downloading: https://nexus.mycompany.com/nexus/content/groups/public/com/mycompany/client-demo/2.16.9-SNAPSHOT/maven-metadata.xml Downloading: https://nexus.mycompany.com/nexus/content/groups/public/com/mycompany/client-demo/2.16.9-SNAPSHOT/client-demo-2.16.9-SNAPSHOT.pom [WARNING] The POM for com.mycompany:client-demo:jar:2.16.9-SNAPSHOT is missing, no dependency information available Downloading: https://nexus.mycompany.com/nexus/content/groups/public/com/mycompany/client-demo/2.16.10-SNAPSHOT/maven-metadata.xml Downloading: https://nexus.mycompany.com/nexus/content/groups/public/com/mycompany/client-demo/2.16.10-SNAPSHOT/client-demo-2.16.10-SNAPSHOT.pom ....snip..... </code></pre> <p>EDIT:: Some more info.</p> <p>This problem appears to be related purely to the inclusion of an additional dependency via profile activation, and not with the dependency itself. For example, if I get rid of the profile and directly depend on the com.mycompany.client-demo-3.32.0-SNAPSHOT the bad behavior is not exhibited. So it's something to do with the way the reactor handles profile-activated dependencies...I think</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload