Lifetime major improvement

By Miguel Mendes on 20 Sep 2017

Hello,


When I select a module, Lifetime detects if any other module becomes broken. If it does, I have to include the broken module. After that, Lifetime validates the new module and detects if the newly added module breaks other modules, and so on.


It seems that Lifetime only validates modules that are on the immediate next level of the module we are including.

Why doesn't Lifetime validade the whole tree recursively?


Today Example:

#1 Select Module A => Module B becomes broken

#2 Include Module B => Module C becomes broken

#3 Include Module C => Module D becomes broken

...

I want to publish Module A but I need to include Module B, C and D. But Lifetime only tells me that I need to include Module D after I include module C, but Lifetime only tells me that I need to include Module C after I include Module B...     get it?



Lifetime should tell me that I need to include Module B, C and D right after I selected Module A.


Thank you,


When you're talking about the modules, you mean eSpaces or applications? Just to get the idea clear

Miguel Mendes22 Sep 2017

eSpaces