Skip to content

Conversation

@Steffengreiner
Copy link
Contributor

Description of changes
This plugin enables the groovydoc maven plugin to function properly by including it in the report section of the pom.xml.
This is necessary to include the linkage to the generated groovydocs in project overview page.

Additional context
This can be easily tested by running mvn site and checking if there is a project reports section in the generated index.html file in the target/site/ directory. (Open it in your favorite browser to see the generated html document)
Without the plugin addition to the pom.xml the index.html will lack a dedicated project report section
Bildschirmfoto 2021-07-07 um 16 48 56
With the plugin addition to the pom.xml the index.html will include the project reports section:
Bildschirmfoto 2021-07-07 um 16 48 51

@Steffengreiner Steffengreiner changed the title Include groovydoc plugin in report generation Include groovydoc plugin in pom.xml to enable report generation Jul 7, 2021
@jenniferboedker jenniferboedker merged commit d3d5f73 into development Feb 8, 2022
@jenniferboedker jenniferboedker deleted the fix/groovydoc-report-generation branch February 8, 2022 12:45
wow-such-code added a commit that referenced this pull request May 6, 2022
* Sync with hotfix 1.9.2 (#69)

* Hotfix 1.9.1 (#66)

* Fix RST syntax error

* Remove orphaned print statement

* Update CL

* Bump version 1.9.1 -> 1.9.2

Co-authored-by: Steffengreiner <[email protected]>

* Update maxquant file parser (#74)

The summary file is now searched within the summary folder

* Remove qube files and Bump version to 1.11.0-SNAPSHOT

* Bump conf.py to current version

* Bump version to 1.11.0-SNAPSHOT

* Include groovydoc plugin in report generation (#59)

* Feature/update nanopore (#91)

* increase some versions, fix testing env

* add tests for alternative nanopore structure

* Add worflow triggers (#93)

* Add triggers

* Reorder git commands

* Use master as base, not main

* parser

* update workflows (#94)

* Set version to 1.10.6

* update pom

* Fix project setup (#96)

* add possibility of some metadata values being empty

* comments

* extract method to validate a single schema

Co-authored-by: Sven F <[email protected]>
Co-authored-by: JohnnyQ5 <[email protected]>
Co-authored-by: Steffengreiner <[email protected]>
Co-authored-by: Sven F <[email protected]>

* Feature/update nanopore (#97)

* increase some versions, fix testing env

* add tests for alternative nanopore structure

* Add worflow triggers (#93)

* Add triggers

* Reorder git commands

* Use master as base, not main

* parser

* update workflows (#94)

* Set version to 1.10.6

* update pom

* Fix project setup (#96)

* add possibility of some metadata values being empty

* comments

* extract method to validate a single schema

* use data-model-lib release

Co-authored-by: Sven F <[email protected]>
Co-authored-by: JohnnyQ5 <[email protected]>
Co-authored-by: Steffengreiner <[email protected]>
Co-authored-by: Sven F <[email protected]>

* Update CHANGELOG.rst

Co-authored-by: Tobias Koch <[email protected]>

Co-authored-by: Sven F <[email protected]>
Co-authored-by: Steffengreiner <[email protected]>
Co-authored-by: jnnfr <[email protected]>
Co-authored-by: JohnnyQ5 <[email protected]>
Co-authored-by: Sven F <[email protected]>
Co-authored-by: Tobias Koch <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants