Agreed; <name> will cause Java 8 Javadoc to report errors.
If you don't want to use @code, one can always use {name} or [name] instead.
Just don't use HTML tag delimiters ...
On 13 April 2014 18:21, Gary Gregory <[email protected]> wrote:
> -1 to using <> instead of {@code}
>
> Gary
>
> <div>-------- Original message --------</div><div>From: Bernd
> <[email protected]> </div><div>Date:04/13/2014 10:50 (GMT-05:00)
> </div><div>To: Commons Developers List <[email protected]>
> </div><div>Subject: Re: svn commit: r1586926 - in
> /commons/proper/dbcp/trunk/src/test/java/org/apache/commons/dbcp2:
> TestConnectionPool.java TestPStmtPoolingBasicDataSource.java </div><div>
> </div>Hello,
>
> Am 13.04.2014 08:11 schrieb <[email protected]>:
>>
>> Author: psteitz
>> Date: Sun Apr 13 06:10:44 2014
>> New Revision: 1586926
>>
>> URL: http://svn.apache.org/r1586926
>> Log:
>> Added test (commented out) to illustrate DBCP-415.
>>
>> Modified:
>>
> commons/proper/dbcp/trunk/src/test/java/org/apache/commons/dbcp2/TestConnectionPool.java
>>
> commons/proper/dbcp/trunk/src/test/java/org/apache/commons/dbcp2/TestPStmtPoolingBasicDataSource.java
>>
>> Modified:
> commons/proper/dbcp/trunk/src/test/java/org/apache/commons/dbcp2/TestConnectionPool.java
>> URL:
> http://svn.apache.org/viewvc/commons/proper/dbcp/trunk/src/test/java/org/apache/commons/dbcp2/TestConnectionPool.java?rev=1586926&r1=1586925&r2=1586926&view=diff
>>
> ==============================================================================
>> ---
> commons/proper/dbcp/trunk/src/test/java/org/apache/commons/dbcp2/TestConnectionPool.java
> (original)
>> +++
> commons/proper/dbcp/trunk/src/test/java/org/apache/commons/dbcp2/TestConnectionPool.java
> Sun Apr 13 06:10:44 2014
> ...
>> + /**
>> + * Launches a group of <numThreads> threads, each of which will
> attempt to obtain a connection
>
> Is using <name> a good idea in Javadoc? I think officially you would need
> to use @{code name}.
>
> ...
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
