[concurrency-interest] jcip annotations

Shaffer, Darron Darron_Shaffer at stercomm.com
Thu Dec 20 11:27:07 EST 2007


The presence of a runtime annotation means one more jar file to ship
with a product.  And one more to run past legal if it's a commercial
product.

 

________________________________

From: concurrency-interest-bounces at cs.oswego.edu
[mailto:concurrency-interest-bounces at cs.oswego.edu] On Behalf Of Tim
Peierls
Sent: Thursday, December 20, 2007 8:30 AM
To: Dhanji R. Prasanna
Cc: concurrency-interest
Subject: Re: [concurrency-interest] jcip annotations

 

On Dec 20, 2007 3:07 AM, Dhanji R. Prasanna <dhanji at gmail.com> wrote:

	I believe source-level retention would be the correct choice (at
best, class-level). 


At least class level, so tools like FindBugs can do their thing.

 

	I cannot see any value in them being retained at runtime and in
fact a potential nuisance to reflection and debugging...  


I'm curious, how is the presence of a runtime annotation a nuisance?

 

	I suppose it is trivial for me to recompile the annotations with
a reduced retention but I am curious as to the motivation behind
retaining them at runtime.


FindBugs does static analysis of bytecode, but other tools could do
dynamic analysis of running code. 

--tim

-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/attachments/20071220/ebad8618/attachment.html 


More information about the Concurrency-interest mailing list