You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe your use-case which is not covered by existing documentation.
We wanted to use the classificationFilePattern argument in order to supply additional metadata to be displayed in the report.
However our .properties file kept getting ignored by cucumber-reporting plugin.
It took me quite some code-reading to discover why:
In CucumberReportPublisher#480 you save available property files below inputReportDirectory to directoryCache, so they can be evaluated later on.
However inputReportDirectory is based on plugin argument/setting jsonReportDirectory.
In our case jsonReportDirectory is set to Maven target subfolder, while the classification property file is residing in workspace root, so because of the above it never was included for the cache and subsequent processing. That was quite a surprise.
Could you add some appropriate advice in documentation, that (contrary to naming) jsonReportDirectory is not only effective for json reports, but also for classificationFilePattern parameter?
Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.
No response
The text was updated successfully, but these errors were encountered:
Describe your use-case which is not covered by existing documentation.
We wanted to use the classificationFilePattern argument in order to supply additional metadata to be displayed in the report.
However our .properties file kept getting ignored by cucumber-reporting plugin.
It took me quite some code-reading to discover why:
In CucumberReportPublisher#480 you save available property files below
inputReportDirectory
todirectoryCache
, so they can be evaluated later on.However
inputReportDirectory
is based on plugin argument/settingjsonReportDirectory
.In our case
jsonReportDirectory
is set to Maventarget
subfolder, while the classification property file is residing in workspace root, so because of the above it never was included for the cache and subsequent processing. That was quite a surprise.Could you add some appropriate advice in documentation, that (contrary to naming)
jsonReportDirectory
is not only effective for json reports, but also forclassificationFilePattern
parameter?Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.
No response
The text was updated successfully, but these errors were encountered: