Closed 480Oswego2013 closed 11 years ago
Honestly, I think this would be better to just have the generated javadocs for. Make sure each test is well documented in the code and just generate the javadocs for all the tests.
not a bad idea- though im no pro at making java docs, any tips on where i should look or how to make them?
mvn site && firefox target/site/testapidocs/index.html
Since a home page is being created for this app, the entire contents of target/site could be uploaded and made public there.
the web page is not that ellaborate. its simply a couple of links, to github,to the wiki, and one to the webpage
right, when you run "mvn site" it basically generates a website for your app. some of it has already been customized, but a few more tweaks and you pretty much have what is needed.
just fire up target/site/index.html and you will see what i am talking about
how do i do that in netbeans? or terminal should i install maven on my machine? do i need maven 3?
run it from the terminal.
i think im getting close i got a website that looks like java7 api
try going up a directory to target/site/index.html and you will see the full site with reports and everything.
i am not sure we need this page any more since the web page has this included in it already. Ill close it at the end of the day if no one has any objections.
provided maven site includes javadocs and test coverage report, so I think I agree that this is redundant.
On Mon, May 13, 2013 at 4:57 PM, 480Oswego2013 notifications@github.comwrote:
i am not sure we need this page any more since the web page has this included in it already. Ill close it at the end of the day if no one has any objections.
— Reply to this email directly or view it on GitHubhttps://github.com/480Oswego2013/CSC-HCI-480-2013-repo/issues/53#issuecomment-17840170 .
The build doc should just include a summery of all the test we made and how they work. feel free to make your own summery and submitt them on the wiki