I am using Drools 6.0.1 and making use of the new Maven-based architecture to deploy my rules.
The POM of the project looks like shown at the end of this post.
I
I found the underlying problem: Bug No. 1065984 in RedHat's Bugzilla. It is about the embedded maven not respecting the settings configured in that explicit settings.xml
. The bugfix was released in Drools 6.1.0.Beta1 which got published in the Maven repositories on friday - that is why I didn't find it until shortly.
With the new version, the offline aspect is working much better, at least it won't connect to a remote server just like this.
Still, there is the problem, that the effective Maven configuration/pom does take into account the POM which is used for the project Drools is running inside. That is bad, because I don't want to put all those dependencies into the Drools-Maven-Repository. But that is for another question.
It is normal for Nexus to contain release artifacts, not just dependencies which you use during builds. However, it is possible to block its use. Presumably your ~/.m2/.settings.xml has been configured to go to your Nexus repository instead of central, when looking for artifacts. Similar to the way you might configure Maven to go to the Nexus proxy instead of central, you just change ~/.m2/.settings to disable downloads of release and snapshot artifacts from central.
<repositories>
<repository>
<id>central</id>
<url>http://repo1.maven.org/maven2</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
</repositories>