That's a good point.  I guess it shows that people working on T5 apps
aren't using JDK 1.7, or have already discoverred they need to compile
with 1.6 or earlier bytecode.

On Wed, May 9, 2012 at 5:48 PM, Bob Harner <[email protected]> wrote:
> So does this mean (and should we document) that applications using
> Tapestry 5.3 should be built using a 1.5 or 1.6 compiler compliance
> level, but not 1.7? I assume so, but I don't remember seeing that
> documented anywhere.
>
> On Wed, May 9, 2012 at 2:49 PM, Howard M. Lewis Ship (JIRA)
> <[email protected]> wrote:
>>
>>     [ 
>> https://issues.apache.org/jira/browse/TAP5-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>  ]
>>
>> Howard M. Lewis Ship updated TAP5-1852:
>> ---------------------------------------
>>
>>
>> This is going to be very important, as ASM 3 doesn't understand JDK 7 
>> bytecode.
>>
>>> Upgrade Plastic to use ASM 4.0
>>> ------------------------------
>>>
>>>                 Key: TAP5-1852
>>>                 URL: https://issues.apache.org/jira/browse/TAP5-1852
>>>             Project: Tapestry 5
>>>          Issue Type: Task
>>>          Components: plastic
>>>    Affects Versions: 5.4
>>>            Reporter: Howard M. Lewis Ship
>>>
>>> Change the embedded (and repackaged) version of ASM from 3.3.1 to 4.0.
>>
>> --
>> This message is automatically generated by JIRA.
>> If you think it was sent incorrectly, please contact your JIRA 
>> administrators: 
>> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>



-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to