These two dependencies are not resolvable. Makes it hard to build externally, which makes it harder to submit patches or to compile code that depends on webserviceshell.
<dependency>
<groupId>edu.iris.dmc</groupId>
<artifactId>dmc-usage-log</artifactId>
<version>${dmc.usage.log.version}</version>
</dependency>
<dependency>
<groupId>edu.iris</groupId>
<artifactId>dmc_logging</artifactId>
<version>${dmc_logging.version}</version>
</dependency>
Per Rob Casey:
Hi Philip-
I've never attempted to build this one myself, but for our internal code, we have an IRIS (Sonatype) >Nexus server that may be picking up on those dependencies you are running into. It wasn't meant to be >built outside of the DMC.
dmc-usage-log and dmc_logging are internal dependencies. I am not sure why they are listed in the >POM, but since this code is distributed for external builds, are they simply ignored unless called for by the >application?
If you can find a way to strip out those dependencies from the code I shared with you, it should be fine.
There are some things that we specifically will not share with the public. The WSS is meant for public use,
though, so I find it interesting that you are running into this problem.
-Rob
These two dependencies are not resolvable. Makes it hard to build externally, which makes it harder to submit patches or to compile code that depends on webserviceshell.
Per Rob Casey: