we got 6 votes, all +1
-matt cooper
-matthias wessendorf
-bruno aranda
-wolfgang toepfer
-andrew robinson
-grant smith
I sent out the notification a second ago.
thx!
M
On 10/24/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
I was running the needed tasks to get the 1.2.3 release of
Ah, ok. What a pity :) - we'll see.
regards,
Martin
On 10/27/07, Wendy Smoak [EMAIL PROTECTED] wrote:
On 10/26/07, Martin Marinschek [EMAIL PROTECTED] wrote:
Hi Wendy,
is this ok?
That looks fine... what I'm not entirely sure of is whether that
feature has made it into a release yet!
Hi!
MyFaces 1.2.1-SNAPSHOT builds properly on my computer - I am also
using /current12. Wonder what this is about... Mario, you are on the
latest sources as well?
Yep I didn't meant that I have this problem too, just wanted to
point out that checking out current12 will do the trick for
Hmm,
MyFaces 1.2.1-SNAPSHOT builds properly on my computer - I am also
using /current12. Wonder what this is about... Mario, you are on the
latest sources as well?
regards,
Martin
On 10/28/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi Simon!
I've checked out
But if you call it myfaces basics, or myfaces components aren't you then at
least sending the message that this is myfaces impl specific?.
From following the thread here I was under the impression that the
components for this common project would be usable, like the apache commons,
in JSF
On 10/28/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
1. Clear separation of API and IMPL (at least on package level, better
by separate artifacts). Mind that the idea behind these commons
classes is that many other projects use them - and therefore depend on
them. So a clear and
[
https://issues.apache.org/jira/browse/TOMAHAWK-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538440
]
Guy Bashan commented on TOMAHAWK-1135:
--
The above code is a part of a dataTable of course ...
[
https://issues.apache.org/jira/browse/TOMAHAWK-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538439
]
Guy Bashan commented on TOMAHAWK-1135:
--
I used the latest build taken from few days ago.
This is a code
Hi!
1. Clear separation of API and IMPL (at least on package level, better
Shouldn't it be possible to have a stable API even without separating it
out?
Have a look at
http://commons.apache.org/beanutils/apidocs/org/apache/commons/beanutils/BeanUtils.html
for an example how
Is an empty file (0 bytes) equal to no file (ie. null)?
is the same as
Is an empty String (length 0) equal to no String (ie. null)?
Technically the answer is no for both questions.
Well the pragmatical (and only reasonable) answer to the second
question is yes in the JSF spec (comp. required for
Hi!
Sure, an app-dev could write a validation method, but I think 0-byte
is somewhat equal to not submitted.
I don't think so. A 0-byte file is a valid file (might be a flag-file to
trigger something).
If you treat a 0-byte file as fake, what would you do with files with
just one space.
I
Mario Ivankovits [EMAIL PROTECTED] schrieb:
Hi!
MyFaces 1.2.1-SNAPSHOT builds properly on my computer - I am also
using /current12. Wonder what this is about... Mario, you are on the
latest sources as well?
Yep I didn't meant that I have this problem too, just wanted to
Hi!
The result of the vote is:
+1
Mike Kienenberger
Martin Marinschek
Matthias Wessendorf
Volker Weber
Gary VanMatre
Grant Smith
Cagaty Civici
Paul Spencer
Scott O'Bryan
Ernst Fastl
alvaro tovar (even if he don't know why ;-) )
Manfred Geiler
Bernd Bohmann
Ron Smits
I've abstaind from splitting
Mario Ivankovits schrieb:
+1
Hi!
Lets start up a MyFaces Facelets project. A name needs to be found.
The aim of this project will be to contain:
1) the taglibs for tomahawk and tomahawk-sandbox as long as we have the
generator not running again. I'd like to ask Bruno if we can jump-start
Hi,
currently Trinidad's inputFile allows the upload of an empty file (0 bytes).
I think it shouldn't. When an inputFile object is marked as required,
I would expect that a user
does a real upload, and not a fake upload.
Sure, an app-dev could write a validation method, but I think 0-byte
is
Hi!
Technically the answer is no for both questions.
Well the pragmatical (and only reasonable) answer to the second
question is yes in the JSF spec (comp. required for h:inputText).
Therefore it makes sense to say yes to Q1 as well.
I think the difference here is, that if there was a file
Popups are brocken in current 1.0.13 snapshot in IE6
-
Key: TOBAGO-523
URL: https://issues.apache.org/jira/browse/TOBAGO-523
Project: MyFaces Tobago
Issue Type: Bug
Components:
I agree with what Manfred said.
Also doing the following:
D:\thisFileDoesNotExistOnMyComputer.png
is handled as an empty file as well.
-M
On 10/29/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
Technically the answer is no for both questions.
Well the pragmatical (and only reasonable)
Matthias Wessendorf schrieb:
I agree with what Manfred said.
Also doing the following:
D:\thisFileDoesNotExistOnMyComputer.png
is handled as an empty file as well.
Really?? Ok, than what Manfred said is true.
Ciao,
Mario
Ok, I'll go ahead and file a bug, at least to track this *change*
This is true for Tomahawk as well, I'll fix that too.
(u can try: http://example.irian.at/example-simple-20071029/fileupload.jsf)
-M
On 10/29/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Matthias Wessendorf schrieb:
I agree
Tobago has such a validator,
max and contentType
yes, should be moved to commons
On 10/29/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
Sure, an app-dev could write a validation method, but I think 0-byte
is somewhat equal to not submitted.
I don't think so. A 0-byte file is a valid
stopp uploading empty files
---
Key: TRINIDAD-788
URL: https://issues.apache.org/jira/browse/TRINIDAD-788
Project: MyFaces Trinidad
Issue Type: Improvement
Reporter: Matthias Weßendorf
[
https://issues.apache.org/jira/browse/TRINIDAD-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-788.
-
Resolution: Fixed
Fix Version/s: 1.0.4-core
fixed in trunk
stopp
Stopp uploading empty files
---
Key: TRINIDAD-789
URL: https://issues.apache.org/jira/browse/TRINIDAD-789
Project: MyFaces Trinidad
Issue Type: Improvement
Affects Versions: 1.0.3-core
Reporter:
[
https://issues.apache.org/jira/browse/TOMAHAWK-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TOMAHAWK-1137.
--
Resolution: Fixed
Fix Version/s: 1.1.7-SNAPSHOT
Stopp uploading
Mandatory-attribute on tx:selectOneChoice is missing
Key: TOBAGO-524
URL: https://issues.apache.org/jira/browse/TOBAGO-524
Project: MyFaces Tobago
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/TOBAGO-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538491
]
Volker Weber commented on TOBAGO-524:
-
which attribute?
jsp or facelets?
Mandatory-attribute on
Hi,
what do you think about doing a 1.0.4 release soon, and the afterwards
created 1.2.4-branch becomes trunk then.
The 1.0.x development goes into maintenance mode, form that time ?
Like:
-new features go into trunk ( 1.2.5-SNAPSHOT)
-fixes go into trunk ( 1.2.5-SNAPSHOT)
-fixes go into
Hi!
I agree that MyFaces Basics is too MyFaces-Core-esque.Tomahawk
Basics or JSF Basics would be better choices.
Hmmm ... I think the MyFaces JSF Basics is the only option then. As
far as I know the token MyFaces needs to be in there as it is a
project of the MyFaces project.
Personally
Mario Ivankovits wrote:
Hi!
1. Clear separation of API and IMPL (at least on package level, better
Shouldn't it be possible to have a stable API even without separating it
out?
Have a look at
Strong -1 on this
0 byte files are very valid, especially on a unix based platform.
There are many times that a file by its existence implies meaning.
Take for example ~/.config/xserver-xgl/disable, if this file is
present, xgl mode of the linux X server is disabled for that user. The
file should
David,
Yes, attaching your goodies as attachment to a jira issue will be fine.
Thanks in advance,
Manfred
Hi ,
While working in my projects i had developed a good collection of static
utility methods for navigation handling, scope handling, resource
loading handling, message handling and
[
https://issues.apache.org/jira/browse/TRINIDAD-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538526
]
Andrew Robinson commented on TRINIDAD-788:
--
0 byte files are very valid, especially on a unix based
I don't think there's any hard rule that all projects have to be
prefixed with MyFaces.
But then, I also don't have any problem with it being associated with
Tomahawk or MyFaces (in the name).
On 10/29/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
I agree that MyFaces Basics is too
Matze,
What about providing a standard tr:validateNonEmptyFile Vaidator.
This would make everybody happy, right?
lg,
Manfred
On 10/29/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Strong -1 on this
0 byte files are very valid, especially on a unix based platform.
There are many times that a
-1 on the 1.0.4.x naming unless for security patches. IMO committers
should be permitted to put new features in both the trunk and the 1.0
branch and therefore would make sense to mirror the releases (1.2.5
and 1.0.5)
On 10/29/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
what do you
How about a new ASF style name instead of basic, commons or
something else that could be more easily misconstrued?
-A
On 10/29/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
I don't think there's any hard rule that all projects have to be
prefixed with MyFaces.
But then, I also don't have any
Would a tr:validateFileLength min=1 / be more useful? Then min and
max could be used.
-A
On 10/29/07, Manfred Geiler [EMAIL PROTECTED] wrote:
Matze,
What about providing a standard tr:validateNonEmptyFile Vaidator.
This would make everybody happy, right?
lg,
Manfred
On 10/29/07, Andrew
Matthias,
If the committers want to spend their time backporting fixes to 1.0.x,
that's their right.
-- Blake Sullivan
Matthias Wessendorf wrote:
Hi,
what do you think about doing a 1.0.4 release soon, and the afterwards
created 1.2.4-branch becomes trunk then.
The 1.0.x development goes
Makes sense.
On 10/29/07, Manfred Geiler [EMAIL PROTECTED] wrote:
Our current MyFaces site artifact is named myfaces:
[..]
groupIdorg.apache.myfaces/groupId
artifactIdmyfaces/artifactId
version1.0.0-SNAPSHOT/version
packagingpom/packaging
nameMyFaces Site/name
[..]
I would
Our current MyFaces site artifact is named myfaces:
[..]
groupIdorg.apache.myfaces/groupId
artifactIdmyfaces/artifactId
version1.0.0-SNAPSHOT/version
packagingpom/packaging
nameMyFaces Site/name
[..]
I would like to rename this artifact to org.apache.myfaces:myfaces-site.
Reason: I
datepicker selects wrong day
Key: TRINIDAD-790
URL: https://issues.apache.org/jira/browse/TRINIDAD-790
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Affects Versions: 1.0.3-core
Yeah, that was kind of my thought. Bug fixes and certain backported
features would go into 1.0.4 but it would pretty much be up to the
developer. If a feature in 1.2 is needed in 1.0.x, it could certainly
be requested with a JIRA ticket and someone could do the backport on
their own.
-1
Has MyFaces switched their trunk yet. I'd like to see us keep inline with
them. It seems like we had this conversation only a month or two ago.
I'd love to see the MyFaces implementation support the JSF-RI feature of
allowing 1.2 components + Facelets on the J2EE 1.4 (MYFACES-1693). With
No offense taken although I don't think this is as much an Oracle issue
as it is that most of the active developers on this project just happen
to be associated with Oracle. I know I personally don't like all the
overhead in contributing to a project that is not build off of a trunk,
Wrong popup panel width
---
Key: TRINIDAD-791
URL: https://issues.apache.org/jira/browse/TRINIDAD-791
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Affects Versions: 1.0.3-core
Danny Robinson wrote:
-1
Has MyFaces switched their trunk yet. I'd like to see us keep inline
with them.
Although it would be nice to stay in sync, there is no technical reason
for a JSF-implementation-independent component library to keep its main
trunk locked to the same api version as the
Width attribute for column
--
Key: TOBAGO-526
URL: https://issues.apache.org/jira/browse/TOBAGO-526
Project: MyFaces Tobago
Issue Type: Improvement
Components: Core
Affects Versions: 1.0.12
Extend ResourceLocator for exploded tobago-theme.jar (unit-testing)
---
Key: TOBAGO-525
URL: https://issues.apache.org/jira/browse/TOBAGO-525
Project: MyFaces Tobago
Issue
Hello Blake,
Please see some comments inline.
On 10/29/07, Blake Sullivan [EMAIL PROTECTED] wrote:
Danny Robinson wrote:
-1
Has MyFaces switched their trunk yet. I'd like to see us keep inline with
them.
Although it would be nice to stay in sync, there is no technical reason
for a
[
https://issues.apache.org/jira/browse/TOMAHAWK-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538637
]
Navid Mitchell commented on TOMAHAWK-1115:
--
Antonio Petrelli on the Nabble forum asked me to post this
[
https://issues.apache.org/jira/browse/TOMAHAWK-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538637
]
navidmitchell edited comment on TOMAHAWK-1115 at 10/29/07 4:59 PM:
Antonio
Yes, correct.
my main point was making the 1.2.x become the trunk;
supporting the 1.0.x series is valid, and I'll do that as well.
-M
On 10/29/07, Blake Sullivan [EMAIL PROTECTED] wrote:
Matthias,
If the committers want to spend their time backporting fixes to 1.0.x,
that's their right.
--
Hi!
How about a new ASF style name instead of basic, commons or
something else that could be more easily misconstrued?
Could you give an ASF style name for example?
---
Mario
valid points.
-M
On 10/29/07, Andrew Robinson [EMAIL PROTECTED] wrote:
-1 on the 1.0.4.x naming unless for security patches. IMO committers
should be permitted to put new features in both the trunk and the 1.0
branch and therefore would make sense to mirror the releases (1.2.5
and 1.0.5)
So, why not doing a
tr:validateFileLength /
with the following attributes:
-minLength
-maxLength
-contentType
Greetings,
Matthias
On 10/29/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Would a tr:validateFileLength min=1 / be more useful? Then min and
max could be used.
-A
On 10/29/07,
tr:validateUploadedFile / might be the better name.
-M
On 10/30/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
So, why not doing a
tr:validateFileLength /
with the following attributes:
-minLength
-maxLength
-contentType
Greetings,
Matthias
On 10/29/07, Andrew Robinson [EMAIL
Hi Danny,
On 10/29/07, Danny Robinson [EMAIL PROTECTED] wrote:
-1
Has MyFaces switched their trunk yet. I'd like to see us keep inline with
them. It seems like we had this conversation only a month or two ago.
yes, being sync w/ MyFaces would be great.
Did the two trunk thing came up here
Hi!
Before this is considered passed, could there be a re-definition of
the scope of this project as there has been some discussion?
For me the scope is to provide components which primarily works with
facelets ONLY. There might be a JSP tag provided, but this is not a must
have for the
59 matches
Mail list logo
