[
https://issues.jboss.org/browse/RF-12745?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-12745:
------------------------------------
If we @ Deprecated a method in RichFaces 4, we can remove that method in RichFaces 5. We
don't need to constrain the RichFaces 5 API unnecessarily with RichFaces 4
deprecations.
Re: the EL API changes, here's a good
stackoverflow.com question describing how to use
the replacement API:
http://stackoverflow.com/questions/2158009/deprecated-richfaces-javax-fac...
What do you mean by:
{quote}
I think this can't be simply worked around because of wrong consequences
{quote}
What "wrong consequences"?
I'll take a stab at implementing the new EL API.
Assess and fix deprecations in Maven compile step
-------------------------------------------------
Key: RF-12745
URL:
https://issues.jboss.org/browse/RF-12745
Project: RichFaces
Issue Type: Task
Security Level: Public(Everyone can see)
Components: build/distribution
Affects Versions: 5.0.0.Alpha1
Reporter: Lukáš Fryč
Assignee: Brian Leathem
Labels: rf5-build
Fix For: 5.0.0.Alpha1
Original Estimate: 3 hours
Remaining Estimate: 3 hours
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira