Continuing software archaeology: confmappingoverride is in both dependencies and configurations in ivy.xsd on 1.4.x branch.
Gintas 2017-09-24 7:11 GMT+02:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > I carry on talking to myself:-) according to ivy.xsd, all three attributes > can be used on both dependencies and configurations. So, it's the > documentation that must be adjusted accordingly... any opinions whether > that deserves a separate Jira issue? > > Gintas > > 2017-09-23 17:10 GMT+02:00 Gintautas Grigelionis <g.grigelio...@gmail.com> > : > >> Re IVY-1420/IVY-1437: there's yet another bug related to duplicated >> defaultconf/defaultconfmapping attributes. >> >> The specification says that confmappingoverride belongs to >> configurations. The way XmlModuleDescriptorUpdater looks -- check out >> startDependencies method -- it is set in dependencies element. >> >> So, what is the best solution: warn that attribute will be ignored or >> allow the same attributes for dependencies and configurations? >> >> Gintas >> >> 2017-09-19 7:54 GMT+02:00 Gintautas Grigelionis <g.grigelio...@gmail.com> >> : >> >>> I believe the reason of having the same attributes in different sections >>> of Ivy files is being able to inherit them selectively; thus they must be >>> remain in the same section where they were set originally. >>> >>> Gintas >>> >>> 2017-09-19 7:42 GMT+02:00 Gintautas Grigelionis <g.grigelio...@gmail.com >>> >: >>> >>>> Looking at IVY-1420/IVY-1437 it appears that defaultconf and >>>> defaultconfmapping attributes were first used with dependencies and were >>>> duplicated in configurations afterwards; would it be sufficient to put them >>>> only on dependencies (that's how current code works)? I would be very >>>> grateful for any useful pointers regarding the design of these features. >>>> >>>> Gintas >>>> >>>> >>> >> >
