sing the reason for the above code being implemented
>> the way it
>> is, is to allow easy handling of potential duplicates, the only
>> problem is
>> that the order is lost in the process. Or is this intentional, if
>> it is can
>> you explain why? If it
ubmit a JIRA request with my patch for it if that is the case.
Regards
Gareth Tilley
--
View this message in context: http://www.nabble.com/Dependency-
order-in-DefaultModelInheritanceAssembler-tf2187909.html#a6052791
Sent from the Maven Devel
ould think that there would be a large
benefit in changing the above code so that it maintains the order.
I'm happy
to submit a JIRA request with my patch for it if that is the case.
Regards
Gareth Tilley
--
View this message in context: http://www.nabble.com/D
ts not, I would think that there would be a large
benefit in changing the above code so that it maintains the order. I'm happy
to submit a JIRA request with my patch for it if that is the case.
Regards
Gareth Tilley
--
View this message in context:
http://www.nabble.com
