> Apart from upgrading all our dependencies to something that doesn't
> have the OpenSymphony repository in its pom (which we're currently
> doing) is there anything else we can do in the meantime to block this
> repository? We're working on Open Source projects so solutions that
> work only in our Network or with our own Nexus server won't work.
The repo is declared as follows in the pom:
<repository>
<id>opensymphony</id>
<name>opensymphony</name>
..........
</repository>
You can use this information to hide the repo via settings.xml:
<settings>
...
<mirrors>
<mirror>
<id>opensymphony-killer</id>
<name>opensymphony-killer</name>
<url>http://repo1.maven.org/maven2</url>
<mirrorOf>opensymphony</mirrorOf>
</mirror>
</mirrors>
...
</settings>
This will basically tell Maven to use Central as an override for the
OpenSymphony repo. This does assume that Central has the artifacts you
were previously accessing via OpenSymphony, of course -- if not, you
will need to substitute another repo for Central. You can apply this
same technique (using the repo id in the mirrorOf value) to block
other sites just as easily.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
