Here are a couple of links that might help you test the Java Doc fixes:

http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javadoc.html

https://maven.apache.org/plugins/maven-javadoc-plugin/test-javadoc-mojo.html

On Thu, Aug 11, 2016 at 8:50 AM Gale Naylor <[email protected]>
wrote:

> Hi Chamini,
>
> Were you able to generate the Java Doc errors in Eclipse without errors?
>
> Gale
>
> On Wed, Aug 3, 2016 at 6:56 PM Gale Naylor <[email protected]>
> wrote:
>
>> Thank you for clarifying, Chamini!
>>
>> The Java Doc warnings listed in Taverna 982 occurred when the
>> Command-line Tool was being BUILT, not when it was running. The
>> Command-line Tool actually RUNS without errors (at least on the Hello World
>> example in the README file).
>>
>> If you are using an IDE, like Eclipse, can you generate the Java Docs
>> using Eclipse and see that there are no errors?
>>
>> I'm not sure how else to test that the issues have been resolved. Anyone
>> else have any suggestions?
>>
>> Gale
>>
>> On Wed, Aug 3, 2016 at 5:32 PM Chamini Prashakthi Jayasinghe <
>> [email protected]> wrote:
>>
>>> Gale,
>>> I tried to test case because i worked on Taverna 982 bug.How could i know
>>> the correctness of my code without running testcases.
>>> Regards Chamini
>>>
>>>
>>> On Thu, Aug 4, 2016 at 5:57 AM, 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
>>> >> >>
>>> >> >>
>>> >>
>>> >
>>> >
>>>
>>

Reply via email to