4

I am building a DXA 1.7 web application for SDL Web 8.5 (using CIL). It is failing because on our build environment we only have access to Maven Central. It is failing on three types of dependencies, all of which I have questions about:

  1. External dependencies - EasyLicense - Since I am using CIL this should not be needed right? Is there a certain profile/setting that I can set so it does not include this dependency?

  2. SDL dependencies - Why are these not in Maven Central like the others?

  3. Custom DD4T 2.0 dependencies - What has been customized in DD4T and why?

5

For future reference: We had to put the artifacts from #3 in the local repository, after that the build worked. We did not need to exclude #1 and #2.
(I must post this as an anwser since I am not permitted to comment)

  • You don't have to apologize; this looks like a genuine Answer to me. :-) – Rick Pannekoek Jul 6 '17 at 17:56
6
  1. You don't need easylicense, that's right. There were some known (and fixed in some later versions) bugs in CIL when some artifacts were still dependent on CIS stuff. Simply exclude easylicense from the build then.
  2. Same as with #1. I don't see them in DXA poms, and I am surprised that you have these problems. Apparently, they come through CIL dependency. The only nice way then to build the framework is to exclude those transitive dependencies.
  3. Although this is not really nice, it's a mistake made when first migrated to SDL Web 8. This is not DD4T 2, this is DD4T 1.something. That time there was no support of Web 8 in DD4T, so this is a custom fork implementing really basic things to support it. Currently it's a legacy mistake that better should be re-worked

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.