Dennis Reedy wrote:
Should the Rio classdepandjar mojo be used to build the artifacts? In this way we can produce the service, dl and api artifacts right out of the gate.
Does Rio's classdepandjar alter classdep in any way?
Past versions of ClassDep depended on Sun's jdk tools non public api and doesn't capture annotation or generic dependencies, but we recently refactored it to do so using ASM, it no longer depends on any Sun non public api.
What can we do to merge functionality?
