In a JAR project, when declaring a dependency with type "zip," the generated manifest class-path excludes the zip dependency. Further, when generating the eclipse artifacts, the .classpath also excludes the zip dependency.
This seems to occur because the ArtifactHandler isAddedToClasspath is false (by default, the "zip" artifact creates a new DefaultArtifactHandler). The ZIP is not a custom artifact type, but rather is created using the assembly plugin, so it is not desirable to create a custom ZIP ArtifactHandler. How can this ZIP dependency be included in a JAR's generated manifest class-path and the generated Eclipse .classpath?
