I was working on the feature to add tab index to components tonight
and after getting it to work with the color palette (chooseColor), I
don't think that it is very useful. There are just too many links to
tab through. Perhaps I can just enable it for the upper left link? Or
do you think that we
Ah, forgot to check that. Thank you
On Sat, Mar 15, 2008 at 2:08 AM, simon [EMAIL PROTECTED] wrote:
On Fri, 2008-03-14 at 17:12 -0600, Andrew Robinson wrote:
I can't seem to get http://myfaces.apache.org/team-list.html to
update. I used continuum to re-build the master project
MyFaces community,
please welcome our new MyFaces PMC member Andrew Robinson.
Andrew is working on the Apache MyFaces and Trinidad stuff.
Therefore last week there was a vote to invite him to the MyFaces
Project Management Committee (PMC) and fortunately he did accept
I can't seem to get http://myfaces.apache.org/team-list.html to
update. I used continuum to re-build the master project, then build
the site project, but the site project is not picking up any of the
changes to the master POM file (the developers in this case). I
checked the continuum working
+0 -- don't have the time to review the JSF 1.1 branch right now
On Tue, Mar 11, 2008 at 10:53 AM, Matt Cooper [EMAIL PROTECTED] wrote:
+1
On Mon, Mar 10, 2008 at 12:29 PM, Scott O'Bryan [EMAIL PROTECTED] wrote:
+1
Matthias Wessendorf wrote:
+1
On Mon, Mar 10, 2008 at 8:20
+1
On Mon, Mar 10, 2008 at 3:18 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
+1
On Mon, Mar 10, 2008 at 10:18 PM, Matthias Wessendorf [EMAIL PROTECTED]
wrote:
Hi,
I was running the needed tasks to get the 1.2.7 release of the Apache
MyFaces Trinidad CORE out. The
[
https://issues.apache.org/jira/browse/TRINIDAD-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12575155#action_12575155
]
Andrew Robinson commented on TRINIDAD-985:
--
Demo works fine for me:
http
gladly help in both issues, but as much as my spare time would let
me do that.
Regards,
On Mon, Mar 3, 2008 at 12:32 AM, Andrew Robinson
[EMAIL PROTECTED] wrote:
I have decided to temporarily quit my side project for various issues,
but I still want to contribute to Trinidad, and now can
I am seeing more and more users setting the fix release as a way to
put down when they seem to want to have it fixed by. It was my
understanding that this should only be used to mark what release the
actual fix has been placed in. If so, is there a way that we can put
security around the fix
That sums it up, thx Matthias, you the man.
On Mon, Mar 3, 2008 at 10:05 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi Andrew,
On Mon, Mar 3, 2008 at 5:37 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
I am seeing more and more users setting the fix release as a way to
put down
[
https://issues.apache.org/jira/browse/MYFACES-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12574617#action_12574617
]
Andrew Robinson commented on MYFACES-1831:
--
Note that t:updateActionListener
Leonardo,
My limitRendered is pretty much not going to change (feature
complete), would this be a good candidate to promote as well or should
it be considered for the commons project instead?
http://myfaces.apache.org/sandbox/limitRendered.html
-Andrew
On Mon, Mar 3, 2008 at 1:59 PM, Leonardo
Will DOJO be optional for tomahawk or will promoting these components
force more 3rd party library dependencies to be added to tomahawk
(regarding the Ajax components)?
On Mon, Mar 3, 2008 at 1:59 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
Hi
I'm doing the related tasks of move sandbox
We can reference the component on the tld of tomahawk, but the hypotetical
DOJO commons module jar should be referenced too. How we can do this
optional?
Maven has an optional scope on dependencies. Believe it looks like:
dependency
groupId /
artifactId /
version /
hmmm, bad memory, thanks Cristi
On Mon, Mar 3, 2008 at 2:31 PM, Cristi Toth [EMAIL PROTECTED] wrote:
it's:
optionaltrue/optional
On Mon, Mar 3, 2008 at 10:24 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
We can reference the component on the tld of tomahawk, but the
hypotetical
: MyFaces Trinidad
Issue Type: Improvement
Components: Skinning
Affects Versions: 1.2.6-core
Reporter: Andrew Robinson
Assignee: Andrew Robinson
Trinidad doesn't have a professional looking skin. This makes people reluctant
to adopt this technology.
I
I have decided to temporarily quit my side project for various issues,
but I still want to contribute to Trinidad, and now can spend some
more time on it. When I was doing this project, I was disapointed by
Trinidad's skins and its demo. As a result, I have created 979 and 980
Jira issues.:
Mark did ask me about putting it on jsf-comp, but I thought it would
be better with Trinidad, but maybe jsf-comp would not be so bad.
On Thu, Feb 28, 2008 at 10:50 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi Mark,
On Fri, Feb 29, 2008 at 12:27 AM, Mark Robinson [EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/TRINIDAD-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572611#action_12572611
]
Andrew Robinson commented on TRINIDAD-971:
--
Why would hint=tabs be of any value
[
https://issues.apache.org/jira/browse/TRINIDAD-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572636#action_12572636
]
Andrew Robinson commented on TRINIDAD-971:
--
Updated the title and description
I have noticed that the text files for Trinidad do not have the eol
SVN property set. Many files have been committed using windows EOL.
Would anyone object to setting svn:eol-style to native on the trinidad
non-binary files so that the correct line endings are used on the
developers machines?
AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
yeah, possible,
we fixed that already in the past.
go ahead and apply the property
-M
On Mon, Feb 25, 2008 at 5:11 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
I have noticed that the text files for Trinidad do not have the eol
Reporter: Andrew Robinson
Priority: Trivial
${version} is a deprecated maven property. It should be changed to
${pom.version} or ${project.version}.
Matches (grep style output):
./shared/shared-tomahawk/pom.xml:41:
version${version}/version
./shared
[
https://issues.apache.org/jira/browse/MYFACES-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Robinson deleted MYFACES-1824:
-
pom.xml uses deprecated syntax
--
Key
Reporter: Andrew Robinson
Priority: Trivial
${version} is a deprecated maven property. It should be changed to
${pom.version} or ${project.version}.
Matches (grep style output):
./shared/shared-tomahawk/pom.xml:41:
version${version}/version
./shared
Versions: 1.1.6
Reporter: Andrew Robinson
Priority: Trivial
${version} is a deprecated maven property. It should be changed to
${pom.version} or ${project.version}.
Tomahawk Matches (grep style output):
./shared/shared-tomahawk/pom.xml:41:
version
This makes me wonder whether it is a goal of Trinidad to generally
support quirks mode operation across all components (without requiring
skin tweaking). If so, I can see exposing a switch to make it easy to
switch into quirks mode. If not, I would be concerned that this might
be
[
https://issues.apache.org/jira/browse/TRINIDAD-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Robinson resolved TRINIDAD-955.
--
Resolution: Fixed
Fix Version/s: 1.2.7-core
Added back in the JSF 1.1
Moving this thread out of the bug and into the mailing list to avoid
an endless comment thread on the bug.
Here is the bug for ppl just joining this thread:
https://issues.apache.org/jira/browse/TRINIDAD-922
This is in reply to Andy's comment on the bug.
Andy, you definitely have a good point
[
https://issues.apache.org/jira/browse/MYFACES-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12570296#action_12570296
]
Andrew Robinson commented on MYFACES-1822:
--
BTW, have you tried facelets 1.1.14
[
https://issues.apache.org/jira/browse/TRINIDAD-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12570486#action_12570486
]
Andrew Robinson commented on TRINIDAD-922:
--
How about these:
tr:document
svn move will retain the svn history
On Feb 19, 2008 3:49 PM, Scott O'Bryan [EMAIL PROTECTED] wrote:
Over the next few days I'm going to be moving in my changes to support
multiple bridges. As a fist step, I need to move the current trunk at
[
https://issues.apache.org/jira/browse/TRINIDAD-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12570520#action_12570520
]
Andrew Robinson commented on TRINIDAD-961:
--
Could you try building the latest
http://www.apache.org/foundation/voting.html
The specifics of the process may vary from project to project, but the
'minimum of three +1 votes' rule is universal.
What happens if there are only 2 members on a team :)
+0 for me as I have never run a portlet server
On Fri, Feb 15, 2008 at 6:44
Instead of a long drawn out debate, why don't we create the sanbox under the
trinidad folder like tomahawk so that there is a sandbox under the 1.2 trunk
as well as the 1.0 trunk.
On Feb 13, 2008 2:41 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi Carsten,
On Feb 13, 2008 10:12 AM,
(this last one would be the site)
On Feb 13, 2008 9:39 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
On Feb 13, 2008 5:32 PM, Andrew Robinson [EMAIL PROTECTED]
wrote:
Instead of a long drawn out debate, why don't we create the sanbox under
the
trinidad folder like tomahawk so
[
https://issues.apache.org/jira/browse/TRINIDAD-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12568619#action_12568619
]
Andrew Robinson commented on TRINIDAD-778:
--
I've seen this to as I think
I have no problems with the author tags, but maybe we want to consider
adding svn keywords?
http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html
On Feb 13, 2008 1:06 PM, simon [EMAIL PROTECTED] wrote:
Hi All,
Currently there are a lot of @author tags in MyFaces code,
[
https://issues.apache.org/jira/browse/TRINIDAD-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567096#action_12567096
]
Andrew Robinson commented on TRINIDAD-922:
--
link rel=stylesheet type=text/css
On Feb 7, 2008 7:37 AM, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
Would one mind if I add these two new attributes to the t:column tag?
Yes
RowID already exists on t:table
As for columns, have you tested t:column id=a?
rowId should go to the tr element and colId to the th element.
+1
On Feb 7, 2008 7:48 AM, Simon Lessard [EMAIL PROTECTED] wrote:
That's a good idea.
On Feb 7, 2008 9:32 AM, Cristi Toth [EMAIL PROTECTED] wrote:
Hi Matthias,
I think it would be great help for developers which first encounter
skinning.
On Feb 7, 2008 9:47 AM, Matthias
Can this wait for Jeanne's PPR refactoring?
On Feb 7, 2008 9:37 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
alright;
no complains, so I am starting now.
-M
On Jan 30, 2008 6:00 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi folks,
I am planing to start the release
Hope no one minds me adding this, I think we should all be sick of the
questions for this page by now.
-Andrew
On Feb 7, 2008 9:41 AM, Apache Wiki [EMAIL PROTECTED] wrote:
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Myfaces Wiki for
change notification.
The
There were no objections, we will go forward with the changes and include
deprecated code to support the old methods (with warnings).
I will create a JIRA issue to monitor this request.
-Andrew
On Jan 30, 2008 5:12 PM, Andrew Robinson [EMAIL PROTECTED]
wrote:
Just had some offline feedback
: Improvement
Components: Components
Affects Versions: 1.2.5-core
Reporter: Andrew Robinson
Thread:
http://www.nabble.com/-VOTE--Partial-triggers-and-%22%3A%3A%22-naming-tt15195442.html
Partial triggers will be changed to a version that makes more sense.
:: will be used to leave
I was wondering what the purpose was. It seemed to me like the apache wiki
was going to start turning into a personal blog site :)
On Feb 5, 2008 1:34 PM, simon [EMAIL PROTECTED] wrote:
On Tue, 2008-02-05 at 20:31 +, Apache Wiki wrote:
Dear Wiki user,
You have subscribed to a wiki
f:subview id=A
tr:commandButton id=B /
tr:table id=C partialTriggers=::B E G ::H:I:K ::H:N
tr:column id=D
tr:commandButton id=E /
tr:inputText partialTriggers=::B E G ::C ::H:I:K ::H:N /
/tr:column
tr:column id=F
tr:commandButton id=G /
/tr:column
Okay, feel free to flame.
Possibility of merging annotations w/ code generation:
@Component(
type = ...,
family = ...,
rendererType = ...,
tagClass = ...,
events = {
@ComponentEvent(
type = ...,
phases = { ..., ... }),
...
)
public abstract class MyComponent
My thoughts:
1. Release 1.1.7 with moving some of the non-render components from
sandbox (I think the PPR would be better in a new library personally)
2. (Rest are post 1.1.7) move any components that work with any render
kit, and are graphical into a new project (or make this
Don't forget that components are just one of the items generated. It is not
wise to make any architectural changes w/o considering all of the artifacts
the plug-in generates.
On Jan 30, 2008 12:34 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
To summarize:
The objective is to look if we can
-1 for a dummy abstract parent class. The resultant OO structure is not
clean. I would rather see a cleaner way to merge the template with the
generated code.
On Jan 30, 2008 1:04 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
1) we do an abstract component base class, very clean, however, it
Sorry that this email is long, but it is a sensitive issue, so please read
on.
https://issues.apache.org/jira/browse/TRINIDAD-757
was reported because the behavior of the code did not match the JavaDoc
description.
Thread: http://tinyurl.com/373smc
At that time, it was decided by others that
abstract from the class definition.
On Jan 30, 2008 1:12 PM, Martin Marinschek [EMAIL PROTECTED]
wrote:
Hi Andrew,
On 1/30/08, Andrew Robinson [EMAIL PROTECTED] wrote:
-1 for a dummy abstract parent class. The resultant OO structure is not
clean. I would rather see a cleaner way to merge
FYI, to parse java source, it looks like there are many utils:
http://java-source.net/open-source/parser-generators
On Jan 30, 2008 3:41 PM, Andrew Robinson [EMAIL PROTECTED]
wrote:
My proposal:
To simplify let me use my:foo that should be used to create
MyFooComponent.java. I want
Here is another:
http://ws.apache.org/jaxme/js/jparser.html
I think you get the drift...
On Jan 30, 2008 4:00 PM, Andrew Robinson [EMAIL PROTECTED]
wrote:
FYI, to parse java source, it looks like there are many utils:
http://java-source.net/open-source/parser-generators
On Jan 30, 2008 3
a say):
+1 : yes I want this change
0: I don't care
-0.5: I don't really like it, but I won't stand in the way (and reason)
-0.9: I hate this, but I won't veto it (and reason)
-1: veto and why
-Andrew
On Jan 30, 2008 3:14 PM, Andrew Robinson [EMAIL PROTECTED]
wrote:
Sorry that this email is long
[
https://issues.apache.org/jira/browse/TRINIDAD-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12562945#action_12562945
]
Andrew Robinson commented on TRINIDAD-922:
--
I would go further than
[
https://issues.apache.org/jira/browse/TRINIDAD-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Robinson resolved TRINIDAD-920.
--
Resolution: Fixed
Fix Version/s: 1.2.6-core
1.0.6-core
Affects Versions: 1.2.5-core
Reporter: Andrew Robinson
Priority: Blocker
CSS styles using attribute selectors are sometimes dropped by the skin
compressor
In my code the following selector is not showing up after compression
(disabling compression is a work around)
af
[
https://issues.apache.org/jira/browse/TRINIDAD-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12562627#action_12562627
]
Andrew Robinson commented on TRINIDAD-920:
--
af|decorativeBox::bottom[_afrTest
Components: Components
Affects Versions: 1.2.5-core, 1.0.5-core
Reporter: Andrew Robinson
Assignee: Andrew Robinson
There is current no way to have a renderer that is a super class of other
renderers to know before and after encoding is done. This is because
[
https://issues.apache.org/jira/browse/TRINIDAD-916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Robinson resolved TRINIDAD-916.
--
Resolution: Fixed
Fix Version/s: 1.2.6-core
1.0.6-core
, 2008 11:36 PM, Andrew Robinson [EMAIL PROTECTED]
wrote:
Usually I would completely agree, but in this case it may be valid. The
encodeEnd/Begin methods that don't use the FacesBean are setup in such a way
to use either encodeAll or encodeEnd (with the FacesBean). So I really don't
think
There are static methods on CoreRenderer that I have no idea why they are
static. The two in particular that I noticed:
static public void renderStyleClass
static public void renderStyleClasses
These are methods for renderers, why would they be static?
There are some util style classes that are
In the development of a library based on Trinidad, I need to have some hooks
in the renderer to improve performance. Specifically, I need to setup a
context and strip down a context for a component. Right now,
CoreRenderer.encodeEnd(FacesContext, UIComponent) is final, so I cannot
extend that
are not part
of the API, what you are doing there, might break with an update. Instead,
everyone is forced by this into compliance mode... how strange.
regards,
Martin
On Jan 22, 2008 10:24 PM, Andrew Robinson [EMAIL PROTECTED]
wrote:
In the development of a library based
there, might break with an update. Instead,
everyone is forced by this into compliance mode... how strange.
regards,
Martin
On Jan 22, 2008 10:24 PM, Andrew Robinson [EMAIL PROTECTED]
wrote:
In the development of a library based on Trinidad, I need to have some
hooks in the renderer to improve
My project has been working fine with me on facelets 1.1.14. You really
should upgrade as 1.1.11 has quite a few bad bugs.
On Jan 19, 2008 11:13 AM, jskillings [EMAIL PROTECTED] wrote:
Hi all,
I am trying to run Trinidad 1.2.5 with Facelets 1.1.11. I made the
necessary changes to the
to 1.1.14.Still having issues. I am unable to
use the date picker or ValueChangeListners.
FYI... I am using Myfaces 1.2.0.
Any other helpful suggestions?
Thank you.
John
Andrew Robinson-5 wrote:
My project has been working fine with me on facelets 1.1.14. You really
should upgrade
All good for me at home over my work VPN
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache MyFaces Trinidad 1.2 ... SUCCESS [
[
https://issues.apache.org/jira/browse/TRINIDAD-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12558019#action_12558019
]
Andrew Robinson commented on TRINIDAD-892:
--
What will be interesting is checking
+1
On Jan 10, 2008 11:45 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
+1
On Jan 10, 2008 10:45 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
I was running the needed tasks to get the 1.0.5 release of the Apache
MyFaces Trinidad CORE out. The artifacts are deployed to my
+1
On Jan 10, 2008 10:49 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
+1
On Jan 10, 2008 9:49 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
I was running the needed tasks to get the 1.2.5 release of the Apache
MyFaces Trinidad CORE out. The artifacts are deployed to my
: 1.2.4-core
Reporter: Andrew Robinson
Using command:
(cd trinidad-examples/trinidad-demo/; mvn -PjettyConfig jetty:run)
The demo is unusable.
1) the ppr page fails miserably
(http://localhost:8080/trinidad-demo/faces/demos/pprDemos.jspx):
Caused by: java.lang.NullPointerException
#4 but with the news style from #2 would be my preference
On Jan 8, 2008 11:35 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
they look cool;
I tend to vote +1 on the draft #4;
Once it gets embedded into the maven-site-build process, we'll see
what the final outcome is.
-Matthias
On
Components: Components
Affects Versions: 1.0.5-core, 1.2.5-core
Reporter: Andrew Robinson
Assignee: Andrew Robinson
Priority: Minor
Add support for tabindex to focusable components (initial list, maybe changed
during implementation):
breadCrumbs
chooseColor
[
https://issues.apache.org/jira/browse/TRINIDAD-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Robinson resolved TRINIDAD-886.
--
Resolution: Fixed
Fix Version/s: 1.0.5-core
Committed revision 610275
[
https://issues.apache.org/jira/browse/TRINIDAD-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12557150#action_12557150
]
Andrew Robinson commented on TRINIDAD-886:
--
Committed revision 610278 in the 1.2
Project: MyFaces Trinidad
Issue Type: New Feature
Components: Components
Affects Versions: 1.0.5-core, 1.2.5-core
Reporter: Andrew Robinson
Assignee: Andrew Robinson
Priority: Minor
The disclosed property of showDetail components
[
https://issues.apache.org/jira/browse/TRINIDAD-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12555334#action_12555334
]
Andrew Robinson commented on TRINIDAD-845:
--
Not to be a stick in the mud
[
https://issues.apache.org/jira/browse/TOMAHAWK-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554812
]
Andrew Robinson commented on TOMAHAWK-1173:
---
Why not just use:
t:datalist
h:panelGrouptr
tdh:outputText
+0.5 on maven
I am a bit indifferent, but I think that a package should be version
agnostic, and only be used for area of functionality. The JAR should
be version specific.
Don't you think that it would be invalid to import maven1 and maven2
jars at the same time?
So I would see as the package:
+1 on apt
-1 on xdoc
APT is *much* easier to write.
Why do we have to choose one? As long as the author is writing
documentation, we should be happy right?
-Andrew
On Dec 15, 2007 7:35 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
-1 on APT
+1 on XML
On Dec 15, 2007 3:29 PM, Simon
First use the users@ and not dev@ for all usage questions.
Don't hold me to it, but I plan on creating a trinidad calendar
component, as I want one myself. It will be a while before I start it
though.
-Andrew
On Dec 13, 2007 4:52 AM, Mustafa DEMİR [EMAIL PROTECTED] wrote:
Hello, i am a new
When are we going to remove the extra trinidad in the trunk folder hierarchy?
-Andrew
On Dec 11, 2007 4:57 AM, Apache Wiki [EMAIL PROTECTED] wrote:
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Myfaces Wiki for
change notification.
The following page has been
Vote summary
+1:
Andrew Robinson
Mike Kienenberger
Simon Lessard
Bruno Aranda
Cagatay Civici
Grant Smith
Mario Ivankovits
Scott O'Bryan
Paul Spencer
-0.9:
Volker Weber (not official vote)
Bernd Bohmann (was -1, but then got a I'm fine if we are starting
with 1.2 only response)
Looks like
Fine with me
Thanks Matthias
On Dec 11, 2007 9:26 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
if you can wait some days, during the hackaton, in Vienna, I can update
commons,
to use jsf 1.2 API (on trunk (and I can create a 1.1 branch))
-M
On Dec 11, 2007 5:23 PM, Andrew Robinson
Ah man, why do you want the web site to look nice? Come on it is open source! :)
Next thing you will want to have the WIKI looking halfway decent
Was this a demo or really working with maven site css changes?
-A
On Dec 11, 2007 9:14 AM, Adonis Raduca [EMAIL PROTECTED] wrote:
Hello,
We have
I think we should delete it and replace it with a page on best
practices on working with 2 trunks.
-Andrew
On Dec 10, 2007 4:58 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
IMO this page isn't needed anymore, because we now have two trunks.
The 1.2.x branches are now only created for
+* [TRINIDAD-663] - Idea for a new component to enhance PPR
+* [TRINIDAD-664] - Component to allow a non-trinidad component
compatible with trinidad with no code
These should not be in the list as I had to pull them out by request
On Dec 10, 2007 1:58 AM, [EMAIL PROTECTED] wrote:
I prefer the M
On Dec 8, 2007 8:33 AM, Adonis Raduca [EMAIL PROTECTED] wrote:
Hello
I look on all comments and I seen the majority agree with the MyFaces
capital M version. I know that many of us are familiar with MyFaces
version and I either. I propose the myFaces, small m from the
-Matthias
On Dec 7, 2007 3:43 AM, Andrew Robinson [EMAIL PROTECTED] wrote:
Okay, the 1.2.x is building fine. Any status on the continuum / maven
snapshot deployment status?
-Andrew
On Dec 4, 2007 10:01 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
let's share the work;
I do 2
Okay, the 1.2.x is building fine. Any status on the continuum / maven
snapshot deployment status?
-Andrew
On Dec 4, 2007 10:01 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
let's share the work;
I do 2)
and you 1.b)
:-)
On Dec 4, 2007 5:59 PM, Andrew Robinson [EMAIL PROTECTED] wrote
PROTECTED] wrote:
On Dec 5, 2007 6:18 PM, Andrew Robinson [EMAIL PROTECTED] wrote:
here we go;
my understanding is, that 1.1 is a must
Why? Is it really necessary for us to create new projects on legacy
specifications?
Well a must is a bit too much. I think I
here we go;
my understanding is, that 1.1 is a must
Why? Is it really necessary for us to create new projects on legacy
specifications?
there is no next merge :)
all 1.2 merges are done. Please merge this onto the trunk_1.2.x if did
not already
On Dec 5, 2007 12:13 PM, Simon Lessard [EMAIL PROTECTED] wrote:
oups, yeah, I didn't mean to commit the 1.2 code as well, brain fart on my
side, it should have been added with the next
As the vote states, if -1, please provide a reason why 1.1 has to be
supported. An argument of why not is not enough.
On Dec 5, 2007 2:14 PM, Bernd Bohmann [EMAIL PROTECTED] wrote:
-1
I don't see any reason why a commons fileupload should not support 1.1
Can someone define what commons API
/target/classes/META-INF/faces-config.xml
On Dec 5, 2007 9:06 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Now it fails for me;
not sure if you were expecting that :-)
On Dec 5, 2007 12:10 AM, Andrew Robinson [EMAIL PROTECTED] wrote:
I just checked in the pom.xml that uncovers
There is another option if this gets vetoed...
All myfaces commons trunks - 1.2
1.1 branch that is only maintained by those willing to perform back ports
-Andrew
On Dec 5, 2007 3:43 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
I think that is a good compromise;
by that we also can filter
+1
On Dec 4, 2007 9:40 AM, Grant Smith [EMAIL PROTECTED] wrote:
+1
On Dec 4, 2007 8:23 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
+1
On Dec 4, 2007 5:20 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
I was running the needed tasks to get the 1.2.4 release of
601 - 700 of 924 matches
Mail list logo
