Task #3769: Jibx-bind dependencies in d1_common_java are showing up in d1_libclient_java as dependencies - Infrastructure - DataONE Tasks

Task #3769

Story #3770: member nodes want to be able to use libclient without having to rely on maven

Jibx-bind dependencies in d1_common_java are showing up in d1_libclient_java as dependencies

Added by Rob Nahf almost 11 years ago. Updated almost 11 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Rob Nahf

Category:

d1_common_java

Target version:

2013.22-Block.3.3

Start date:

2013-05-17

Due date:

% Done:

100%

Milestone:

None

Product Version:

Story Points:

Sprint:

Description

Certain jibx jars are showing up in the dependency tree of d1_libclient_java, when these are only used by d1_common_java to create the dataone dataTypes from the d1_schemas. This functionality is never called from d1_libclient, so creates false-dependencies.

wrt discussion on packaging libclient_java and it's dependencies as a releases, we want an automatic way to exclude them from the dependency tree, preferably from within d1_common_java itself.

JibX tools and its dependencies on Eclipse plugin arch are not needed for the execution of the jibx generated classes.

Maven seems to have mechanisms for excluding dependencies from the transitive dependencies "graph"
see: http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html

History

#1 Updated by Rob Nahf almost 11 years ago

Parent task set to #3770

#2 Updated by Rob Nahf almost 11 years ago

Status changed from New to In Progress
% Done changed from 0 to 70

setting the scope of the jibx dependencies to 'provided', in both d1_common_java, and d1_jibx_extensions reclassifies most of the unneeded dependencies from libclient's dependency:tree, however, the filter in mvn dependency:tree -Dscope=compile,runtime doesn't work, so they do show in the tree as 'provided' dependencies. Not sure what that does for any other maven plugins that copy them.

Also, the maven-jibx-plugin introduces dependencies on jibx jars, unbelievably...

Will try to filter out these dependencies at the packaging stage.

#3 Updated by Rob Nahf almost 11 years ago

Status changed from In Progress to Testing
% Done changed from 70 to 90

to get rid of the transitive dependencies introduced by maven-jibx-plugin and other plugins added exclusions to the d1_common_java dependency declaration in d1_libclient_java pom.

org.dataone
d1_common_java
${d1_common_java_version}
jar

org.jibx
maven-jibx-plugin

org.apache.maven.plugins
maven-compiler-plugin

This removes most of the unwanted dependencies.
Also added miscellaneous exclusions to the copy-dependencies command:

org.apache.maven,org.codehaus.plexus,classworlds