Debug Info

Some EE jars such as zkmax contains a repository entry in their pom targeting ZK CE.
This may cause maven to search for dependencies in ZK CE repositories regardless of their availability in EE repository or local repository.
This also add the CE repository as a repository to be resolved during build, even if the user defined pom.xml file only use a local repository to manage their dependencies (such as nexus, archiva, artifactory).

Root Cause

https://maven.zkoss.org/repo/zk/ee/org/zkoss/zk/zkmax/8.0.4.2/zkmax-8.0.4.2.pom

ZK EE jars contain entries such as
	<repositories>
		<repository>
			<id>zk repository</id>
			<url>http://mavensync.zkoss.org/maven2</url>
		</repository>

EE jars contain references to

Maven configuration and Workaround

Configuring maven to work with a single repository (recommended by maven when working with a local repository)
http://maven.apache.org/guides/mini/guide-mirror-settings.html

Workaround blacklisting the ZK CE repository:

    <repository>
        <id>ZK CE</id>
        <name>ZK CE Repository</name>
        <url>http://mavensync.zkoss.org/maven2</url>
        <releases>
            <enabled>false</enabled>
        </releases>
        <snapshots>
            <enabled>false</enabled>
        </snapshots>
    </repository>