/browse/MYFACES-1570
Project: MyFaces Core
Issue Type: Bug
Components: JSR-127
Affects Versions: 1.1.6-SNAPSHOT, 1.1.6
Environment: 1.1.5 tomahawk with 1.1.6 myfaces
Reporter: Mike Kienenberger
Assigned To: Martin Marinschek
I opened an issue and appended the details.
http://issues.apache.org/jira/browse/MYFACES-1570
On 3/20/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
Hey Martin,
It looks like you deprecated
org.apache.myfaces.renderkit.html.HtmlResponseStateManager.writeStateAsUrlParams()
-- demolished might
[
https://issues.apache.org/jira/browse/MYFACES-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482607
]
Mike Kienenberger commented on MYFACES-1570:
I think the references to the method should be removed
+1
On 3/19/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hello,
last week I sent out the proposal for the donation of RCF from Oracle
to the ASF. The proposal mentioned, that we need to do a vote on the
MyFaces PMC of being the Sponsoring Entity of that *podling*. After
finding the sponsor,
[
https://issues.apache.org/jira/browse/TOMAHAWK-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Kienenberger reopened TOMAHAWK-934:
After reading this more carefully, the problem is on the MyFaces side.
commons
that strong
opinion on TLP or subproject, but after reading Mario's mail a second
time and now yours, I'd agree.
Regarding, Trinidad as *base*, that's the way Oracle is using in the RCF.
-Matthias
On 3/15/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
I'd strongly prefer to see Trinidad
Yes.
h:selectOneMenu id=doors value=#{carconf.doors}
f:selectItem itemValue=2 itemLabel=2 /
f:selectItem itemValue=4 itemLabel=4 /
f:selectItem itemValue=7 itemLabel=7 /
/h:selectOneMenu
public void setDoors(int
Still a huge first step would be a myfaces commons, containing stuff
like updateActionlistener and validators/converters.
On 3/15/07, Gary VanMatre [EMAIL PROTECTED] wrote:
I would think that even moving the validators and converters out would be a
big step since they provide client side
Wessendorf [EMAIL PROTECTED] wrote:
On 3/15/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
One big concern I have is that we do not go to such an extreme (like
Tobago did) that we are no longer compatible with other component
sets. Once you start requiring a specific kind of form or document
I took a look at SortableModel and t:dataTable sorting again last
night. My requirements in most cases are to simply specify a sort
order in the page code, not to allow end-users to manipulate the sort
order.From what I can tell, there's no easy way to do this. I
documented the most
Unfortunately, I haven't. I'm likely to be pulling down the latest
MyFaces code in the next week or two and implementing a few things.
If no one else has gotten to it by then, I'll try to do it at that
point.
On the bright side, your issue has helped me dodge a number of
potential issues by
[
https://issues.apache.org/jira/browse/MYFACES-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480921
]
Mike Kienenberger commented on MYFACES-790:
---
Carsten,
It is your responsiblity as the programmer
[
https://issues.apache.org/jira/browse/MYFACES-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480932
]
Mike Kienenberger commented on MYFACES-790:
---
Thomas,
I took a look at 4.1.13.2. There's nothing
It would be more helpful if you commented directly on each of the
following issues where it's not obvious if it's fixed or invalid.
Your comment should prove that the issue is either fixed or no longer
valid.
For instance, it's not clear to me that TOMAHAWK-11 is fixed.
On 3/14/07, Zdeněk
TOMAHAWK-420 is not invalid or fixed. It's incomplete -- I've never
gotten back to finishing it.
On 3/14/07, Zdeněk Sochor [EMAIL PROTECTED] wrote:
Hi,
as much as i hate responding to my own message, BUT:
Can someone review these issues (IMO fixed or invalid)?
TOMAHAWK-11
TOMAHAWK-207
[
https://issues.apache.org/jira/browse/TOMAHAWK-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Kienenberger resolved TOMAHAWK-846.
Resolution: Fixed
Fix Version/s: 1.1.5-SNAPSHOT
Diana reports
[
https://issues.apache.org/jira/browse/TOMAHAWK-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478102
]
Mike Kienenberger commented on TOMAHAWK-915:
Close, but not correct.
You need to use triggerComponent
[
https://issues.apache.org/jira/browse/TOMAHAWK-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Kienenberger resolved TOMAHAWK-915.
Resolution: Fixed
Fix Version/s: 1.1.6-SNAPSHOT
I think this takes care
[
https://issues.apache.org/jira/browse/TOMAHAWK-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Kienenberger resolved TOMAHAWK-917.
Resolution: Fixed
Fix Version/s: 1.1.5-SNAPSHOT
Fixed.
t:columns
Affects Versions: 1.1.4-SNAPSHOT, 1.1.5-SNAPSHOT
Reporter: Mike Kienenberger
Assigned To: Mike Kienenberger
Priority: Minor
Fix For: 1.1.5-SNAPSHOT
Updated to http://jscook.sourceforge.net/JSCookMenu
--
This message is automatically generated
Versions: 1.1.4-SNAPSHOT, 1.1.5-SNAPSHOT
Reporter: Mike Kienenberger
Assigned To: Mike Kienenberger
Priority: Minor
Fix For: 1.1.5-SNAPSHOT
Improve description of buffer in apt documentation.
Change
This component allows you to render a part
[
https://issues.apache.org/jira/browse/TOMAHAWK-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Kienenberger resolved TOMAHAWK-919.
Resolution: Fixed
Updated.
Improve description of buffer in apt documentation
: UpdateActionListener
Affects Versions: 1.1.4-SNAPSHOT, 1.1.5-SNAPSHOT
Reporter: Mike Kienenberger
There's no xdocs or apt docs for updateActionListener. The only documentation
is on the wiki.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment
: Improvement
Components: Validators
Affects Versions: 1.1.4-SNAPSHOT, 1.1.5-SNAPSHOT
Reporter: Mike Kienenberger
Assigned To: Mike Kienenberger
Priority: Minor
Fix For: 1.1.5-SNAPSHOT
Improve usage example for validateEqual by adding second
[
https://issues.apache.org/jira/browse/TOMAHAWK-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Kienenberger resolved TOMAHAWK-921.
Resolution: Fixed
Updated.
Improve usage example for validateEqual by adding
Top 5
On 3/3/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Another question is, if I should allow you to vote for each name, or if
I should force you to cast your vote for e.g. 5 names only.
Then changing the available vote selections should be 0 1 2 3 4 5, no?
Hi!
Using Apache MyFaces
Affects Versions: 1.1.3, 1.1.4-SNAPSHOT, 1.1.5-SNAPSHOT
Reporter: Mike Kienenberger
Priority: Critical
The jslistener.jsf example no longer works. Not sure when it broke.
http://www.irian.at/myfaces/jslistener.jsf
http://example.irian.at/example-simple-20070303
Came across this today -- For facelets and JSF RI 1.2, you have to
manually add the following to your form in order for an action to be
triggered by a navigationMenuItem enclosed in a jscookMenu component.
input type=hidden name=jscook_action /
Does anyone know if this is fixed in the latest
I'm not really heavily involved at this time. I'd be a poor choice.
On 3/2/07, Werner Punz [EMAIL PROTECTED] wrote:
Kito D. Mann schrieb:
Hello everyone,
I'd like to conduct a new e-mail interview with one or two people from
the MyFaces Core team. The last one was in 2004
SubmitOnEvent doesn't work as child of h:selectOneMenu without
explicit id. If 'id=choiceInput' is removed from the example code
below, no submit occurs.
sandbox:subForm id=choiceForm
h:selectOneMenu id=choiceInput
value=#{page.choice}
f:selectItems
My copy of the sandbox is so old, it doesn't even have the component :-)
I manually copied it into my project on Jan 24th, though.
Here's what the non-working html contains:
==
script type=text/javascript
function chooseMemberForm_submit() {
var form =
Not sure if this is relevent, but there are some errors when I first
load the page, even though there's no errors when I select a row.
=
Error: clear_masterForm is not defined
Source File: http://localhost:8089/faces/pages/connect.xhtml
Line: 1
Error:
Jeff,
I think a single diff file is easier, so go ahead and update the documentation.
On 3/2/07, Jeff Bischoff (JIRA) dev@myfaces.apache.org wrote:
[
https://issues.apache.org/jira/browse/TOMAHAWK-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477427
On 3/2/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Ok, its getting hot now, there is a difference between your two html
snippets:
not working
select size=1
name=masterForm:connectPageForm:chooseMemberForm:_id48
working
select size=1
Hey Mario.
Thanks for taking the time to step through this with me. You are
correct -- the version I had was quite different from the version in
trunk. The bug goes away once I upgrade to the new version. I must
have downloaded the wrong version by mistake.
On 3/2/07, Mario Ivankovits
As I was dealing with the submitOnEvent error, one thing I noticed is
that there's no svn info in the javascript file. This made it hard
to know what revision of the file I was working with. Should we be
including an id tag in there, or was it left out intentionally?
Issue Type: Improvement
Components: submitOnEvent
Affects Versions: 1.1.5-SNAPSHOT
Reporter: Mike Kienenberger
Priority: Minor
One thing that I had issues with for submitOnEvent is that the default
event is keyPress. I didn't realize that the default event
Mario,
One thing that I had issues with for submitOnEvent is that the default
event is keyPress. Until I found the hidden wiki docs for
submitOnEvent (I've made them more visible now :-), I didn't realize
that the default wouldn't work for a selectOneUI.
Is there any chance we can have
What's the spec say about UIInput's getValue()? If it's silent, I'd
say your solution makes sense.
On 3/1/07, Martin Marinschek [EMAIL PROTECTED] wrote:
Wanted to discuss a small thing with you:
UIOutput currently has the following code:
public Object getValue()
{
if
Might be significant that two people have asked this question so far :-)
On 3/1/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi !
Just out of curiosity, why is this part of MyFaces as opposed to Shale. It
sounds more like something that belongs there...
We developed it under the MyFaces
are wrong-doers for every component
attribute of every component, even if the chance is rather small that
the issue arises for normal attributes (it might definitely happen
though).
regards,
Martin
On 3/1/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
What's the spec say about UIInput's getValue
It probably sounds like Clever.
It looks like Keebler (a cookie/cracker manufacturer).
On 2/28/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hey,
I wonder how Kleber sounds for English native speakers?
I bet it sounds horrible . I hope so :-)
Ciao,
Mario
Guy,
In your particular case, you can try to use
f:selectItem itemValue={1} itemLabel=1 /
On 2/28/07, Guy Coleman [EMAIL PROTECTED] wrote:
On 27/02/2007 15:23, Dainius Vaznys (JIRA) wrote:
UISelectOne validation fails with custom converter
--
I found it easier to manually import s:submitOnEvent into my
application. (I'm not using a recent-enough sandbox snapshot to
include it). Then you don't have to worry about the javascript
issues.
On 2/28/07, PeshoChuka [EMAIL PROTECTED] wrote:
Ok maybe example is not very good. Yes i am
On 2/28/07, Grant Smith (JIRA) dev@myfaces.apache.org wrote:
Apache MyFaces Fellowship --- I Like this one
I think we should save this one for the future merged
Tomahawk/Trinidad/Tobago project :-)
Paul,
Your logic sounds reasonable to me, but I've never used groupBy.
On 2/28/07, Paul Palaszewski (JIRA) dev@myfaces.apache.org wrote:
[
https://issues.apache.org/jira/browse/TOMAHAWK-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Palaszewski updated
in
the extended dataTable class anywhere. Therefore, my feeling is to just
leave it and fix the other two. Thoughts?
Regards,
Jeff Bischoff
Kenneth L Kurz Associates, Inc.
Jeff Bischoff wrote:
If there's no objections, I'll open a JIRA and submit a patch. :)
Mike Kienenberger wrote:
This change
Werner,
Why not add this an example app to the fusion project?
On 2/27/07, Werner Punz [EMAIL PROTECTED] wrote:
Arash Rajaeeyan schrieb:
how can I see the result of this work?
The demos are not quite there yet (mario is working on them)
but you can contact me this evening so that I can drop
On 2/27/07, Craig McClanahan [EMAIL PROTECTED] wrote:
Just as a procedural note, the only votes that PMC members have
binding votes on is releases. For technical issues (like this one),
all committer votes are not only binding, but a -1 (supported by
adequate reasoning) is a blocker (whereas a
Ah, Ok.
I thought you were simply playing around with the fusion framework,
not trying to use it for real work :-)
On 2/27/07, Werner Punz [EMAIL PROTECTED] wrote:
Mike Kienenberger schrieb:
Werner,
Why not add this an example app to the fusion project?
Problem is i do not know the code
There's no way that Fusion as a web development framework is going
to pass legal. It doesn't matter if you call it Fusion, MyFaces
Fusion, or Apache Myfaces Fusion. Even if it could (and it can't),
why would you want to develop product that would be confused with any
of the other fusion web
[
https://issues.apache.org/jira/browse/TOMAHAWK-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476362
]
Mike Kienenberger commented on TOMAHAWK-548:
One possiblity -- an actionlistener component
It's up to you, but I'd think using a wiki page would be far easier to manage.
You can propose names, and then group them as they're added:
- current contenders
- names eliminated because
On 2/27/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hey,
let's collect these names in a jira
Is maven-cayenne-build-plugin supposed to be 1.4 compatible?
If so, there's one error that prevents this:
maven-cayenne-build-plugin/src/main/java/org.apache.cayenne.maven.plugin.confluence/DocPageRenderer.java:line
219 has
matcher.appendReplacement(replacementBuffer,
Works for me.
On 2/26/07, Dennis Byrne [EMAIL PROTECTED] wrote:
Since JSF is part of the JEE 5 spec users don't need to include the
JSF jars or their dependencies in their webapps when deploying into
Geronimo 2.0. This makes developing a webapp much easier but makes
developing JSF a
+1
On 2/26/07, Dennis Byrne [EMAIL PROTECTED] wrote:
Alright. Here's my +1 binding. Let's put the nail in this coffin.
Dennis Byrne
On 2/26/07, Paul McMahan [EMAIL PROTECTED] wrote:
Excellent observation, Dennis. In Geronimo and a few other app
servers I am familiar with the user is
Check it in as you go along, and that should provide a record.
On 2/23/07, Martin Marinschek [EMAIL PROTECTED] wrote:
Wow. I wonder how anyone will ever find out if they typed it or if
they just copied ;)
regards,
Martin
On 2/23/07, Paul McMahan [EMAIL PROTECTED] wrote:
The Geronimo project
I don't think Tomahawk has proved yet that it is independent from core
versioning. Take the MyFaces Core 1.1.4 incompatiblities between
Tomahawk 1.1.5 as an example.
I think we should take a wait and see attitude before we decide
we're going to start with Tomahawk 1.6 numbering.Remember,
://myfaces.apache.org/tomahawk/testing/selenium.html
Mike Kienenberger wrote:
I don't think Tomahawk has proved yet that it is independent from core
versioning. Take the MyFaces Core 1.1.4 incompatiblities between
Tomahawk 1.1.5 as an example.
I think we should take a wait and see attitude
] wrote:
Mike,
As a part of the 1.1.5 release, the next version is set. Based on your
comments, the version should be set to 1.1.6. I have no problem with
this. The release of 1.1.5 should not be delayed while we determine the
next version number.
Paul Spencer
Mike Kienenberger wrote:
I think
[
https://issues.apache.org/jira/browse/MYFACES-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Kienenberger reopened MYFACES-1223:
Assignee: (was: Mathias Broekelmann)
I don't think marking
On 2/23/07, Mike Kienenberger (JIRA) dev@myfaces.apache.org wrote:
[
https://issues.apache.org/jira/browse/MYFACES-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Kienenberger reopened MYFACES-1223:
Assignee
[
https://issues.apache.org/jira/browse/TOBAGO-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475058
]
Mike Kienenberger commented on TOBAGO-287:
--
Guido,
The form will work, provided it is properly escaped
On 2/22/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Some of us reviewed it (offlist) and we came to the conclusion that it
has enough power to live as separate project.
In the future, please remember that such reviews and conclusions
*must* be made on the mailing list.
As to the
You've answered some of the management issues, but you still haven't
addressed what the difference between tomahawk and/or sandbox and
fusion will be.
From my understanding so far, this is still just a collection of
components, and I don't see why it needs to be separate from the
sandbox or
Well, the thread started with this statement, so you'll have to
forgive me if I thought it was true :-)
MyFaces Fusion is just a collection of already existing myfaces sandbox
components.
On 2/22/07, Werner Punz [EMAIL PROTECTED] wrote:
Mike Kienenberger schrieb:
You've answered some
I went back and reread the spring conversation scope and ejb.
There's nothing in here stating that Mario was planning on starting a
subproject or committing any code, so I don't think we're being too
harsh when someone starts a new subproject without any warning, and we
get concerned.
There
On 2/22/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
The parts in the sandbox will deleted once the setup of the new project
has settled down.
Mario,
Other than the conversation tag, what else will be removed from the sandbox?
Also, how is this going to affect the users who are currently
Hey Mario,
Sounds good. I think a simple announcement to the user list
regarding moving the components is appropriate. Sounds like there is
no one who will be affected, except those who will be moving to
fusion anyway (we should come up with a new name right away if a new
name is necessary).
This change looks good to me. It's probably more important that the
value binding be able to default to null than to output an empty
string css style.
On 2/22/07, Jeff Bischoff [EMAIL PROTECTED] wrote:
Greets,
After converting my application from JSP to Facelets, I set out to make
my
[
https://issues.apache.org/jira/browse/MYFACES-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474777
]
Mike Kienenberger commented on MYFACES-1109:
I no longer remember the details of this issue.
However
[
https://issues.apache.org/jira/browse/TOBAGO-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474568
]
Mike Kienenberger commented on TOBAGO-287:
--
You can avoid the escaping issues by using
/
On 2/20/07, Dennis Byrne [EMAIL PROTECTED] wrote:
I'm not sure why 2.0 is there. Perhaps I was thinking the version of the
shared lib. Anyone know which version of the shared lib we had when
encryption was brought in?
Dennis Byrne
On 2/20/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
Manfred
From the code:
org.apache.myfaces.taglib.html.ext.HtmlPanelGridTag
===
public class HtmlPanelGridTag
extends HtmlPanelGridTagBase
{
public String getComponentType()
{
return HtmlPanelGrid.COMPONENT_TYPE;
}
public String getRendererType()
{
with an explanation.
Paul Spencer
[1] http://www.mail-archive.com/dev@myfaces.apache.org/msg16445.html
[2] http://wiki.apache.org/myfaces/SecurityContext
Mike Kienenberger wrote:
Because attributes have to be documented and maintained for every
component. They also don't work for non-Tomahawk components
Possibly overlooked because it's marked as In Progress rather than
Patch Available.
Unfortunately, I don't see the ability to change the workflow setting
currently available to me.
A quick glance at the patch doesn't show any obvious reasons why it
wouldn't be applied.
One thing that would
Because attributes have to be documented and maintained for every
component. They also don't work for non-Tomahawk components.
A securityContext approach is more flexible, maintainable, and
all-encompassing. We had a long discussion on this a long time ago
on the dev list. You could
On 2/6/07, Manfred Geiler [EMAIL PROTECTED] wrote:
I'm almost finished with core 1.1.5 preparations and already have
changed all dependencies to the next SNAPSHOT versions. Although there
should be more discussions regarding this issue, I would like to go on
like I have started. Please do not
Go for it :-) Can't be any worse that the current broken behavior :-)
On 1/24/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
Now that I am again working around in MyFacesResourceLoader I've had a
look at its lastModified stuff.
You know, we create a properties file with a date generated
[
https://issues.apache.org/jira/browse/TOMAHAWK-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467234
]
Mike Kienenberger commented on TOMAHAWK-872:
Yes, http://www.irian.at/myfaces/collapsiblePanel.jsf's
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
[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)
Thomas Spiegl wrote:
Maybe you can take a look at the Trinidad approach. I think Trinidad
solves state-saving more effective than tomahawk or myfaces does.
On 12/20/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
I'm a fan of client-side state saving. It solves a lot of issues
for me.
However
[
http://issues.apache.org/jira/browse/TOMAHAWK-826?page=comments#action_12460541
]
Mike Kienenberger commented on TOMAHAWK-826:
Just a note that this is an open source project -- anyone who contributes is a
project owner
Actually, the one downside of a single form is that it doesn't
accomodate independent validation sets.A validation error on your
mailing list form could very well break your login form.
The immediate flag can handle trivial cases, but not complex ones.
The ADFaces, Trinidad, and MyFaces
I'm a fan of client-side state saving. It solves a lot of issues for me.
However, there's no doubt that it requires more bandwidth due to
saving the entire component tree state in a hidden input field.
I wonder how much of this is really necessary. I'm guessing 90% of
the state saved is
[
http://issues.apache.org/jira/browse/MYFACES-1414?page=comments#action_12457805
]
Mike Kienenberger commented on MYFACES-1414:
Why would the MyFaces Core examples be only in Tomahawk?
There aren't any MyFaces core examples
MYFACES-1411 has I.P. issues.
MYFACES-1506 is an improvement. It can be moved to 1.1.6. Actually,
this is a Tomahawk issue, not a MyFaces one. Should be moved. Not
sure how Messages.properties interacts with Tomahawk, though.
On 12/8/06, Wendy Smoak [EMAIL PROTECTED] wrote:
The release
MYFACES-1372h:messages not shown (- not working) is important,
but it's been broken for 18 months. It's not a regression as far as
I know.
On 12/8/06, Wendy Smoak [EMAIL PROTECTED] wrote:
The release plan links to unresolved issues, and there are still five
open for 1.1.5:
[
http://issues.apache.org/jira/browse/TOMAHAWK-728?page=comments#action_12454726
]
Mike Kienenberger commented on TOMAHAWK-728:
Michael,
Your patches will be more likely to be accepted if you submit these as a
unified diff patch
Please do not add your table entry to the
http://wiki.apache.org/myfaces/Use_Facelets_with_Tomahawk page. It's
already in this file as dataTable which is the standard name for
this component.
I am reverting your change again.
On 10/3/06, Bruno Aranda [EMAIL PROTECTED] wrote:
I am going this days through the open JIRAs for JSR-252 (JSF 1.2).
Does anybody know if the JIRAs we have are most of the effort, only a
small part.. ?
I believe that there are jira issues for most of 1.2. Not everything
got an issue, though,
Are we building an examples package as part of a release? Martin's
comment in http://issues.apache.org/jira/browse/TOMAHAWK-629 makes it
sound like we are, but I can't find them in any of the usual expected
places.
We need to correct the link in this issue if so. Otherwise, this
issue really
] wrote:
Yeah, open an issue, and I'll carry on for now ;)
regards,
Martin
On 9/21/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
Shall I open a Jira issue on this and solve it later, or were you
planning on reworking it now? Quite honestly, I'm fine with fixing
it on Monday (or whenver I
An FYI:
I hit the following build error just now, even though MyFaces had
built fine a little bit ago.
===
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to configure plugin parameters for:
[ http://issues.apache.org/jira/browse/TOMAHAWK-683?page=all ]
Mike Kienenberger resolved TOMAHAWK-683.
Fix Version/s: 1.1.5-SNAPSHOT
Resolution: Fixed
r448673 lost ValueBinding support for message/detailMessage/summaryMessage
to feel bad. I thought we open jira issues for important
changes, like new components or changes to MyFaces core. I did not
knew that we have to open a jira issue for new component attributes. I
will consider this in the future.
-Thomas
On 9/20/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
Thomas
[
http://issues.apache.org/jira/browse/TOMAHAWK-584?page=comments#action_12436780
]
Mike Kienenberger commented on TOMAHAWK-584:
Well, this is going to be a bit more work.
tree2 was done in apt format, and I'll have to convert
be picked up in the next release.
On 9/22/06, Thomas Spiegl [EMAIL PROTECTED] wrote:
Is an additional attribute always a non-trivial change? In the
specific case it was a trivial change from my point of view. How
should we handle this in the future?
On 9/22/06, Mike Kienenberger [EMAIL PROTECTED
Is it just me, or does mvn site take way too long to run?
I can build the jar files faster, which is saying somethinig.
Is there any way to improve the mvn site speed? Trying to work on
documentation is kinda hard when turnaround time is 20 minutes.
701 - 800 of 1572 matches
Mail list logo
