Hi, thanks for looking at https://issues.apache.org/jira/browse/TAVERNA-982 !
I found the easiest way to test the javadoc is to use: mvn clean javadoc:javadoc In the log output you will find good log lines line: Generating /home/stain/src/taverna/incubator-taverna-commandline/taverna-commandline-launcher/target/apidocs/org/apache/taverna/commandline/class-use/CommandLineOptionsImpl.html... Generating /home/stain/src/taverna/incubator-taverna-commandline/taverna-commandline-launcher/target/apidocs/org/apache/taverna/commandline/package-use.html... Building index for all the packages and classes... but also the kind of warnings TAVERNA-982 talks about: [WARNING] Javadoc Warnings [WARNING] /home/stain/src/taverna/incubator-taverna-commandline/taverna-commandline-common/src/main/java/org/apache/taverna/commandline/data/SaveResultsHandler.java:39: warning - Tag @link: reference not found: CommandLineResultListener [WARNING] /home/stain/src/taverna/incubator-taverna-commandline/taverna-commandline-common/src/main/java/org/apache/taverna/commandline/data/SaveResultsHandler.java:39: warning - Tag @see: reference not found: BaclavaHandler To fix these you would have to edit the javadoc at those lines (e.g. in https://github.com/apache/incubator-taverna-commandline/blob/master/taverna-commandline-common/src/main/java/org/apache/taverna/commandline/data/SaveResultsHandler.java#L35 - in this case neither CommandLineResultListener or BaclavaHandler are relevant class names anymore and both @see lines should be removed: https://github.com/search?q=org%3Aapache+CommandLineResultListener&type=Code I also think TestDatabaseConfigurationHandler can be removed altogether, it was commented out by Alexandra back in 2011: https://github.com/apache/incubator-taverna-commandline/commits/1bbcfc30b0685bf7b8b56e19a263b8606cea2c3b/taverna-commandline-common/src/test/java/net/sf/taverna/t2/commandline/TestDatabaseConfigurationHandler.java And for release 3.1.0 we disabled the database options of the command line anyway, as we can't use Hibernate under the Apache license. (although remnants of that functionality might still be around) I have now deleted TestDatabaseConfigurationHandler.java - but I agree there should be more tests of the command line itself, because now we just have: stain@biggiebuntu:~/src/taverna/incubator-taverna-commandline$ find -type f | grep -i test/java ./taverna-commandline-launcher/src/test/java/org/apache/taverna/commandline/TestCommandLineOptionsHandler.java ./taverna-commandline-tests/src/test/java/org/apache/taverna/commandline/WorkflowTestSuite.java ./taverna-commandline-tests/src/test/java/org/apache/taverna/commandline/WorkflowTestRunner.java ./taverna-commandline-tests/src/test/java/org/apache/taverna/commandline/TavernaCommandLineTest.java (The first checks parsing of -commandline=arguments, the others have to be tweaked and run manually to test the command line against an older version (e.g. 2.5.0) On 4 August 2016 at 01:27, Chamini Prashakthi Jayasinghe <[email protected]> wrote: > hI, > I got this kind of errors after run the testcase without comment mark. > Error:(32, 43) java: > org.apache.taverna.commandline.options.CommandLineOptions is abstract; > cannot be instantiated > Error:(35, 70) java: cannot find symbol > symbol: variable DataManagementConfiguration > location: class > org.apache.taverna.commandline.TestDatabaseConfigurationHandler > Error:(36, 37) java: cannot find symbol > symbol: variable DataManagementConfiguration > location: class > org.apache.taverna.commandline.TestDatabaseConfigurationHandler > > Regards chamini > > On Thu, Aug 4, 2016 at 5:53 AM, Gale Naylor <[email protected]> > wrote: > >> I think Chamini is getting errors AFTER un-commenting all the code in >> the TestDatabaseConfigurationHandler >> class. https://github.com/apache/ >> >> incubator-taverna-commandline/blob/master/taverna-commandline-common/src/test/java/org/apache/taverna/commandline/TestDatabaseConfigurationHandler.java >> >> I presume the code was commented out for a good reason (thus the errors), >> and I wonder why the TestDatabaseConfigurationHandler.java file is included >> in the distribution if all the code is commented out. >> >> Chamini, the README file ( >> >> https://github.com/apache/incubator-taverna-commandline/blob/master/README.md >> ) >> contains an example of using the command-line tool. Does this help? If not, >> can you provide a little more information about what you are trying to test >> and why? >> >> Thanks, >> >> Gale >> >> >> On Wed, Aug 3, 2016 at 11:30 AM Gale Naylor <[email protected]> >> wrote: >> >> > I'm wondering why the class TestDatabaseConfigurationHandler is commented >> > out... >> > >> > >> > >> https://github.com/apache/incubator-taverna-commandline/blob/master/taverna-commandline-common/src/test/java/org/apache/taverna/commandline/TestDatabaseConfigurationHandler.java >> > >> > >> > On Wed, Aug 3, 2016 at 10:19 AM Alan Williams <[email protected]> >> > wrote: >> > >> >> On 03-Aug-16 03:50, Chamini Prashakthi Jayasinghe wrote: >> >> > Hi all, >> >> > can someone explain me how to run the test case in Apache Taverna >> >> > Commandline common module.it is all commented and after remove >> comment >> >> mark >> >> > it shows errors. >> >> >> >> What errors are you getting? >> >> >> >> > regards chamini >> >> >> >> Alan >> >> >> >> >> -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons http://orcid.org/0000-0001-9842-9718
