commit | ebefa118a2ee10fb011128b93a50d29d0867883e | [log] [tgz] |
---|---|---|
author | Christoph Läubrich <mail@laeubi-soft.de> | Tue Dec 19 18:39:56 2023 +0100 |
committer | GitHub <noreply@github.com> | Tue Dec 19 12:39:56 2023 -0500 |
tree | 2d49d865357079cec9495d72d208f0b567c00a64 | |
parent | 811e3675d494433013bb6982fe954c0bcd8ff9e6 [diff] |
[MSHARED-1285] use an up-to-date scanner instead the newscanner (#77) * [MSHARED-1285] - exhibit incremental issue Current incremental build does not honor isUptodate(), so changed or removed target resources are not refreshed until sources are modified or a full build is performed. 2 new testcases exhibits this issue (one for missing target resource, one for modified target resource). As stub BuildContext provides appropriate isUptodate results, build should refresh this resources. Current implementation prevents BuildContext implementors to trigger appropriate resource refresh by tweaking isUptodate implementation. See javadoc in BuildContext#newScanner javadoc that advices that incremental build may be performed with a full resource scanning and a isUptodate call to refresh only needed resources. * MSHARED-1285 use an up-to-date scanner instead the newscanner Currently it could happen that the scanner misses changed files (because they are not part of the delta) or copies files even if they have not changed (e.g. because the output has changes). This uses now a different approach, instead of only handling the delta files, we scan all inputs and compare if they are up-to-date with the output. --------- Co-authored-by: Laurent Almeras <laurent.almeras@kobalt.fr> Co-authored-by: Christoph Läubrich <christoph@laeubi-soft.de>
You have found a bug or you have an idea for a cool new feature? Contributing code is a great way to give something back to the open source community. Before you dig right into the code, there are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
We accept Pull Requests via GitHub. The developer mailing list is the main channel of communication for contributors.
There are some guidelines which will make applying PRs easier for us:
git diff --check
before committing.[MSHARED-XXX] - Subject of the JIRA Ticket Optional supplemental description.
mvn -Prun-its verify
to assure nothing else was accidentally broken.If you plan to contribute on a regular basis, please consider filing a contributor license agreement.
For changes of a trivial nature to comments and documentation, it is not always necessary to create a new ticket in JIRA. In this case, it is appropriate to start the first line of a commit with ‘(doc)’ instead of a ticket number.