Community
Participate
Working Groups
Juno M4. The auto-tagging script should detect when ISV doc bundle needs to be built due to Javadoc or extension point doc changes outside the ISV doc bundles. Possible solution: 1. We keep a list of bundles that require a rebuild of a certain ISV doc bundle. 2. During the build we check whether the map file entry for one of the bundles in the list changed. If so, rebuild the ISV doc bundle.
I don't think I'll ever have time to fix this. Just tag it once a milestone (not when the build is running :-) and we're done :-)
The brute force method: The same tags can be used that are used to generate the report for each repo: git log --pretty=format:"" --name-only ${oldTag}..origin/integration \ sort -u | grep '\.java$' | grep -v internal | wc -l You get all of the non-internal package java changes. It's not an exact science, as you get 2 sets of false positives: 1) example and test plugins show changes. In some repos these bundles are in tests/ and examples/, but not all. 2) it doesn't take into account packages marked x-internal PW
This is irrelevant now as if it's not autodetected we have the force qualifier update files.
(In reply to Alexander Kurtakov from comment #3) > This is irrelevant now as if it's not autodetected we have the force > qualifier update files. OK, and with "we" you mean you are now going to track and update the qualifier since you consider an automate process a WONTFIX? If yes, you can close again, and thanks for doing that work :-).
