[
https://issues.apache.org/jira/browse/TOBAGO-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462166
]
Volker Weber commented on TOBAGO-228:
-
for a workarround in 1.0.9 you can use the attached files:
put the file
[
https://issues.apache.org/jira/browse/TOBAGO-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462167
]
Volker Weber commented on TOBAGO-225:
-
see TOBAGO-228 for a workarround
tc:box with height on tree display was
AJAX-reload of scrollable Sheets resets scrollbar to top position
-
Key: TOBAGO-229
URL: https://issues.apache.org/jira/browse/TOBAGO-229
Project: MyFaces Tobago
Issue Type:
[
https://issues.apache.org/jira/browse/TOBAGO-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-228.
-
Resolution: Fixed
css classes for tree are missing after renaming tree to treeOld
[
https://issues.apache.org/jira/browse/TOBAGO-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-225.
-
Resolution: Fixed
tc:box with height on tree display was not able to display scroable body
[
https://issues.apache.org/jira/browse/TOBAGO-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462199
]
Udo Schnurpfeil commented on TOBAGO-228:
Yes, the tobago-tree- must be replaced by tobago-treeOld-. But the
Exception when using umlauts in confirm component
-
Key: TOBAGO-230
URL: https://issues.apache.org/jira/browse/TOBAGO-230
Project: MyFaces Tobago
Issue Type: Bug
Components: Core
[
https://issues.apache.org/jira/browse/TOBAGO-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-230.
-
Resolution: Fixed
Exception when using umlauts in confirm component
[
https://issues.apache.org/jira/browse/TOBAGO-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-218.
-
Resolution: Fixed
Fix Version/s: 1.0.10
tobago throws an exception after validation
[
https://issues.apache.org/jira/browse/TOMAHAWK-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cagatay Civici resolved TOMAHAWK-805.
-
Resolution: Fixed
Fix Version/s: 1.1.5-SNAPSHOT
Move sandbox selectItems to
Problem when t:popup is into t:div with IE
--
Key: TOMAHAWK-841
URL: https://issues.apache.org/jira/browse/TOMAHAWK-841
Project: MyFaces Tomahawk
Issue Type: Bug
Components: Popup
[
https://issues.apache.org/jira/browse/TOBAGO-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462223
]
Sam Wong commented on TOBAGO-228:
-
I replace the html_scarborough_mozilla_style_style.css and named style.css
into
[
https://issues.apache.org/jira/browse/TOMAHAWK-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462253
]
Paul Pogonyshev commented on TOMAHAWK-186:
--
Set `locale' attribute on f:view tag.
inputCalendar - how
popup is active for disabled calendar components
Key: TOMAHAWK-842
URL: https://issues.apache.org/jira/browse/TOMAHAWK-842
Project: MyFaces Tomahawk
Issue Type: Bug
Affects Versions:
[
https://issues.apache.org/jira/browse/TOBAGO-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-107.
--
Resolution: Fixed
tc:page should use a reasonable default width+height and state
[
https://issues.apache.org/jira/browse/TOBAGO-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-217.
--
Resolution: Fixed
Create a popup ref tag
--
Key:
We don't have one.
It's frequently requested.
+1 on creating a 1.1.4.1 maintenance branch.
On 1/4/07, Stan Silvert [EMAIL PROTECTED] wrote:
Are we maintaining a service pack type of branch for MyFaces 1.1.4 core?
There is a critical portlet bug that is fixed in 1.1.5, but I don't think we
Is their a reason NOT to release 1.1.5?
Based on a Tomcat style release model I purposed earlier [1] we can
label this release Alpha status and change it's status later.
Assuming the current source is stable, which it appeared to be as
of this weekend, we can release it meets the requirement for
Hi Paul,
1) Mitigates the need for a 1.1.4.1 branch.
There is still some small value for orgs that want the one fix w/out the
inherit risk that comes with a new release of any piece of software. I do
agree with you that a 1.1.5 release would be a better use of resources though.
2) No need to
[release 1.1.5 now instead]
1) Mitigates the need for a 1.1.4.1 branch.
Not really. In all likelihood, there are always going to be bugs in
the latest release since new features are constantly being worked on.
Users want to have access to a bug-fix release that does not add new
features.
2)
Dennis Byrne wrote:
Hi Paul,
1) Mitigates the need for a 1.1.4.1 branch.
There is still some small value for orgs that want the one fix w/out
the inherit risk that comes with a new release of any piece of
software. I do agree with you that a 1.1.5 release would be a better
use of resources
Hello,
is the new copyright policy a blocker for a 1.1.4.1 release?
See: http://www.apache.org/legal/src-headers.html
Regards
Bernd
Paul Spencer wrote:
Dennis Byrne wrote:
Hi Paul,
1) Mitigates the need for a 1.1.4.1 branch.
There is still some small value for orgs that want the one
Mike Kienenberger wrote:
[release 1.1.5 now instead]
1) Mitigates the need for a 1.1.4.1 branch.
Not really. In all likelihood, there are always going to be bugs in
the latest release since new features are constantly being worked on.
Users want to have access to a bug-fix release that does
myfaces not releasing memory gracefully?
Key: TOMAHAWK-843
URL: https://issues.apache.org/jira/browse/TOMAHAWK-843
Project: MyFaces Tomahawk
Issue Type: Bug
Affects Versions: 1.1.3
Problem with input validation and tab group
---
Key: TOBAGO-231
URL: https://issues.apache.org/jira/browse/TOBAGO-231
Project: MyFaces Tobago
Issue Type: Bug
Components: Core
Affects
On 1/4/07, Paul Spencer [EMAIL PROTECTED] wrote:
Is their a reason NOT to release 1.1.5?
Yes. There are still open issues for 1.1.5. MYFACES-1411 is the one
that concerns me. I'm not familiar with the situation, I just flagged
it as a contribution of new classes with no CLA on file.
--
On 1/4/07, Bernd Bohmann [EMAIL PROTECTED] wrote:
is the new copyright policy a blocker for a 1.1.4.1 release?
See: http://www.apache.org/legal/src-headers.html
Yes, but it's fairly simple to fix. I think the Maven developers have
been using an IDEA plugin to do it, and there are some
27 matches
Mail list logo