[jira] Commented: (TRINIDAD-65) The JS e.getFacesMessage method does not work when trinidad was compiled with Java 6 (JSLocaleElementsGenerator does not work with Java6)

[ https://issues.apache.org/jira/browse/TRINIDAD-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553913 ] Matthias Weßendorf commented on TRINIDAD-65: nevermind; I noticed that the vmbuild was running w/ JDK6,

we have a close to final version of MyFaces web interface :)

Hello, We have a close to final version of the MyFaces web interface. All elements needed are designed and are included in two design samples. I also added the apache feather in the header. All graphical elements are designed to achieve an intuitive and minimalist interface close to the already

Re: we have a close to final version of MyFaces web interface :)

the design is cool I don't like: http://www.ubuntu.com/ and myfaces has to many hot artifacts so a FF-style start-page would contain too much infos; let's keep the current structure + the a maven-skin that includes your design. -M On Dec 21, 2007 10:50 AM, Adonis Raduca [EMAIL PROTECTED]

Question on ValueExpression, with an empty ExpressionString (Jetty vs Tomcat)

Inside of Trinidad's EditableValueRenderer (org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.EditableValueRenderer) there getReadOnly(...), which is called by all inputXyz Renderers to check if the component should be rendered readOnly or not That method checks if the component is

[jira] Created: (TOBAGO-581) Sheet component with paging on demand

Sheet component with paging on demand - Key: TOBAGO-581 URL: https://issues.apache.org/jira/browse/TOBAGO-581 Project: MyFaces Tobago Issue Type: Improvement Components: Core

[Build-Tools] Wagon plugin

Hey Börnd, the wagon plugin has /** * @parameter expression=${project} * @required * @readonly */ private MavenProject project; but project isn't used in the code. -M -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions:

[Build-Tools] java packages

Hi, should we always start with this package ? org.apache.myfaces.buildtools.maven2 or org.apache.myfaces.buildtools.maven than -plugin.wagon -plugin.jdev -plugin.faces -plugin.javascript that would be similar to the maven-plugins, provided by the maven-folks; not really sure on maven vs

Re: [Build-Tools] java packages

maven2 is ok I think at least it makes sure we have a namespace for incompatible maven3 plugins in the future... ;-) --Manfred On 12/21/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hi, should we always start with this package ? org.apache.myfaces.buildtools.maven2 or

Re: Question on ValueExpression, with an empty ExpressionString (Jetty vs Tomcat)

My personal feeling is that getValueExpression should NOT return null if explictly called with an empty String. However, this is something for the Unified EL (ie. JSP) specification. If this behaviour is unclear from the spec, it should be explicitly defined there. --Manfred On 12/21/07,

Re: Question on ValueExpression, with an empty ExpressionString (Jetty vs Tomcat)

in case of jsf11; value= == null as well, not valueBinding-object -M On Dec 21, 2007 2:53 PM, Manfred Geiler [EMAIL PROTECTED] wrote: My personal feeling is that getValueExpression should NOT return null if explictly called with an empty String. However, this is something for the Unified EL

Re: [Build-Tools] java packages

+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:

Re: [Trinidad] NLS bug re: formatting locale

I'm going to check my fix in today. I can back it out if anyone has any objections, which I don't foresee. thanks! Jeanne Jeanne Waldman wrote: Hi there, Our local NLS expert brought this bug to my attention. I created a JIRA issue https://issues.apache.org/jira/browse/TRINIDAD-879 Here is

[jira] Commented: (TRINIDAD-879) NLS: Translation to always honor view locale not formatting locale

[ https://issues.apache.org/jira/browse/TRINIDAD-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554008 ] Jeanne Waldman commented on TRINIDAD-879: - TRINIDAD-879 NLS: Translation to always honor view locale not

[jira] Resolved: (TRINIDAD-879) NLS: Translation to always honor view locale not formatting locale

[ https://issues.apache.org/jira/browse/TRINIDAD-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeanne Waldman resolved TRINIDAD-879. - Resolution: Fixed NLS: Translation to always honor view locale not formatting locale

Tomahawk 1.2 Roadmap

Hi, Recently I've discussed tomahawk 1.2 with Bruno. For now we thought it's better to make a branch based on 1.2 and do a quick release and after that for 1.2.x, switch the build to autogeneration with faces-plugin. Since the main goal is tomahawk 1.2, autogeneration could wait a little bit.

RESULT (was Re: [Vote] release for Trinidad Plugins 1.2.6)

Hi, thanks for voting. We got 5 +1 Matthias Wessendorf Bernd Bohmann Martin Marinschek Bruno Aranda Grant Smith So the release will start now