[
https://issues.apache.org/jira/browse/TOMAHAWK-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Kitching reopened TOMAHAWK-1143:
--
Reopening. As discussed on the mailing lists, setting ALT text to an empty
string is
Andrew Robinson schrieb:
I can see the point of that argument, but worry that putting heavy 3rd
party JS libraries into Tomahawk will steer people away from using it.
IMO, Dojo based components should either be (1) in a new MyFaces top
project, or in (2) a subproject of Tomahawk (i.e.
Martin Marinschek schrieb:
I can certainly live with dojo components being in an optional,
plug-in subproject of Tomahawk - they should then however use Tomahawk
infrastructure, the generator-environment and work together with its
components.
As I said moving over the generator is basically a
Hello everyone, we have been using commons-logging the past years.
I am not sure if it is a good idea,
first of all java has a decent logging api, which would allow us to
eliminate the logging dependency.
Secondly,I have not looked into the code yet, but there are a load
of references that
simon schrieb:
Hi,
Should the new commons modules use the traditional MyFaces code style,
the Sun code style?
Right now, it is a mix with some files in one style, and some files in
another (probably about 65% Sun style).
Regards,
Simon
+1 for the myfaces codestyle...
Guess i have to clarify things here
we have a huge codebase, following the myfaces
codestyle, it simply does not make sense to use the sun codestyle,
in one project if all others follow the myfaces guidelines.
Either codestyle can be enforced via code formatting settings.
Werner
Hazem Saleh
+1 for using the same codestyle for all myfaces projects.
regards,
gerhard
2008/7/14 Werner Punz [EMAIL PROTECTED]:
Guess i have to clarify things here
we have a huge codebase, following the myfaces
codestyle, it simply does not make sense to use the sun codestyle,
in one project if all
Hi,
+1 for the code style used in myfaces-tobago ;-)
Can someone describe the differences between sun and myfaces code styles?
Regards,
Volker
2008/7/12 simon [EMAIL PROTECTED]:
Hi,
Should the new commons modules use the traditional MyFaces code style,
the Sun code style?
Right now,
escape value of a selectItem is never evaluated
---
Key: MYFACES-1897
URL: https://issues.apache.org/jira/browse/MYFACES-1897
Project: MyFaces Core
Issue Type: Bug
Components: JSR-252
Hello Werner,
I would like to replace commons-logging with slf4j:-)
Regards
Bernd
Werner Punz schrieb:
Hello everyone, we have been using commons-logging the past years.
I am not sure if it is a good idea,
first of all java has a decent logging api, which would allow us to
eliminate the
Hello,
+1 for the myfaces-tobago code style.
The the myfaces-tobago code style is primarily the sun code style.
Some addtional requirements are:
tabWith is 2,
need Braces ...
Regards
Bernd
Volker Weber schrieb:
Hi,
+1 for the code style used in myfaces-tobago ;-)
Can someone describe
Werner Punz schrieb:
Hello everyone, we have been using commons-logging the past years.
I am not sure if it is a good idea,
first of all java has a decent logging api, which would allow us to
eliminate the logging dependency.
Using a logging API built into the JDK does feel tempting.
However
[
https://issues.apache.org/jira/browse/MYFACES-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12613327#action_12613327
]
Patrick Schmidt commented on MYFACES-1891:
--
Paul, I tried your patch and it
On Sat, Jul 12, 2008 at 5:24 PM, simon [EMAIL PROTECTED] wrote:
On Fri, 2008-07-11 at 13:46 -0500, Leonardo Uribe wrote:
On Fri, Jul 11, 2008 at 2:56 AM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Leonardo Uribe schrieb:
Hi
I think that
On Sun, Jul 13, 2008 at 12:48 PM, simon [EMAIL PROTECTED] wrote:
Hi,
I've just noticed that quite a few component classes are checked in to
the JSF 1.2 trunk, but carry big generated code, do not modify
warnings.
And they look completely different from the versions in the JSF1.1
branch.
Hi guys,
I hope someone can help me out. I've been working with Myfaces and Trinidad
in several projects, but instead of just using it, I would like to learn how
to add new components, to in this case Trinidad. I have checked out the
snapshot and it builds - so that works fine (I believe).
I
Ok I just saw that the slf4j people provide a thin api layer
which replaces the commons logging if needed.
Then probably replacing commons logging is a non issue.
I just was raising this issue again, due to the problems i read
about log4j especially in combination with was and other big irons
Tree initiallyExpanded=true attribute leaves a dangling currency
--
Key: TRINIDAD-1155
URL: https://issues.apache.org/jira/browse/TRINIDAD-1155
Project: MyFaces Trinidad
Issue
[
https://issues.apache.org/jira/browse/TRINIDAD-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Guddanti updated TRINIDAD-1155:
---
Status: Patch Available (was: Open)
Tree initiallyExpanded=true attribute
Is there anyone else out there willing to check the release candidate?
It's pretty simple, as it is just a pom.
I'm hoping to be able to finish the release for this tomorrow, then get
a release candidate out for orchestra-core12 before I go on holiday for
a week. But of course 3 +1s are needed...
After discussing the matter with some of the lead members within the
Apache Incubator, the members asked that the project first grow a
community to sustain the maintainability of the project.
That's probably the best thing to do at this point, and if you're
able to build a small community there
Hi,
There is an assembly subdirectory in tomahawk that has a pom. But I
cannot see anything that uses it. The pom in the main tomahawk dir
doesn't build it. And it doesn't build anyway.
Does anyone know what it does?
Can it be removed from trunk?
Regards,
Simon
Sure, that's what the section is for.
On 7/14/08, Jihoon Kim [EMAIL PROTECTED] wrote:
So that is the update and I was hoping if I could modify the
Frameworks related to JSF section within the MyFaces Wikipage to
include a link to FlexFaces project in order to increase the exposure
of the
[
https://issues.apache.org/jira/browse/TRINIDAD-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Cooper updated TRINIDAD-1155:
--
Resolution: Fixed
Fix Version/s: 1.2.9-core
1.0.9-core
+1
Mario Ivankovits schrieb:
+1
simon schrieb:
Hi All,
I'd like to release a new parent pom for the Orchestra project. You can
find the artifact here:
http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/orchestra/myfaces-orchestra-maven/1.2/
and the svn tag
[
https://issues.apache.org/jira/browse/TOMAHAWK-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Kitching reopened TOMAHAWK-876:
-
Assignee: (was: Gerald Müllan)
Hi Felix,
The patch you attached for this image
[
https://issues.apache.org/jira/browse/TOMAHAWK-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12613481#action_12613481
]
Felix Röthenbacher commented on TOMAHAWK-876:
-
Hi Simon,
Please take the
27 matches
Mail list logo