Closed dergo closed 8 years ago
changed testapi-parent pom file.
Issue to be validated.
Validated OK: Utility documentation is generated! and wildcard are accepted!
Fix is not correct, configuration is still not correctly inherited from testapi-parent (you applied a workaround in demo/testapi to make it work, and the configuration is not even completely correct). You can use "mvn help:effective-pom" to check the effective pom in demo/testapi for example.
The problem seems to come from the <inherited>${plugins-inheritance}</inherited> tag in the testapi-parent, if I remove it the effective pom is correct, but I don't know why it has been added and if there are side-effects of removing it.
Actually I don't think the "inherited" tag should ever be used in a "pluginManagement" section, but only in "plugin" sections. "pluginManagement" is there expressly to define a default plugin configuration, so disabling inheritance would anyway be strange.
Fixed TestAPI documentation generation. To be validated.
The inherited tag has been removed, so if it causes an issue when doing a release, an other way to fix it will have to be found.
Could you check if it was fixed in 2.3.0 and simply regenerate the release notes? Thks
Fixed in 2.3.0.
In QTaste 2.1.0 and current 2.2.0-SNAPSHOT, the Test API documentation generated in /target/TestAPI-doc/ doesn't include the documentation of the other Test API on which the Test API depends anymore.
E.g. at BMS level, I had the documentation of BMS, BDS, BSS, ICOMP, QTaste-Toolbox, etc..., now I only have BMS documentation.
There is a maven inheritance configuration issue in qtaste-testapi-parent: the configuration of maven-dependency-plugin is not inherited anymore!
Also even if I override the configuration myself, JavaGUI is not included because the package name doesn't match the includes: <includes>*/qtaste/testapi/api/.java</includes> must be changed to: <includes>*/qtaste//testapi/api/.java</includes>