edemo / PDEngine

voting engine using ADA authentication and condorcet method
Other
2 stars 12 forks source link

javadoc does not find packages #140

Open magwas opened 5 years ago

magwas commented 5 years ago

This is a DevOps issue, no testcases are needed. We count this issue as 3 testcases. the following should be eliminated from the javadoc run output: " error: cannot find symbol" and "error: package .* does not exist" solution: https://stackoverflow.com/questions/45075521/javadoc-suppress-package-does-not-exist-for-external-references-without

szirbucz commented 5 years ago

@magwas, running mvn javadoc:javadoc gives no error. How can I reproduce the issue?

magwas commented 5 years ago

make javadoc

magwas commented 5 years ago

To understand the testenvironment, here is a yet unpublished raw video about it: https://drive.google.com/open?id=1xZzLZrgNEnvVGZhri1TmXaQSW8wDfYM2

magwas commented 5 years ago

It would be nice if you could include those javadoc runs into one of the mvn runs, The point is that the documentation generation needs the xml generated by javadoc to extract implemented behaviours. There is no html generated yet, which in tudn would be nice as a developer documentation.

szirbucz commented 5 years ago

szirbucz

szirbucz commented 5 years ago

@magwas: Warning messages have been disappeared due to the applied modifications and additionally, we have HTML version of javadocs under target/site/project-reports.html Please check if the generated XML-s are fit for the requirements. As far as I see, they are a bit more verbose.

magwas commented 5 years ago

The behaviour doc seems to generate correctly.