Il 03/04/2014 10:19, Klevenz, Stephan ha scritto:
Hi,
I am having issues in setting up my OData 4 project using eclipse maven plugin
(mvn eclipse:eclipse). Actually the module fit and client core do show errors.
I have analyzed two reasons for that:
a) cyclic dependencies
Fit depends on client core and vice versa. Q: Can we avoid this e.g. by moving
all testing stuff from client core to the fit module? Later, I think we do the
same with server based integration tests.
Hi Stephan, fit module doesn't depend on client. See dependency tree above.
[INFO] org.apache.olingo:olingo-fit:war:0.1.0-SNAPSHOT
[INFO] +- stax:stax-api:jar:1.0.1:compile
[INFO] +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.7.10:compile
[INFO] | +- org.apache.cxf:cxf-api:jar:2.7.10:compile
[INFO] | | +- org.codehaus.woodstox:woodstox-core-asl:jar:4.2.0:compile
[INFO] | | | \- org.codehaus.woodstox:stax2-api:jar:3.1.1:compile
[INFO] | | +- org.apache.ws.xmlschema:xmlschema-core:jar:2.1.0:compile
[INFO] | | +-
org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.7.1:compile
[INFO] | | \- wsdl4j:wsdl4j:jar:1.6.3:compile
[INFO] | +- org.apache.cxf:cxf-rt-core:jar:2.7.10:compile
[INFO] | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.6:compile
[INFO] | +- javax.ws.rs:javax.ws.rs-api:jar:2.0-m10:compile
[INFO] | +- org.apache.cxf:cxf-rt-bindings-xml:jar:2.7.10:compile
[INFO] | \- org.apache.cxf:cxf-rt-transports-http:jar:2.7.10:compile
[INFO] +- com.fasterxml.jackson.core:jackson-databind:jar:2.3.2:compile
[INFO] | +-
com.fasterxml.jackson.core:jackson-annotations:jar:2.3.2:compile
(version managed from 2.3.0)
[INFO] | \- com.fasterxml.jackson.core:jackson-core:jar:2.3.2:compile
[INFO] +-
com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider:jar:2.3.2:compile
[INFO] | +-
com.fasterxml.jackson.jaxrs:jackson-jaxrs-base:jar:2.3.2:compile
[INFO] | \-
com.fasterxml.jackson.module:jackson-module-jaxb-annotations:jar:2.3.2:compile
[INFO] +- org.springframework:spring-web:jar:4.0.2.RELEASE:compile
[INFO] | +- org.springframework:spring-aop:jar:4.0.2.RELEASE:compile
[INFO] | | \- aopalliance:aopalliance:jar:1.0:compile
[INFO] | +- org.springframework:spring-beans:jar:4.0.2.RELEASE:compile
[INFO] | +- org.springframework:spring-context:jar:4.0.2.RELEASE:compile
[INFO] | | \-
org.springframework:spring-expression:jar:4.0.2.RELEASE:compile
[INFO] | \- org.springframework:spring-core:jar:4.0.2.RELEASE:compile
[INFO] +- javax.servlet:javax.servlet-api:jar:3.1.0:provided
[INFO] +- org.esigate:esigate-core:jar:4.3:compile
[INFO] | +- org.apache.httpcomponents:httpclient:jar:4.2.6:compile
(version managed from 4.2.5)
[INFO] | | +- org.apache.httpcomponents:httpcore:jar:4.2.5:compile
[INFO] | | \- commons-codec:commons-codec:jar:1.9:compile (version
managed from 1.6)
[INFO] | +- commons-io:commons-io:jar:2.4:compile (version managed from
2.0.1)
[INFO] | +- nu.validator.htmlparser:htmlparser:jar:1.4:compile
[INFO] | +- org.apache.commons:commons-lang3:jar:3.3.1:compile (version
managed from 3.0.1)
[INFO] | +- org.slf4j:slf4j-api:jar:1.7.6:compile (version managed from
1.6.2)
[INFO] | +- org.slf4j:jcl-over-slf4j:jar:1.6.2:runtime
[INFO] | \- org.apache.httpcomponents:httpclient-cache:jar:4.2.5:compile
[INFO] +- commons-logging:commons-logging:jar:1.1.3:provided
[INFO] \- org.apache.commons:commons-vfs2:jar:2.0:compile
[INFO] +- org.apache.maven.scm:maven-scm-api:jar:1.4:compile
[INFO] | \- org.codehaus.plexus:plexus-utils:jar:1.5.6:compile
[INFO] \- org.apache.maven.scm:maven-scm-provider-svnexe:jar:1.4:compile
[INFO] +-
org.apache.maven.scm:maven-scm-provider-svn-commons:jar:1.4:compile
[INFO] \- regexp:regexp:jar:1.3:compile
b) additional resources outside the hierarchy
Fit module for instance references to root dir for getting its license file.
Can we avoid this root reference e.g. by having a copy task where the root
publish its sources to sub module?
That's true: fit references parent's license files.
Not sure about the proposed solution. I do think that parent license
dependency can be just removed.
I will remove this dependency ASAP but, if you prefer, change it by
yourself.
Best regards,
F.
Eclipse as IDE is very strict in hierarchies and allows only top down
dependencies. On the other hand it's not bad to keep sub module independent.
WDYT?
Greetings,
Stephan
--
Fabio Martelli
Tirasa - Open Source Excellence
http://www.tirasa.net/
Apache Syncope PMC
http://people.apache.org/~fmartelli/
