New maven dependency version pulling pom, not jar into private nexus repo?
<p>I'm upgrading some dependency versions I have in a java/maven/spring application, which is using our nexus repo as the central repository mirroring maven central.</p>

<p>I tried upgrading <em>hibernate</em> to it's newest version of 3.5.4-Final as listed:</p>

<p><a href="http://mvnrepository.com/artifact/org.hibernate/hibernate/3.5.4-Final" rel="nofollow">Hibernate newest release stable version</a></p>

<p>And when I run maven install, I see in my nexus server that there is now 3.5.4-Final listed, but inside its directory there is only a pom.xml file for the project and none of it's associated JAR's.</p>

<p>When I inspect the POM, I can see it's packaging is listed as POM and not JAR.</p>

<p>Why is this, and how can I make maven take the jar packaged version of the library rather than just the POM?</p>

<p>EDIT - mvn install error message posted:</p>

<pre><code>[ERROR] Failed to execute goal on project app: Could not resolve dependencies for project com.app:app:war:16.2.1-SNAPSHOT: Failure to find org.hibernate:hibernate:jar:3.5.4-Final in http://ssp-nexus1.mynexus-server.com:8081/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of company.nexus.mirror has elapsed or updates are forced -&gt; [Help 1]
</code></pre>