You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by GitBox <gi...@apache.org> on 2021/12/30 13:40:26 UTC

[GitHub] [felix-dev] laeubi commented on pull request #124: [FELIX-6493] Extend is-up-to-date logic of Manifest goal

laeubi commented on pull request #124:
URL: https://github.com/apache/felix-dev/pull/124#issuecomment-1003033763


   > > * consider pom.xml modifications in up-to-date logic
   > 
   > Actually the pom's of all parent projects have to be considered as well. I'm about to update this PR accordingly.
   
   I'm not sure if this is not a bit out of scope. I would assume that if one updates the parent he also has to update the child to reflect the new version?
   
   What I actually wonder is: Is there really a measurable benefit for all those stale checking? I could only think of a resource that was modified and thus do not change the generated manifest but does it really impact performance to regenerate the manifest in those scenarios?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@felix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org