The maven command runs successfully, I see the logs stating that its pointing to my proxy repo.
However when I go to the repo manager and check the proxy repo its still empty.
My thought would be once I run the above mvn command the junit contents would be available in the proxy repo, then I would remove internet access to the nexus server and try to re-run the mvn command and see the effects and make note. My company is moving to a secured network where we wont have internet access and I was tasked to see how that would affect nexus.
But I’m new to nexus overall, so I feel like im missing something.
Its generally recommended to modify the settings.xml - Maven Repositories
Aside from reminding you that maven has a local cache in ~/.m2/repository I can’t really suggest anything other than verify from the request logs that it spoke to Nexus.
<!-- Another sample, using keys to authenticate.
<server>
<id>siteServer</id>
<privateKey>/path/to/private/key</privateKey>
<passphrase>optional; leave empty if not used.</passphrase>
</server>
-->
<activation>
<jdk>1.4</jdk>
</activation>
<repositories>
<repository>
<id>maven_proxy</id>
<name>maven_proxy</name>
<url>http://:172.X.X.X:8081/repository/maven_proxy/</url>
<layout>default</layout>
<snapshotPolicy>always</snapshotPolicy>
</repository>
</repositories>
</profile>
<!--
| Here is another profile, activated by the system property 'target-env' with a value of 'dev',
| which provides a specific path to the Tomcat instance. To use this, your plugin configuration
| might hypothetically look like:
|
| ...
| <plugin>
| <groupId>org.myco.myplugins</groupId>
| <artifactId>myplugin</artifactId>
|
| <configuration>
| <tomcatLocation>${tomcatPath}</tomcatLocation>
| </configuration>
| </plugin>
| ...
|
| NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
| anything, you could just leave off the <value/> inside the activation-property.
|
<profile>
<id>env-dev</id>
<activation>
<property>
<name>target-env</name>
<value>dev</value>
</property>
</activation>
<properties>
<tomcatPath>/path/to/tomcat/instance</tomcatPath>
</properties>
</profile>
-->