+1 for the first one as well, since I already have a few of such issues.
Some of them can be solved on 2.0 level but not exposed (like our
working queue handling) some of them really need a spec change (like the
semi broken viewstate handling on protocol level)
Werner
Am 09.07.10 03:29, schrieb Hazem Saleh:
+1 for the first option.
On Thu, Jul 8, 2010 at 1:39 PM, Gerhard Petracek
<gerhard.petra...@gmail.com <mailto:gerhard.petra...@gmail.com>> wrote:
+1 for #1
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2010/7/8 Jan-Kees van Andel <jankeesvanan...@gmail.com
<mailto:jankeesvanan...@gmail.com>>
+1 on the first option.
/JK
2010/7/8 Jakob Korherr <jakob.korh...@gmail.com
<mailto:jakob.korh...@gmail.com>>
Hi guys,
Since there are currently some issues in the JIRA, which we
can't fix now, because they require a spec behavior change,
but which should be fixed for JSF 2.1, I was thinking of
some way to mark them. There are two options:
1) Simply create a 2.1.0 version and change the Affects
Version/s of those issues to 2.1.0
2) Create a parent issue and convert all those issues to
sub-tasks
Frankly I would prefer the first option. What do you guys think?
Regards,
Jakob
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
--
Hazem Ahmed Saleh Ahmed
Author of (The Definitive Guide to Apache MyFaces and Facelets):
http://www.amazon.com/Definitive-Guide-Apache-MyFaces-Facelets/dp/1590597370
http://www.amazon.com/-/e/B002M052KY
Web blog: http://hazems.blogetery.com/
[Web 2.0] Mashups Integration with JSF:
http://code.google.com/p/mashups4jsf/
