aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Ward (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-669) Proxy or weaving code should mark all its changes synthetic
Date Mon, 06 Jun 2011 23:05:59 GMT

    [ https://issues.apache.org/jira/browse/ARIES-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045196#comment-13045196
] 

Timothy Ward commented on ARIES-669:
------------------------------------

I would probably also subclass the Serial version UID adder but then expose the has SVUID
flag. I would then use this to make the SVUID synthetic as necessary and avoid copying any
ASM source. The principle is more or less identical though.

I can work through these changes in the morning assuming you don't mind a temporary reversion?
It would be nice to get the clinit behaviour right (I think your previous comment hits the
nail on the head for that one) and to avoid having any ASM licensed source if we don't really
need it.

Tim

> Proxy or weaving code should mark all its changes synthetic
> -----------------------------------------------------------
>
>                 Key: ARIES-669
>                 URL: https://issues.apache.org/jira/browse/ARIES-669
>             Project: Aries
>          Issue Type: Bug
>          Components: Proxy
>    Affects Versions: 0.4
>            Reporter: David Jencks
>
> In order to make it easier for OWB to ignore the additional goo added by the proxy/weaving
stuff, it should all be marked synthetic.  So far I've identified the added SerialVersionUID
field and static_init_* methods as causing problems with the jcdi tck.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message