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

[GitBox <gi...@apache.org>]

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


   > > From my recent observations the BND-Analyzer takes some time for larger projects with many classes to scan. So I think it is not worthless.
   > 
   > Sure but how often is an incremental build triggered that does _not_ is detected as a change? e.g if I see correctly it is only checked if a java file is affected but not if the change actually is a relevant change (e.g. if I just add a comment into a file this will still trigger generation of the manifest!).
   
   In general a change is not detected, if a non java resource is modified that is not copied into `target/classes`. It then depends on ones use cases/workspace. For some cases (like e.g. in our case in M2E where the project actually only contains a pom that specifies what is packed into a bundle) there are probably only very few cases where the manifest generation is skipped. But others might have other cases.
   
   > 
   > > So additional or modified java classes while cause later modifications in that directory
   > 
   > I'm not sure if this is always true as far as I know under linux one could disable that parents are updated.
   
   Of course one could disable autobuild in Eclipse (I don't know how other IDE handle it), but then no incremental builds happen anyways. But except this case, I don't know how to disable the write of compiled class files into target/classes directory?


-- 
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