-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
-
pipeline-maven-plugin 3.10.0
The goal is the same as https://issues.jenkins-ci.org/browse/JENKINS-61092 but for the maven-frontend-plugin instead of the maven-karma one.
The major difference is where the karma plugin overload the karma configuration of the projet, to add the requirements for JUnit compatible XML outputs, thus knowing where these reports will be, the frontend plugin does not alter karma configuration. So you have to add what is needed yourself, and thus the output directory is only known by karma, not the plugin, so not exposed ...
- relates to
-
-
- Closed
-
- links to
[JENKINS-63689] supports maven-frontend-plugin
benoit guerin
created issue -
benoit guerin
made changes -
| Remote Link | New: This issue links to "Pull Request #281 (Web Link)" [ 25902 ] |
benoit guerin
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
benoit guerin
made changes -
| Link |
New:
This issue relates to |
benoit guerin
made changes -
| Description |
New:
The goal is the same as https://issues.jenkins-ci.org/browse/JENKINS-61092 but for the [maven-frontend-plugin|https://github.com/eirslett/frontend-maven-plugin] instead of the maven-karma one. The major difference is where the karma plugin overload the karma configuration of the projet, to add the requirements for JUnit compatible XML outputs, thus knowing where these reports will be, the frontend plugin does not alter karma configuration. So you have to add what is needed yourself, and thus the output directory is only known by karma, not the plugin, so not exposed ... |
| Released As | New: pipeline-maven-plugin 3.10.0 | |
| Assignee | New: benoit guerin [ falcon ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Fixed but Unreleased [ 10203 ] |
| Status | Original: Fixed but Unreleased [ 10203 ] | New: Closed [ 6 ] |