[Trinidad] Possible to skip certain stops in a train model?
Hi,
I am looking at implementing my own custom Train Model using my custom
ProcessMenuModel
public ProcessMenuModel getTrainModel() {
}
However, I have a specific use case wherein I should be able to skip
certain stops in my train.
Say for example, I have seven stops then on Step 2, I choose something from
that page.
Is it possible to disable Steps 3 and 4 programatically so that user wont
be able to navigate to that page?
Step 5, 6 and 7 should still be available.
Thanks
Re: MyFaces 2.0.10 and 2.1.4 release date?
Hi I for one need another week for testing, I did a load of changes in the javascripts which are tested but I need some additional days to finalize everything. Werner Am 11/1/11 11:03 AM, schrieb Udo Schnurpfeil: Hi, I think it's time for the next release. There are a lot of bug fixed now, and the last release is some weeks ago. What do you think? Regards Udo
Re: [VOTE] Internal Incubator
+1 Am 11/1/11 9:16 AM, schrieb Bernd Bohmann: +1 for the idea but -1 for the name. I expect trouble with the Apache Incubator. What is the difference between Apache Incubator and Apache MyFaces Incubator? If there is a difference we should consider a different name. I would prefer labs, sandbox or what ever. Regards Bernd Bohmann On Tue, Nov 1, 2011 at 1:36 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: Hi, in order to check if there is a community for a new sub-project (esp. GSoC projects for MyFaces), we discussed [1] the introduction of an internal incubator. We would release such projects early and e.g. after a quarter we decide if we keep and promote a project (as a sub-project or a module of an existing sub-project) or if we drop it. Please vote: [+1] I like the idea [0] I'm not convinced but I'm ok with it [-1] I don't agree Regards, Gerhard [1] http://markmail.org/message/d7oogfabvliwn7fg
Re: [VOTE] Internal Incubator
FWIW: -1 why introducing yet another level of incubation process ? I find it (very) problematic trying to be in some sort of competition w/ the Apache Incubator... (even if the discussed targets here are JSF specific) Why not simply moving future (MyFaces) GSoC directly to the Apache Labs project ([1])?! For there, just start coding and releasing (alphas etc). The new release process is straightforward and not heavyweight - so (alpha) releases are cheap. -M [1] http://labs.apache.org/ On Tue, Nov 1, 2011 at 11:28 AM, Bernd Bohmann bernd.bohm...@atanion.com wrote: Ok, if there is no real difference between Apache Incubator and Apache MyFaces Incubator, I have to change my vote to -1 especially a have a problem with: All code donations from external organisations and existing external projects wishing to join MyFaces enter through the MyFaces-Incubator. This is the Apache Incubator role. Regards Bernd On Tue, Nov 1, 2011 at 10:25 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi bart, as mentioned [1] by mark it's also about ip clearance [2]. regards, gerhard [1] http://mail-archives.apache.org/mod_mbox/myfaces-dev/201110.mbox/%3c1319274310.93350.yahoomail...@web27807.mail.ukl.yahoo.com%3E [2] http://incubator.apache.org/ip-clearance/index.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/1 Bart Kummel b...@kummelweb.nl +1 for the idea! I agree with Bernd about the name. For me, incubator is also associated with rules and legal stuff. We should encourage people to contribute, instead of scaring them away. Sandbox or labs sounds encouraging and accessible. But perhaps we should discuss/vote the name in another thread and first focus on the idea... Best regards, Bart Kummel On Tue, Nov 1, 2011 at 01:36, Gerhard Petracek gerhard.petra...@gmail.com wrote: Hi, in order to check if there is a community for a new sub-project (esp. GSoC projects for MyFaces), we discussed [1] the introduction of an internal incubator. We would release such projects early and e.g. after a quarter we decide if we keep and promote a project (as a sub-project or a module of an existing sub-project) or if we drop it. Please vote: [+1] I like the idea [0] I'm not convinced but I'm ok with it [-1] I don't agree Regards, Gerhard [1] http://markmail.org/message/d7oogfabvliwn7fg -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [html5] alpha release for myfaces html5
I don't get why not just having a simple alpha release ?
Does not hurt... Or... move the entire thing to Apache Labs... for
future experiments ?!
-M
On Tue, Nov 1, 2011 at 12:03 AM, Ali Ok al...@aliok.com.tr wrote:
Hi,
So do you think myfaces/incubator/html5 is a good place?
Greetings,
Ali
On Sat, Oct 22, 2011 at 1:37 PM, Ali Ok al...@aliok.com.tr wrote:
Hi,
In my opinion as long this lib is html5 only it should not be part of
the tomahawk project
I agree, no relation with Tomahawk.
a different idea would be a small myfaces-incubator for new project-ideas
(esp. for gsoc projects).
Makes more sense to me than Tomahawk.
I think (almost) everyone is in favor of moving the project to somewhere
else, I am also ok with it.
Important thing for the project is having the ability for releases and the
jars are deployed to maven repo.
Cheers,
Ali
On Sat, Oct 22, 2011 at 11:05 AM, Mark Struberg strub...@yahoo.de wrote:
including our very own little 'attic' :)
Actually the big difference between the incubator and a mf subproject
would be the IP clearance. We really need to do this upfront before
importing.
But actually I like this much more than having projects developed outside
and only later brought into our SVN - because this causes lots of paperwork
(gas grants and a IP clearance review is mandatory).
Thus a +1
LieGrue,
strub
From: Gerhard Petracek gerhard.petra...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Sent: Saturday, October 22, 2011 10:58 AM
Subject: Re: [html5] alpha release for myfaces html5
a different idea would be a small myfaces-incubator for new
project-ideas (esp. for gsoc projects).
we can release parts easily and drop them if we see that something
doesn't work for our community. if an idea works for the community, we can
discuss the correct place for it.
we might see new gsoc projects (related to myfaces) every year. imo it's
the wrong approach to just add them as new sub-project and we don't have
the
resources/community to maintain them.
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/10/22 Bernd Bohmann bernd.bohm...@atanion.com
Ha, I don't think we should wait for the jsf-eg.
Hey guys they are asking for a alpha release.
In my opinion as long this lib is html5 only it should not be part of
the tomahawk project.
I don't see any problems in releasing an alpha release. But before a
beta we should decide own extension or tomahawk.
Regards
Bernd
On Sat, Oct 22, 2011 at 9:31 AM, Gerhard Petracek
gerhard.petra...@gmail.com wrote:
it's planned that jsf2.2 will get some sort of html5 support.
imo we should work together with the jsf-eg to ensure that we won't
promote
incompatible components.
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/10/22 Mark Struberg strub...@yahoo.de
+1 for moving it to tomahawk.
One big open question for me is our html5 strategy at all.
Will the html5 components provide legacy html support themselfs?
Thus a calendar component will use jQuery (or whatever) calendar
when a
non-html5 browser is detected,
or is this in the responsibility of the developer?
if (html5){
} else{
//fallback
}
?
Afaik our current html5 components 'only' support pure html5
rendering,
isn't?
LieGrue,
strub
From: Gerhard Petracek gerhard.petra...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Sent: Friday, October 21, 2011 10:22 PM
Subject: Re: [html5] alpha release for myfaces html5
@grant: +1
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/10/21 Grant Smith work.gr...@gmail.com
I must agree with Gerhard. The whole point of the sandbox is for
this
very purpose. However, perhaps we should look at the sandbox more
often and
vote on components that are ready to graduate.
On Fri, Oct 21, 2011 at 1:12 PM, Gerhard Petracek
gerhard.petra...@gmail.com wrote:
hi leo,
imo such an argument doesn't justify an own sub-project. i
don't say
-1. my point is that we should discuss it (esp. because the
situation
changed).
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/10/21 Leonardo Uribe lu4...@gmail.com
Hi
The problem with move to tomahawk sandbox is those artifact
Re: [VOTE] Internal Incubator
On Wed, Nov 2, 2011 at 6:32 AM, Matthias Wessendorf mat...@apache.org wrote: FWIW: -1 why introducing yet another level of incubation process ? I find it (very) problematic trying to be in some sort of competition w/ the Apache Incubator... (even if the discussed targets here are JSF specific) As I have attempted to point out elsewhere via email links (which presumably went unfollowed), not only is this problematic; per Incubator PMC consensus it is downright unacceptable. You simply can't have a mini-incubator so complete that it makes sense even to use the *name* incubator. PLEASE read [1] for background, or skip directly to [2] (search for Some possible solutions) to know what IS acceptable. There is no need for MyFaces to rehash my experiences on Commons' behalf two-plus years ago. [1] http://markmail.org/message/n3t7lksceuplh45r [2] http://markmail.org/message/r6ffmmyh6pxnn6nd Matt Why not simply moving future (MyFaces) GSoC directly to the Apache Labs project ([1])?! For there, just start coding and releasing (alphas etc). The new release process is straightforward and not heavyweight - so (alpha) releases are cheap. -M [1] http://labs.apache.org/ On Tue, Nov 1, 2011 at 11:28 AM, Bernd Bohmann bernd.bohm...@atanion.com wrote: Ok, if there is no real difference between Apache Incubator and Apache MyFaces Incubator, I have to change my vote to -1 especially a have a problem with: All code donations from external organisations and existing external projects wishing to join MyFaces enter through the MyFaces-Incubator. This is the Apache Incubator role. Regards Bernd On Tue, Nov 1, 2011 at 10:25 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi bart, as mentioned [1] by mark it's also about ip clearance [2]. regards, gerhard [1] http://mail-archives.apache.org/mod_mbox/myfaces-dev/201110.mbox/%3c1319274310.93350.yahoomail...@web27807.mail.ukl.yahoo.com%3E [2] http://incubator.apache.org/ip-clearance/index.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/1 Bart Kummel b...@kummelweb.nl +1 for the idea! I agree with Bernd about the name. For me, incubator is also associated with rules and legal stuff. We should encourage people to contribute, instead of scaring them away. Sandbox or labs sounds encouraging and accessible. But perhaps we should discuss/vote the name in another thread and first focus on the idea... Best regards, Bart Kummel On Tue, Nov 1, 2011 at 01:36, Gerhard Petracek gerhard.petra...@gmail.com wrote: Hi, in order to check if there is a community for a new sub-project (esp. GSoC projects for MyFaces), we discussed [1] the introduction of an internal incubator. We would release such projects early and e.g. after a quarter we decide if we keep and promote a project (as a sub-project or a module of an existing sub-project) or if we drop it. Please vote: [+1] I like the idea [0] I'm not convinced but I'm ok with it [-1] I don't agree Regards, Gerhard [1] http://markmail.org/message/d7oogfabvliwn7fg -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] Internal Incubator
thx matt for the links regards, gerhard 2011/11/2 Matt Benson gudnabr...@gmail.com: On Wed, Nov 2, 2011 at 6:32 AM, Matthias Wessendorf mat...@apache.org wrote: FWIW: -1 why introducing yet another level of incubation process ? I find it (very) problematic trying to be in some sort of competition w/ the Apache Incubator... (even if the discussed targets here are JSF specific) As I have attempted to point out elsewhere via email links (which presumably went unfollowed), not only is this problematic; per Incubator PMC consensus it is downright unacceptable. You simply can't have a mini-incubator so complete that it makes sense even to use the *name* incubator. PLEASE read [1] for background, or skip directly to [2] (search for Some possible solutions) to know what IS acceptable. There is no need for MyFaces to rehash my experiences on Commons' behalf two-plus years ago. [1] http://markmail.org/message/n3t7lksceuplh45r [2] http://markmail.org/message/r6ffmmyh6pxnn6nd Matt Why not simply moving future (MyFaces) GSoC directly to the Apache Labs project ([1])?! For there, just start coding and releasing (alphas etc). The new release process is straightforward and not heavyweight - so (alpha) releases are cheap. -M [1] http://labs.apache.org/ On Tue, Nov 1, 2011 at 11:28 AM, Bernd Bohmann bernd.bohm...@atanion.com wrote: Ok, if there is no real difference between Apache Incubator and Apache MyFaces Incubator, I have to change my vote to -1 especially a have a problem with: All code donations from external organisations and existing external projects wishing to join MyFaces enter through the MyFaces-Incubator. This is the Apache Incubator role. Regards Bernd On Tue, Nov 1, 2011 at 10:25 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi bart, as mentioned [1] by mark it's also about ip clearance [2]. regards, gerhard [1] http://mail-archives.apache.org/mod_mbox/myfaces-dev/201110.mbox/%3c1319274310.93350.yahoomail...@web27807.mail.ukl.yahoo.com%3E [2] http://incubator.apache.org/ip-clearance/index.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/1 Bart Kummel b...@kummelweb.nl +1 for the idea! I agree with Bernd about the name. For me, incubator is also associated with rules and legal stuff. We should encourage people to contribute, instead of scaring them away. Sandbox or labs sounds encouraging and accessible. But perhaps we should discuss/vote the name in another thread and first focus on the idea... Best regards, Bart Kummel On Tue, Nov 1, 2011 at 01:36, Gerhard Petracek gerhard.petra...@gmail.com wrote: Hi, in order to check if there is a community for a new sub-project (esp. GSoC projects for MyFaces), we discussed [1] the introduction of an internal incubator. We would release such projects early and e.g. after a quarter we decide if we keep and promote a project (as a sub-project or a module of an existing sub-project) or if we drop it. Please vote: [+1] I like the idea [0] I'm not convinced but I'm ok with it [-1] I don't agree Regards, Gerhard [1] http://markmail.org/message/d7oogfabvliwn7fg -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [html5] alpha release for myfaces html5
see [1] - esp.:
Apache Labs are the place where ASF committers can work on innovative,
blue-sky and off-the-wall ideas, without having to worry about fitting in an
existing project bylaw or building a community around it...
we already know that it works and it's just about a community check
- imo labs doesn't fit and the alternative would be the incubator
itself.
regards,
gerhard
[1] http://labs.apache.org/bylaws.html
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/11/2 Matthias Wessendorf mat...@apache.org:
I don't get why not just having a simple alpha release ?
Does not hurt... Or... move the entire thing to Apache Labs... for
future experiments ?!
-M
On Tue, Nov 1, 2011 at 12:03 AM, Ali Ok al...@aliok.com.tr wrote:
Hi,
So do you think myfaces/incubator/html5 is a good place?
Greetings,
Ali
On Sat, Oct 22, 2011 at 1:37 PM, Ali Ok al...@aliok.com.tr wrote:
Hi,
In my opinion as long this lib is html5 only it should not be part of
the tomahawk project
I agree, no relation with Tomahawk.
a different idea would be a small myfaces-incubator for new project-ideas
(esp. for gsoc projects).
Makes more sense to me than Tomahawk.
I think (almost) everyone is in favor of moving the project to somewhere
else, I am also ok with it.
Important thing for the project is having the ability for releases and the
jars are deployed to maven repo.
Cheers,
Ali
On Sat, Oct 22, 2011 at 11:05 AM, Mark Struberg strub...@yahoo.de wrote:
including our very own little 'attic' :)
Actually the big difference between the incubator and a mf subproject
would be the IP clearance. We really need to do this upfront before
importing.
But actually I like this much more than having projects developed outside
and only later brought into our SVN - because this causes lots of paperwork
(gas grants and a IP clearance review is mandatory).
Thus a +1
LieGrue,
strub
From: Gerhard Petracek gerhard.petra...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Sent: Saturday, October 22, 2011 10:58 AM
Subject: Re: [html5] alpha release for myfaces html5
a different idea would be a small myfaces-incubator for new
project-ideas (esp. for gsoc projects).
we can release parts easily and drop them if we see that something
doesn't work for our community. if an idea works for the community, we
can
discuss the correct place for it.
we might see new gsoc projects (related to myfaces) every year. imo it's
the wrong approach to just add them as new sub-project and we don't have
the
resources/community to maintain them.
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/10/22 Bernd Bohmann bernd.bohm...@atanion.com
Ha, I don't think we should wait for the jsf-eg.
Hey guys they are asking for a alpha release.
In my opinion as long this lib is html5 only it should not be part of
the tomahawk project.
I don't see any problems in releasing an alpha release. But before a
beta we should decide own extension or tomahawk.
Regards
Bernd
On Sat, Oct 22, 2011 at 9:31 AM, Gerhard Petracek
gerhard.petra...@gmail.com wrote:
it's planned that jsf2.2 will get some sort of html5 support.
imo we should work together with the jsf-eg to ensure that we won't
promote
incompatible components.
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/10/22 Mark Struberg strub...@yahoo.de
+1 for moving it to tomahawk.
One big open question for me is our html5 strategy at all.
Will the html5 components provide legacy html support themselfs?
Thus a calendar component will use jQuery (or whatever) calendar
when a
non-html5 browser is detected,
or is this in the responsibility of the developer?
if (html5){
} else{
//fallback
}
?
Afaik our current html5 components 'only' support pure html5
rendering,
isn't?
LieGrue,
strub
From: Gerhard Petracek gerhard.petra...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Sent: Friday, October 21, 2011 10:22 PM
Subject: Re: [html5] alpha release for myfaces html5
@grant: +1
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/10/21 Grant Smith work.gr...@gmail.com
I must agree with Gerhard. The whole point of the sandbox is for
this
very purpose. However, perhaps we should look at the sandbox more
often and
vote on
[jira] [Created] (EXTCDI-237) create jee 5 support modules
create jee 5 support modules Key: EXTCDI-237 URL: https://issues.apache.org/jira/browse/EXTCDI-237 Project: MyFaces CODI Issue Type: Task Reporter: Gerhard Petracek Priority: Minor currently we have two add-ons ([1] and [2]) which are needed for some jee 5 application-servers to get jsf+cdi up and running correctly. those add-ons aren't needed for jee 6 application-servers. however, we could include them in codi to improve the jee 5 support. [1] http://code.google.com/a/apache-extras.org/p/myfaces-codi-addons/source/browse/#hg%2Fcontrolled_bootstrapping_owb [2] http://code.google.com/a/apache-extras.org/p/myfaces-codi-addons/source/browse/#hg%2Fcontrolled_bootstrapping_weld -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Internal Incubator
i think we should stop the vote and re-visit the original thread at [1]. there we could discuss the name and we could re-visit the option to use the asf incubator directly (for gsoc projects). regards, gerhard [1] http://markmail.org/message/d7oogfabvliwn7fg 2011/11/2 Gerhard Petracek gerhard.petra...@gmail.com: thx matt for the links regards, gerhard 2011/11/2 Matt Benson gudnabr...@gmail.com: On Wed, Nov 2, 2011 at 6:32 AM, Matthias Wessendorf mat...@apache.org wrote: FWIW: -1 why introducing yet another level of incubation process ? I find it (very) problematic trying to be in some sort of competition w/ the Apache Incubator... (even if the discussed targets here are JSF specific) As I have attempted to point out elsewhere via email links (which presumably went unfollowed), not only is this problematic; per Incubator PMC consensus it is downright unacceptable. You simply can't have a mini-incubator so complete that it makes sense even to use the *name* incubator. PLEASE read [1] for background, or skip directly to [2] (search for Some possible solutions) to know what IS acceptable. There is no need for MyFaces to rehash my experiences on Commons' behalf two-plus years ago. [1] http://markmail.org/message/n3t7lksceuplh45r [2] http://markmail.org/message/r6ffmmyh6pxnn6nd Matt Why not simply moving future (MyFaces) GSoC directly to the Apache Labs project ([1])?! For there, just start coding and releasing (alphas etc). The new release process is straightforward and not heavyweight - so (alpha) releases are cheap. -M [1] http://labs.apache.org/ On Tue, Nov 1, 2011 at 11:28 AM, Bernd Bohmann bernd.bohm...@atanion.com wrote: Ok, if there is no real difference between Apache Incubator and Apache MyFaces Incubator, I have to change my vote to -1 especially a have a problem with: All code donations from external organisations and existing external projects wishing to join MyFaces enter through the MyFaces-Incubator. This is the Apache Incubator role. Regards Bernd On Tue, Nov 1, 2011 at 10:25 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi bart, as mentioned [1] by mark it's also about ip clearance [2]. regards, gerhard [1] http://mail-archives.apache.org/mod_mbox/myfaces-dev/201110.mbox/%3c1319274310.93350.yahoomail...@web27807.mail.ukl.yahoo.com%3E [2] http://incubator.apache.org/ip-clearance/index.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/1 Bart Kummel b...@kummelweb.nl +1 for the idea! I agree with Bernd about the name. For me, incubator is also associated with rules and legal stuff. We should encourage people to contribute, instead of scaring them away. Sandbox or labs sounds encouraging and accessible. But perhaps we should discuss/vote the name in another thread and first focus on the idea... Best regards, Bart Kummel On Tue, Nov 1, 2011 at 01:36, Gerhard Petracek gerhard.petra...@gmail.com wrote: Hi, in order to check if there is a community for a new sub-project (esp. GSoC projects for MyFaces), we discussed [1] the introduction of an internal incubator. We would release such projects early and e.g. after a quarter we decide if we keep and promote a project (as a sub-project or a module of an existing sub-project) or if we drop it. Please vote: [+1] I like the idea [0] I'm not convinced but I'm ok with it [-1] I don't agree Regards, Gerhard [1] http://markmail.org/message/d7oogfabvliwn7fg -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [VOTE] Internal Incubator
Why incubator for Gsoc projects? IMO that's wrong. Move stuff like that to Labs: build code and get releases out (release often, release early) Once there is interest - by some community decide where to go: There some options, like: a) Going to the incubator - start to build a community around it ( the new experimental code base) b) if it makes sense, integrate it with existing MyFaces code (e.g. partial state savings improvements etc) (or make it Apache MyFaces subproject) -M On Wed, Nov 2, 2011 at 2:00 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: i think we should stop the vote and re-visit the original thread at [1]. there we could discuss the name and we could re-visit the option to use the asf incubator directly (for gsoc projects). regards, gerhard [1] http://markmail.org/message/d7oogfabvliwn7fg 2011/11/2 Gerhard Petracek gerhard.petra...@gmail.com: thx matt for the links regards, gerhard 2011/11/2 Matt Benson gudnabr...@gmail.com: On Wed, Nov 2, 2011 at 6:32 AM, Matthias Wessendorf mat...@apache.org wrote: FWIW: -1 why introducing yet another level of incubation process ? I find it (very) problematic trying to be in some sort of competition w/ the Apache Incubator... (even if the discussed targets here are JSF specific) As I have attempted to point out elsewhere via email links (which presumably went unfollowed), not only is this problematic; per Incubator PMC consensus it is downright unacceptable. You simply can't have a mini-incubator so complete that it makes sense even to use the *name* incubator. PLEASE read [1] for background, or skip directly to [2] (search for Some possible solutions) to know what IS acceptable. There is no need for MyFaces to rehash my experiences on Commons' behalf two-plus years ago. [1] http://markmail.org/message/n3t7lksceuplh45r [2] http://markmail.org/message/r6ffmmyh6pxnn6nd Matt Why not simply moving future (MyFaces) GSoC directly to the Apache Labs project ([1])?! For there, just start coding and releasing (alphas etc). The new release process is straightforward and not heavyweight - so (alpha) releases are cheap. -M [1] http://labs.apache.org/ On Tue, Nov 1, 2011 at 11:28 AM, Bernd Bohmann bernd.bohm...@atanion.com wrote: Ok, if there is no real difference between Apache Incubator and Apache MyFaces Incubator, I have to change my vote to -1 especially a have a problem with: All code donations from external organisations and existing external projects wishing to join MyFaces enter through the MyFaces-Incubator. This is the Apache Incubator role. Regards Bernd On Tue, Nov 1, 2011 at 10:25 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi bart, as mentioned [1] by mark it's also about ip clearance [2]. regards, gerhard [1] http://mail-archives.apache.org/mod_mbox/myfaces-dev/201110.mbox/%3c1319274310.93350.yahoomail...@web27807.mail.ukl.yahoo.com%3E [2] http://incubator.apache.org/ip-clearance/index.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/1 Bart Kummel b...@kummelweb.nl +1 for the idea! I agree with Bernd about the name. For me, incubator is also associated with rules and legal stuff. We should encourage people to contribute, instead of scaring them away. Sandbox or labs sounds encouraging and accessible. But perhaps we should discuss/vote the name in another thread and first focus on the idea... Best regards, Bart Kummel On Tue, Nov 1, 2011 at 01:36, Gerhard Petracek gerhard.petra...@gmail.com wrote: Hi, in order to check if there is a community for a new sub-project (esp. GSoC projects for MyFaces), we discussed [1] the introduction of an internal incubator. We would release such projects early and e.g. after a quarter we decide if we keep and promote a project (as a sub-project or a module of an existing sub-project) or if we drop it. Please vote: [+1] I like the idea [0] I'm not convinced but I'm ok with it [-1] I don't agree Regards, Gerhard [1] http://markmail.org/message/d7oogfabvliwn7fg -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
MyFaces Parent 11-SNAPSHOT
HI guys, I just saw that some days ago the version of the parent pom in myfaces-core was changed to 11-SNAPSHOT. I had no problems with this as I had the dependency in my repo. But we just had problems on a 'clean' machine. Maven could not find the dependency. So I guess the solution would be: a) Add the snapshot repository to myfaces-parent. b) Revert to version 10 of the parent. I fixed something like this some weeks ago for snapshot plugins. So if someone can confirm this I can make the according change. regards Michael
Re: [VOTE] Internal Incubator
besides labs (see [1]) i agree for the existing gsoc projects like: - component library for html5 components - webapp-test btw. webapp-test2 (manila) - codi-rad i'm perfectly fine with a) since the basic topic was the quick community check. - we should start a new thread for checking potential participants. regards, gerhard [1] http://markmail.org/message/c6vcpqbdpqygjwkt 2011/11/2 Matthias Wessendorf mat...@apache.org: Why incubator for Gsoc projects? IMO that's wrong. Move stuff like that to Labs: build code and get releases out (release often, release early) Once there is interest - by some community decide where to go: There some options, like: a) Going to the incubator - start to build a community around it ( the new experimental code base) b) if it makes sense, integrate it with existing MyFaces code (e.g. partial state savings improvements etc) (or make it Apache MyFaces subproject) -M On Wed, Nov 2, 2011 at 2:00 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: i think we should stop the vote and re-visit the original thread at [1]. there we could discuss the name and we could re-visit the option to use the asf incubator directly (for gsoc projects). regards, gerhard [1] http://markmail.org/message/d7oogfabvliwn7fg 2011/11/2 Gerhard Petracek gerhard.petra...@gmail.com: thx matt for the links regards, gerhard 2011/11/2 Matt Benson gudnabr...@gmail.com: On Wed, Nov 2, 2011 at 6:32 AM, Matthias Wessendorf mat...@apache.org wrote: FWIW: -1 why introducing yet another level of incubation process ? I find it (very) problematic trying to be in some sort of competition w/ the Apache Incubator... (even if the discussed targets here are JSF specific) As I have attempted to point out elsewhere via email links (which presumably went unfollowed), not only is this problematic; per Incubator PMC consensus it is downright unacceptable. You simply can't have a mini-incubator so complete that it makes sense even to use the *name* incubator. PLEASE read [1] for background, or skip directly to [2] (search for Some possible solutions) to know what IS acceptable. There is no need for MyFaces to rehash my experiences on Commons' behalf two-plus years ago. [1] http://markmail.org/message/n3t7lksceuplh45r [2] http://markmail.org/message/r6ffmmyh6pxnn6nd Matt Why not simply moving future (MyFaces) GSoC directly to the Apache Labs project ([1])?! For there, just start coding and releasing (alphas etc). The new release process is straightforward and not heavyweight - so (alpha) releases are cheap. -M [1] http://labs.apache.org/ On Tue, Nov 1, 2011 at 11:28 AM, Bernd Bohmann bernd.bohm...@atanion.com wrote: Ok, if there is no real difference between Apache Incubator and Apache MyFaces Incubator, I have to change my vote to -1 especially a have a problem with: All code donations from external organisations and existing external projects wishing to join MyFaces enter through the MyFaces-Incubator. This is the Apache Incubator role. Regards Bernd On Tue, Nov 1, 2011 at 10:25 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi bart, as mentioned [1] by mark it's also about ip clearance [2]. regards, gerhard [1] http://mail-archives.apache.org/mod_mbox/myfaces-dev/201110.mbox/%3c1319274310.93350.yahoomail...@web27807.mail.ukl.yahoo.com%3E [2] http://incubator.apache.org/ip-clearance/index.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/1 Bart Kummel b...@kummelweb.nl +1 for the idea! I agree with Bernd about the name. For me, incubator is also associated with rules and legal stuff. We should encourage people to contribute, instead of scaring them away. Sandbox or labs sounds encouraging and accessible. But perhaps we should discuss/vote the name in another thread and first focus on the idea... Best regards, Bart Kummel On Tue, Nov 1, 2011 at 01:36, Gerhard Petracek gerhard.petra...@gmail.com wrote: Hi, in order to check if there is a community for a new sub-project (esp. GSoC projects for MyFaces), we discussed [1] the introduction of an internal incubator. We would release such projects early and e.g. after a quarter we decide if we keep and promote a project (as a sub-project or a module of an existing sub-project) or if we drop it. Please vote: [+1] I like the idea [0] I'm not convinced but I'm ok with it [-1] I don't agree Regards, Gerhard [1] http://markmail.org/message/d7oogfabvliwn7fg -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] [Created] (EXTVAL-137) Deregistering a class from the NameMapperFactory results in unsupported operation on CopyOnWriteArrayList
Deregistering a class from the NameMapperFactory results in unsupported operation on CopyOnWriteArrayList - Key: EXTVAL-137 URL: https://issues.apache.org/jira/browse/EXTVAL-137 Project: MyFaces Extensions Validator Issue Type: Bug Components: Core Affects Versions: 2.0.4, 1.2.4 Reporter: Rudy De Busscher Assignee: Rudy De Busscher Priority: Minor If you wan't to deregister a NameMapper from the Factory class, so that it isn't used in your application, you get an exception because (some) factories use a CopyOnWriteArrayList List implementation. For example ClassMappingFactory factory = ExtValContext.getContext().getFactoryFinder() .getFactory(FactoryNames.STORAGE_MANAGER_FACTORY, ClassMappingFactory.class); NameMapperAwareFactory nameMapperFactory = (NameMapperAwareFactory) factory.create(ProcessedInformationStorage.class); nameMapperFactory.deny(ProcessedInformationStorageNameMapper.class); // Code omitted to add the custom nameMapper -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (EXTVAL-137) Deregistering a class from the NameMapperFactory results in unsupported operation on CopyOnWriteArrayList
[ https://issues.apache.org/jira/browse/EXTVAL-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13142205#comment-13142205 ] Rudy De Busscher commented on EXTVAL-137: - There exists in many cases a workaround to define an appropiate InvocationOrder annotation on your custom NameMapper so that it is tried as the first NameMapper. @InvocationOrder(value = 1) Deregistering a class from the NameMapperFactory results in unsupported operation on CopyOnWriteArrayList - Key: EXTVAL-137 URL: https://issues.apache.org/jira/browse/EXTVAL-137 Project: MyFaces Extensions Validator Issue Type: Bug Components: Core Affects Versions: 1.2.4, 2.0.4 Reporter: Rudy De Busscher Assignee: Rudy De Busscher Priority: Minor If you wan't to deregister a NameMapper from the Factory class, so that it isn't used in your application, you get an exception because (some) factories use a CopyOnWriteArrayList List implementation. For example ClassMappingFactory factory = ExtValContext.getContext().getFactoryFinder() .getFactory(FactoryNames.STORAGE_MANAGER_FACTORY, ClassMappingFactory.class); NameMapperAwareFactory nameMapperFactory = (NameMapperAwareFactory) factory.create(ProcessedInformationStorage.class); nameMapperFactory.deny(ProcessedInformationStorageNameMapper.class); // Code omitted to add the custom nameMapper -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (EXTVAL-137) Deregistering a class from the NameMapperFactory results in unsupported operation on CopyOnWriteArrayList
[ https://issues.apache.org/jira/browse/EXTVAL-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rudy De Busscher resolved EXTVAL-137. - Resolution: Fixed Fix Version/s: 1.2.5 2.0.5 Deregistering a class from the NameMapperFactory results in unsupported operation on CopyOnWriteArrayList - Key: EXTVAL-137 URL: https://issues.apache.org/jira/browse/EXTVAL-137 Project: MyFaces Extensions Validator Issue Type: Bug Components: Core Affects Versions: 1.2.4, 2.0.4 Reporter: Rudy De Busscher Assignee: Rudy De Busscher Priority: Minor Fix For: 2.0.5, 1.2.5 If you wan't to deregister a NameMapper from the Factory class, so that it isn't used in your application, you get an exception because (some) factories use a CopyOnWriteArrayList List implementation. For example ClassMappingFactory factory = ExtValContext.getContext().getFactoryFinder() .getFactory(FactoryNames.STORAGE_MANAGER_FACTORY, ClassMappingFactory.class); NameMapperAwareFactory nameMapperFactory = (NameMapperAwareFactory) factory.create(ProcessedInformationStorage.class); nameMapperFactory.deny(ProcessedInformationStorageNameMapper.class); // Code omitted to add the custom nameMapper -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: MyFaces Parent 11-SNAPSHOT
Hi Michael It is better to do a) Add the snapshot repository to myfaces-parent. I hope to send a vote to release myfaces master pom and myfaces checkstyle rules soon, to fix the problem, but it will take some days before publish the artifacts on the repo. regards, Leonardo Uribe 2011/11/2 Michael Kurz michi.k...@gmx.at: HI guys, I just saw that some days ago the version of the parent pom in myfaces-core was changed to 11-SNAPSHOT. I had no problems with this as I had the dependency in my repo. But we just had problems on a 'clean' machine. Maven could not find the dependency. So I guess the solution would be: a) Add the snapshot repository to myfaces-parent. b) Revert to version 10 of the parent. I fixed something like this some weeks ago for snapshot plugins. So if someone can confirm this I can make the according change. regards Michael
[VOTE] release for myfaces master pom v 11
Hi, I was running the needed tasks to get the version 11 release of Apache MyFaces Master POM. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.myfaces v 11 [1] 2. Maven artifact group org.apache.myfaces.buildtools checkstyle-rules v 3 The artifacts are deployed to a nexus staging repository [1]. Please take a look at the version 11 pom and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-142 https://repository.apache.org/content/groups/staging/org/apache/myfaces/myfaces/11/ https://repository.apache.org/content/groups/staging/org/apache/myfaces/buildtools/checkstyle-rules/3/
Re: [VOTE] release for myfaces master pom v 11
+1 2011/11/2 Leonardo Uribe lu4...@gmail.com: Hi, I was running the needed tasks to get the version 11 release of Apache MyFaces Master POM. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.myfaces v 11 [1] 2. Maven artifact group org.apache.myfaces.buildtools checkstyle-rules v 3 The artifacts are deployed to a nexus staging repository [1]. Please take a look at the version 11 pom and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-142 https://repository.apache.org/content/groups/staging/org/apache/myfaces/myfaces/11/ https://repository.apache.org/content/groups/staging/org/apache/myfaces/buildtools/checkstyle-rules/3/
Re: Several main links on the Trinidad home page are broken
The link at the Trinidad page still points to http://www.irian.at/trinidad-examples which is wrong. For now Irian has put a 301 redirect to http://example.irian.at/trinidad-demo/ but note that this is just a temporary solution. It would be nice if someone with access rights could change the links on http://myfaces.apache.org/trinidad/ to get a permanent solution. Regards, Jan (Irian employee) On Thu, Oct 20, 2011 at 9:12 PM, Jan Zarnikov jan.zarni...@gmail.com wrote: Hi Victor, thanks for the report. Irian has completely redesigned the homepage and the links to www.irian.at/trinidad-examples are no longer valid. You can use http://example.irian.at/trinidad-demo/ and the component showcase at http://example.irian.at/trinidad-components-showcase/ @MyFaces Devs: Can somebody with access to the MyFaces page change the links? Please make sure that the links go to example.irian.com and not www.irian.at/something or irian.at/something Regards, Jan On Thu, Oct 20, 2011 at 5:06 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi victor, the live-demos should be back online within the next days. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/10/20 Victor Gradinescu victor.gradine...@gmail.com Hi, I've heard of the trinidad project and wanted to check it out but most of the links on the home page (left menu) are broken (Live Demos, for example). What's the status of this project? Thank you, Victor
Re: [html5] alpha release for myfaces html5
One important point is labs projects are not allowed to make releases.
Sent from Android
On Nov 2, 2011 1:22 PM, Gerhard Petracek gerhard.petra...@gmail.com
wrote:
see [1] - esp.:
Apache Labs are the place where ASF committers can work on innovative,
blue-sky and off-the-wall ideas, without having to worry about fitting in
an existing project bylaw or building a community around it...
we already know that it works and it's just about a community check
- imo labs doesn't fit and the alternative would be the incubator
itself.
regards,
gerhard
[1] http://labs.apache.org/bylaws.html
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/11/2 Matthias Wessendorf mat...@apache.org:
I don't get why not just having a simple alpha release ?
Does not hurt... Or... move the entire thing to Apache Labs... for
future experiments ?!
-M
On Tue, Nov 1, 2011 at 12:03 AM, Ali Ok al...@aliok.com.tr wrote:
Hi,
So do you think myfaces/incubator/html5 is a good place?
Greetings,
Ali
On Sat, Oct 22, 2011 at 1:37 PM, Ali Ok al...@aliok.com.tr wrote:
Hi,
In my opinion as long this lib is html5 only it should not be part of
the tomahawk project
I agree, no relation with Tomahawk.
a different idea would be a small myfaces-incubator for new
project-ideas
(esp. for gsoc projects).
Makes more sense to me than Tomahawk.
I think (almost) everyone is in favor of moving the project to
somewhere
else, I am also ok with it.
Important thing for the project is having the ability for releases and
the
jars are deployed to maven repo.
Cheers,
Ali
On Sat, Oct 22, 2011 at 11:05 AM, Mark Struberg strub...@yahoo.de
wrote:
including our very own little 'attic' :)
Actually the big difference between the incubator and a mf subproject
would be the IP clearance. We really need to do this upfront before
importing.
But actually I like this much more than having projects developed
outside
and only later brought into our SVN - because this causes lots of
paperwork
(gas grants and a IP clearance review is mandatory).
Thus a +1
LieGrue,
strub
From: Gerhard Petracek gerhard.petra...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Sent: Saturday, October 22, 2011 10:58 AM
Subject: Re: [html5] alpha release for myfaces html5
a different idea would be a small myfaces-incubator for new
project-ideas (esp. for gsoc projects).
we can release parts easily and drop them if we see that something
doesn't work for our community. if an idea works for the community,
we can
discuss the correct place for it.
we might see new gsoc projects (related to myfaces) every year. imo
it's
the wrong approach to just add them as new sub-project and we don't
have the
resources/community to maintain them.
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/10/22 Bernd Bohmann bernd.bohm...@atanion.com
Ha, I don't think we should wait for the jsf-eg.
Hey guys they are asking for a alpha release.
In my opinion as long this lib is html5 only it should not be part
of
the tomahawk project.
I don't see any problems in releasing an alpha release. But before a
beta we should decide own extension or tomahawk.
Regards
Bernd
On Sat, Oct 22, 2011 at 9:31 AM, Gerhard Petracek
gerhard.petra...@gmail.com wrote:
it's planned that jsf2.2 will get some sort of html5 support.
imo we should work together with the jsf-eg to ensure that we
won't
promote
incompatible components.
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/10/22 Mark Struberg strub...@yahoo.de
+1 for moving it to tomahawk.
One big open question for me is our html5 strategy at all.
Will the html5 components provide legacy html support themselfs?
Thus a calendar component will use jQuery (or whatever) calendar
when a
non-html5 browser is detected,
or is this in the responsibility of the developer?
if (html5){
} else{
//fallback
}
?
Afaik our current html5 components 'only' support pure html5
rendering,
isn't?
LieGrue,
strub
From: Gerhard Petracek gerhard.petra...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Sent: Friday, October 21, 2011 10:22 PM
Subject: Re: [html5] alpha release for myfaces html5
@grant: +1
regards,
gerhard
http://www.irian.at
Your JSF
Re: [VOTE] release for myfaces master pom v 11
+1 txs and LieGrue, strub - Original Message - From: Leonardo Uribe lu4...@gmail.com To: MyFaces Development dev@myfaces.apache.org Cc: Sent: Wednesday, November 2, 2011 6:13 PM Subject: Re: [VOTE] release for myfaces master pom v 11 +1 2011/11/2 Leonardo Uribe lu4...@gmail.com: Hi, I was running the needed tasks to get the version 11 release of Apache MyFaces Master POM. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.myfaces v 11 [1] 2. Maven artifact group org.apache.myfaces.buildtools checkstyle-rules v 3 The artifacts are deployed to a nexus staging repository [1]. Please take a look at the version 11 pom and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-142 https://repository.apache.org/content/groups/staging/org/apache/myfaces/myfaces/11/ https://repository.apache.org/content/groups/staging/org/apache/myfaces/buildtools/checkstyle-rules/3/
Re: [VOTE] release for myfaces master pom v 11
+1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Mark Struberg strub...@yahoo.de: +1 txs and LieGrue, strub - Original Message - From: Leonardo Uribe lu4...@gmail.com To: MyFaces Development dev@myfaces.apache.org Cc: Sent: Wednesday, November 2, 2011 6:13 PM Subject: Re: [VOTE] release for myfaces master pom v 11 +1 2011/11/2 Leonardo Uribe lu4...@gmail.com: Hi, I was running the needed tasks to get the version 11 release of Apache MyFaces Master POM. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.myfaces v 11 [1] 2. Maven artifact group org.apache.myfaces.buildtools checkstyle-rules v 3 The artifacts are deployed to a nexus staging repository [1]. Please take a look at the version 11 pom and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-142 https://repository.apache.org/content/groups/staging/org/apache/myfaces/myfaces/11/ https://repository.apache.org/content/groups/staging/org/apache/myfaces/buildtools/checkstyle-rules/3/
Re: [Trinidad] Possible to skip certain stops in a train model?
Hello Phuu,
On 11/2/2011 2:44 AM, Phuu Tek wrote:
Hi,
I am looking at implementing my own custom Train Model using my custom
ProcessMenuModel
public ProcessMenuModel getTrainModel() {
}
However, I have a specific use case wherein I should be able to skip
certain stops in my train.
Say for example, I have seven stops then on Step 2, I choose something
from that page.
Is it possible to disable Steps 3 and 4 programatically so that user
wont be able to navigate to that page?
Step 5, 6 and 7 should still be available.
You most certainly can, by setting an EL for the disabled attribute of
the tr:commandNavigationItem .The EL will obviously return 'true' for
the stops you want disabled.
Thanks
Pavitra
Thanks
Re: MyFaces Parent 11-SNAPSHOT
Hi Leo, I mixed up the artifacts. We should add the snapshot repository to the pom file of myfaces-core to fix the build. If we add it to the parent, a snapshot parent won't be found. But maybe we talk about the same anyway ;) regards Michael Am 02.11.2011 um 17:40 schrieb Leonardo Uribe lu4...@gmail.com: Hi Michael It is better to do a) Add the snapshot repository to myfaces-parent. I hope to send a vote to release myfaces master pom and myfaces checkstyle rules soon, to fix the problem, but it will take some days before publish the artifacts on the repo. regards, Leonardo Uribe 2011/11/2 Michael Kurz michi.k...@gmx.at: HI guys, I just saw that some days ago the version of the parent pom in myfaces-core was changed to 11-SNAPSHOT. I had no problems with this as I had the dependency in my repo. But we just had problems on a 'clean' machine. Maven could not find the dependency. So I guess the solution would be: a) Add the snapshot repository to myfaces-parent. b) Revert to version 10 of the parent. I fixed something like this some weeks ago for snapshot plugins. So if someone can confirm this I can make the according change. regards Michael
Re: MyFaces Parent 11-SNAPSHOT
any apache snapshots will get deployed to apache.snapshots which should be configured in apache-parent. Thus we don't need to add it ourselfs. LieGrue, strub - Original Message - From: Michael Kurz michi.k...@gmx.at To: MyFaces Development dev@myfaces.apache.org Cc: Sent: Wednesday, November 2, 2011 8:01 PM Subject: Re: MyFaces Parent 11-SNAPSHOT Hi Leo, I mixed up the artifacts. We should add the snapshot repository to the pom file of myfaces-core to fix the build. If we add it to the parent, a snapshot parent won't be found. But maybe we talk about the same anyway ;) regards Michael Am 02.11.2011 um 17:40 schrieb Leonardo Uribe lu4...@gmail.com: Hi Michael It is better to do a) Add the snapshot repository to myfaces-parent. I hope to send a vote to release myfaces master pom and myfaces checkstyle rules soon, to fix the problem, but it will take some days before publish the artifacts on the repo. regards, Leonardo Uribe 2011/11/2 Michael Kurz michi.k...@gmx.at: HI guys, I just saw that some days ago the version of the parent pom in myfaces-core was changed to 11-SNAPSHOT. I had no problems with this as I had the dependency in my repo. But we just had problems on a 'clean' machine. Maven could not find the dependency. So I guess the solution would be: a) Add the snapshot repository to myfaces-parent. b) Revert to version 10 of the parent. I fixed something like this some weeks ago for snapshot plugins. So if someone can confirm this I can make the according change. regards Michael
Re: [html5] alpha release for myfaces html5
that's stupid :-)
Personal releases are IMO possible (e.g. deployment to p.a.o/~asf-id)
-M
On Wed, Nov 2, 2011 at 6:35 PM, Ali Ok al...@aliok.com.tr wrote:
One important point is labs projects are not allowed to make releases.
Sent from Android
On Nov 2, 2011 1:22 PM, Gerhard Petracek gerhard.petra...@gmail.com
wrote:
see [1] - esp.:
Apache Labs are the place where ASF committers can work on innovative,
blue-sky and off-the-wall ideas, without having to worry about fitting in
an
existing project bylaw or building a community around it...
we already know that it works and it's just about a community check
- imo labs doesn't fit and the alternative would be the incubator
itself.
regards,
gerhard
[1] http://labs.apache.org/bylaws.html
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/11/2 Matthias Wessendorf mat...@apache.org:
I don't get why not just having a simple alpha release ?
Does not hurt... Or... move the entire thing to Apache Labs... for
future experiments ?!
-M
On Tue, Nov 1, 2011 at 12:03 AM, Ali Ok al...@aliok.com.tr wrote:
Hi,
So do you think myfaces/incubator/html5 is a good place?
Greetings,
Ali
On Sat, Oct 22, 2011 at 1:37 PM, Ali Ok al...@aliok.com.tr wrote:
Hi,
In my opinion as long this lib is html5 only it should not be part of
the tomahawk project
I agree, no relation with Tomahawk.
a different idea would be a small myfaces-incubator for new
project-ideas
(esp. for gsoc projects).
Makes more sense to me than Tomahawk.
I think (almost) everyone is in favor of moving the project to
somewhere
else, I am also ok with it.
Important thing for the project is having the ability for releases and
the
jars are deployed to maven repo.
Cheers,
Ali
On Sat, Oct 22, 2011 at 11:05 AM, Mark Struberg strub...@yahoo.de
wrote:
including our very own little 'attic' :)
Actually the big difference between the incubator and a mf subproject
would be the IP clearance. We really need to do this upfront before
importing.
But actually I like this much more than having projects developed
outside
and only later brought into our SVN - because this causes lots of
paperwork
(gas grants and a IP clearance review is mandatory).
Thus a +1
LieGrue,
strub
From: Gerhard Petracek gerhard.petra...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Sent: Saturday, October 22, 2011 10:58 AM
Subject: Re: [html5] alpha release for myfaces html5
a different idea would be a small myfaces-incubator for new
project-ideas (esp. for gsoc projects).
we can release parts easily and drop them if we see that something
doesn't work for our community. if an idea works for the community,
we can
discuss the correct place for it.
we might see new gsoc projects (related to myfaces) every year. imo
it's
the wrong approach to just add them as new sub-project and we don't
have the
resources/community to maintain them.
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/10/22 Bernd Bohmann bernd.bohm...@atanion.com
Ha, I don't think we should wait for the jsf-eg.
Hey guys they are asking for a alpha release.
In my opinion as long this lib is html5 only it should not be part
of
the tomahawk project.
I don't see any problems in releasing an alpha release. But before
a
beta we should decide own extension or tomahawk.
Regards
Bernd
On Sat, Oct 22, 2011 at 9:31 AM, Gerhard Petracek
gerhard.petra...@gmail.com wrote:
it's planned that jsf2.2 will get some sort of html5 support.
imo we should work together with the jsf-eg to ensure that we
won't
promote
incompatible components.
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/10/22 Mark Struberg strub...@yahoo.de
+1 for moving it to tomahawk.
One big open question for me is our html5 strategy at all.
Will the html5 components provide legacy html support themselfs?
Thus a calendar component will use jQuery (or whatever) calendar
when a
non-html5 browser is detected,
or is this in the responsibility of the developer?
if (html5){
} else{
//fallback
}
?
Afaik our current html5 components 'only' support pure html5
rendering,
isn't?
LieGrue,
strub
From: Gerhard Petracek gerhard.petra...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Sent: Friday,
Re: MyFaces Parent 11-SNAPSHOT
But if Maven can't resolve the myfaces-parent (as it is a snapshot) it won't find apache-parent either. regards Michael Am 02.11.2011 um 20:13 schrieb Mark Struberg strub...@yahoo.de: any apache snapshots will get deployed to apache.snapshots which should be configured in apache-parent. Thus we don't need to add it ourselfs. LieGrue, strub - Original Message - From: Michael Kurz michi.k...@gmx.at To: MyFaces Development dev@myfaces.apache.org Cc: Sent: Wednesday, November 2, 2011 8:01 PM Subject: Re: MyFaces Parent 11-SNAPSHOT Hi Leo, I mixed up the artifacts. We should add the snapshot repository to the pom file of myfaces-core to fix the build. If we add it to the parent, a snapshot parent won't be found. But maybe we talk about the same anyway ;) regards Michael Am 02.11.2011 um 17:40 schrieb Leonardo Uribe lu4...@gmail.com: Hi Michael It is better to do a) Add the snapshot repository to myfaces-parent. I hope to send a vote to release myfaces master pom and myfaces checkstyle rules soon, to fix the problem, but it will take some days before publish the artifacts on the repo. regards, Leonardo Uribe 2011/11/2 Michael Kurz michi.k...@gmx.at: HI guys, I just saw that some days ago the version of the parent pom in myfaces-core was changed to 11-SNAPSHOT. I had no problems with this as I had the dependency in my repo. But we just had problems on a 'clean' machine. Maven could not find the dependency. So I guess the solution would be: a) Add the snapshot repository to myfaces-parent. b) Revert to version 10 of the parent. I fixed something like this some weeks ago for snapshot plugins. So if someone can confirm this I can make the according change. regards Michael
Re: [html5] alpha release for myfaces html5
@matthias: apache labs are only for prototyping and the next step is e.g. the incubator for building a community (see [1]). regards, gerhard [1] http://labs.apache.org/bylaws.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Matthias Wessendorf mat...@apache.org: that's stupid :-) Personal releases are IMO possible (e.g. deployment to p.a.o/~asf-id) -M On Wed, Nov 2, 2011 at 6:35 PM, Ali Ok al...@aliok.com.tr wrote: One important point is labs projects are not allowed to make releases. Sent from Android On Nov 2, 2011 1:22 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: see [1] - esp.: Apache Labs are the place where ASF committers can work on innovative, blue-sky and off-the-wall ideas, without having to worry about fitting in an existing project bylaw or building a community around it... we already know that it works and it's just about a community check - imo labs doesn't fit and the alternative would be the incubator itself. regards, gerhard [1] http://labs.apache.org/bylaws.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Matthias Wessendorf mat...@apache.org: I don't get why not just having a simple alpha release ? Does not hurt... Or... move the entire thing to Apache Labs... for future experiments ?! -M On Tue, Nov 1, 2011 at 12:03 AM, Ali Ok al...@aliok.com.tr wrote: Hi, So do you think myfaces/incubator/html5 is a good place? Greetings, Ali On Sat, Oct 22, 2011 at 1:37 PM, Ali Ok al...@aliok.com.tr wrote: Hi, In my opinion as long this lib is html5 only it should not be part of the tomahawk project I agree, no relation with Tomahawk. a different idea would be a small myfaces-incubator for new project-ideas (esp. for gsoc projects). Makes more sense to me than Tomahawk. I think (almost) everyone is in favor of moving the project to somewhere else, I am also ok with it. Important thing for the project is having the ability for releases and the jars are deployed to maven repo. Cheers, Ali On Sat, Oct 22, 2011 at 11:05 AM, Mark Struberg strub...@yahoo.de wrote: including our very own little 'attic' :) Actually the big difference between the incubator and a mf subproject would be the IP clearance. We really need to do this upfront before importing. But actually I like this much more than having projects developed outside and only later brought into our SVN - because this causes lots of paperwork (gas grants and a IP clearance review is mandatory). Thus a +1 LieGrue, strub From: Gerhard Petracek gerhard.petra...@gmail.com To: MyFaces Development dev@myfaces.apache.org Sent: Saturday, October 22, 2011 10:58 AM Subject: Re: [html5] alpha release for myfaces html5 a different idea would be a small myfaces-incubator for new project-ideas (esp. for gsoc projects). we can release parts easily and drop them if we see that something doesn't work for our community. if an idea works for the community, we can discuss the correct place for it. we might see new gsoc projects (related to myfaces) every year. imo it's the wrong approach to just add them as new sub-project and we don't have the resources/community to maintain them. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/10/22 Bernd Bohmann bernd.bohm...@atanion.com Ha, I don't think we should wait for the jsf-eg. Hey guys they are asking for a alpha release. In my opinion as long this lib is html5 only it should not be part of the tomahawk project. I don't see any problems in releasing an alpha release. But before a beta we should decide own extension or tomahawk. Regards Bernd On Sat, Oct 22, 2011 at 9:31 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: it's planned that jsf2.2 will get some sort of html5 support. imo we should work together with the jsf-eg to ensure that we won't promote incompatible components. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/10/22 Mark Struberg strub...@yahoo.de +1 for moving it to tomahawk. One big open question for me is our html5 strategy at all. Will the html5 components provide legacy html support themselfs? Thus a calendar component will use jQuery (or whatever) calendar when a non-html5 browser is detected, or is this in the
Re: MyFaces Parent 11-SNAPSHOT
uh yes, true ^^ repository sections in parent poms are somehow questionable ... ;) LieGrue, strub - Original Message - From: Michael Kurz michi.k...@gmx.at To: MyFaces Development dev@myfaces.apache.org Cc: Sent: Wednesday, November 2, 2011 9:00 PM Subject: Re: MyFaces Parent 11-SNAPSHOT But if Maven can't resolve the myfaces-parent (as it is a snapshot) it won't find apache-parent either. regards Michael Am 02.11.2011 um 20:13 schrieb Mark Struberg strub...@yahoo.de: any apache snapshots will get deployed to apache.snapshots which should be configured in apache-parent. Thus we don't need to add it ourselfs. LieGrue, strub - Original Message - From: Michael Kurz michi.k...@gmx.at To: MyFaces Development dev@myfaces.apache.org Cc: Sent: Wednesday, November 2, 2011 8:01 PM Subject: Re: MyFaces Parent 11-SNAPSHOT Hi Leo, I mixed up the artifacts. We should add the snapshot repository to the pom file of myfaces-core to fix the build. If we add it to the parent, a snapshot parent won't be found. But maybe we talk about the same anyway ;) regards Michael Am 02.11.2011 um 17:40 schrieb Leonardo Uribe lu4...@gmail.com: Hi Michael It is better to do a) Add the snapshot repository to myfaces-parent. I hope to send a vote to release myfaces master pom and myfaces checkstyle rules soon, to fix the problem, but it will take some days before publish the artifacts on the repo. regards, Leonardo Uribe 2011/11/2 Michael Kurz michi.k...@gmx.at: HI guys, I just saw that some days ago the version of the parent pom in myfaces-core was changed to 11-SNAPSHOT. I had no problems with this as I had the dependency in my repo. But we just had problems on a 'clean' machine. Maven could not find the dependency. So I guess the solution would be: a) Add the snapshot repository to myfaces-parent. b) Revert to version 10 of the parent. I fixed something like this some weeks ago for snapshot plugins. So if someone can confirm this I can make the according change. regards Michael
Re: [VOTE] release for myfaces master pom v 11
+1 On Wed, Nov 2, 2011 at 11:24 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: +1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Mark Struberg strub...@yahoo.de: +1 txs and LieGrue, strub - Original Message - From: Leonardo Uribe lu4...@gmail.com To: MyFaces Development dev@myfaces.apache.org Cc: Sent: Wednesday, November 2, 2011 6:13 PM Subject: Re: [VOTE] release for myfaces master pom v 11 +1 2011/11/2 Leonardo Uribe lu4...@gmail.com: Hi, I was running the needed tasks to get the version 11 release of Apache MyFaces Master POM. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.myfaces v 11 [1] 2. Maven artifact group org.apache.myfaces.buildtools checkstyle-rules v 3 The artifacts are deployed to a nexus staging repository [1]. Please take a look at the version 11 pom and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-142 https://repository.apache.org/content/groups/staging/org/apache/myfaces/myfaces/11/ https://repository.apache.org/content/groups/staging/org/apache/myfaces/buildtools/checkstyle-rules/3/ -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC.
Re: [html5] alpha release for myfaces html5
I guess the question is what are you (all) trying to accomplish? If we have active committers who want to create an html5 subproject, it seems like our policy thus far is to create it. If we only have a code-dump, it should go through the incubator -- we have done this with other things which are now myfaces subprojects. If enough of the incubated project members are myfaces committers, then it would likely become a myfaces subproject. If there is no overlap, it would have to find its own place. Working out how much is enough and training up non-myfaces-committers would be the task of incubation. If the goal is to change our policies for new subprojects, then I don't see that incubation or apache labs is really relevant -- we're only talking about our own internal organization.And if we're changing our policies, I would hope that whatever we come up with applies to all existing projects as well as new projects. Or, in other words, we shouldn't be treating the html5 subproject any differently than we do anything else. Sandbox was a good start, but we've been having issues with getting things out of sandbox for several years now. I suspect this is why the trend recently has been to skip the sandbox and dive right in with a new subproject. While my personal preference would have been to reform the sandbox, I wasn't really doing any of the work. The folks doing the work have been making the subprojects idea succeed, so from a meritocracy point of view, I'd say that's the future, until something else better comes along. Maybe we're now at the point where some of us do want to see if we can come up with something better. Like I said, I personally think our explosion of subprojects is disorganized and confusing. But if that's our goal, let's say so, and apply it to everything. In the meantime, my opinion is that if we have html5 committers, we allow the html5 committers to have a subproject and move forward with a release. Regards, Mike On Wed, Nov 2, 2011 at 4:13 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: @matthias: apache labs are only for prototyping and the next step is e.g. the incubator for building a community (see [1]). regards, gerhard [1] http://labs.apache.org/bylaws.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Matthias Wessendorf mat...@apache.org: that's stupid :-) Personal releases are IMO possible (e.g. deployment to p.a.o/~asf-id) -M On Wed, Nov 2, 2011 at 6:35 PM, Ali Ok al...@aliok.com.tr wrote: One important point is labs projects are not allowed to make releases. Sent from Android On Nov 2, 2011 1:22 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: see [1] - esp.: Apache Labs are the place where ASF committers can work on innovative, blue-sky and off-the-wall ideas, without having to worry about fitting in an existing project bylaw or building a community around it... we already know that it works and it's just about a community check - imo labs doesn't fit and the alternative would be the incubator itself. regards, gerhard [1] http://labs.apache.org/bylaws.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Matthias Wessendorf mat...@apache.org: I don't get why not just having a simple alpha release ? Does not hurt... Or... move the entire thing to Apache Labs... for future experiments ?! -M On Tue, Nov 1, 2011 at 12:03 AM, Ali Ok al...@aliok.com.tr wrote: Hi, So do you think myfaces/incubator/html5 is a good place? Greetings, Ali On Sat, Oct 22, 2011 at 1:37 PM, Ali Ok al...@aliok.com.tr wrote: Hi, In my opinion as long this lib is html5 only it should not be part of the tomahawk project I agree, no relation with Tomahawk. a different idea would be a small myfaces-incubator for new project-ideas (esp. for gsoc projects). Makes more sense to me than Tomahawk. I think (almost) everyone is in favor of moving the project to somewhere else, I am also ok with it. Important thing for the project is having the ability for releases and the jars are deployed to maven repo. Cheers, Ali On Sat, Oct 22, 2011 at 11:05 AM, Mark Struberg strub...@yahoo.de wrote: including our very own little 'attic' :) Actually the big difference between the incubator and a mf subproject would be the IP clearance. We really need to do this upfront before importing. But actually I like this much more than having projects developed outside and only later brought into our SVN - because this causes lots of paperwork (gas grants and a IP clearance review is mandatory). Thus a +1 LieGrue, strub From: Gerhard Petracek gerhard.petra...@gmail.com To: MyFaces
Re: [html5] alpha release for myfaces html5
On Wed, Nov 2, 2011 at 9:13 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: @matthias: apache labs are only for prototyping and the next step is e.g. the incubator for building a community (see [1]). perfect for new GSoC projects, IMO However, generally Apache Labs is (unfortunately) pretty limited (not sure I why would actually do stuff there (instead of at github etc)) -M regards, gerhard [1] http://labs.apache.org/bylaws.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Matthias Wessendorf mat...@apache.org: that's stupid :-) Personal releases are IMO possible (e.g. deployment to p.a.o/~asf-id) -M On Wed, Nov 2, 2011 at 6:35 PM, Ali Ok al...@aliok.com.tr wrote: One important point is labs projects are not allowed to make releases. Sent from Android On Nov 2, 2011 1:22 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: see [1] - esp.: Apache Labs are the place where ASF committers can work on innovative, blue-sky and off-the-wall ideas, without having to worry about fitting in an existing project bylaw or building a community around it... we already know that it works and it's just about a community check - imo labs doesn't fit and the alternative would be the incubator itself. regards, gerhard [1] http://labs.apache.org/bylaws.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Matthias Wessendorf mat...@apache.org: I don't get why not just having a simple alpha release ? Does not hurt... Or... move the entire thing to Apache Labs... for future experiments ?! -M On Tue, Nov 1, 2011 at 12:03 AM, Ali Ok al...@aliok.com.tr wrote: Hi, So do you think myfaces/incubator/html5 is a good place? Greetings, Ali On Sat, Oct 22, 2011 at 1:37 PM, Ali Ok al...@aliok.com.tr wrote: Hi, In my opinion as long this lib is html5 only it should not be part of the tomahawk project I agree, no relation with Tomahawk. a different idea would be a small myfaces-incubator for new project-ideas (esp. for gsoc projects). Makes more sense to me than Tomahawk. I think (almost) everyone is in favor of moving the project to somewhere else, I am also ok with it. Important thing for the project is having the ability for releases and the jars are deployed to maven repo. Cheers, Ali On Sat, Oct 22, 2011 at 11:05 AM, Mark Struberg strub...@yahoo.de wrote: including our very own little 'attic' :) Actually the big difference between the incubator and a mf subproject would be the IP clearance. We really need to do this upfront before importing. But actually I like this much more than having projects developed outside and only later brought into our SVN - because this causes lots of paperwork (gas grants and a IP clearance review is mandatory). Thus a +1 LieGrue, strub From: Gerhard Petracek gerhard.petra...@gmail.com To: MyFaces Development dev@myfaces.apache.org Sent: Saturday, October 22, 2011 10:58 AM Subject: Re: [html5] alpha release for myfaces html5 a different idea would be a small myfaces-incubator for new project-ideas (esp. for gsoc projects). we can release parts easily and drop them if we see that something doesn't work for our community. if an idea works for the community, we can discuss the correct place for it. we might see new gsoc projects (related to myfaces) every year. imo it's the wrong approach to just add them as new sub-project and we don't have the resources/community to maintain them. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/10/22 Bernd Bohmann bernd.bohm...@atanion.com Ha, I don't think we should wait for the jsf-eg. Hey guys they are asking for a alpha release. In my opinion as long this lib is html5 only it should not be part of the tomahawk project. I don't see any problems in releasing an alpha release. But before a beta we should decide own extension or tomahawk. Regards Bernd On Sat, Oct 22, 2011 at 9:31 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: it's planned that jsf2.2 will get some sort of html5 support. imo we should work together with the jsf-eg to ensure that we won't promote incompatible components. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/10/22 Mark Struberg strub...@yahoo.de +1 for moving it to tomahawk.
Re: [html5] alpha release for myfaces html5
hi mike, i agree with you and that's the reason why i didn't suggest the asf-incubator. imo we just need a quick community check (esp. for gsoc projects) because the overall community is pretty clear. all of our gsoc projects which might become a sub-project started with one student and we never saw other community members working on them actively (after gsoc) and the activities of all students decreased (a lot) after gsoc. actually we already changed our approach. before starting codi we made such a community check. and yes - in the past we missed to do that with some other sub-projects - but we learned from it. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Mike Kienenberger mkien...@gmail.com: I guess the question is what are you (all) trying to accomplish? If we have active committers who want to create an html5 subproject, it seems like our policy thus far is to create it. If we only have a code-dump, it should go through the incubator -- we have done this with other things which are now myfaces subprojects. If enough of the incubated project members are myfaces committers, then it would likely become a myfaces subproject. If there is no overlap, it would have to find its own place. Working out how much is enough and training up non-myfaces-committers would be the task of incubation. If the goal is to change our policies for new subprojects, then I don't see that incubation or apache labs is really relevant -- we're only talking about our own internal organization. And if we're changing our policies, I would hope that whatever we come up with applies to all existing projects as well as new projects. Or, in other words, we shouldn't be treating the html5 subproject any differently than we do anything else. Sandbox was a good start, but we've been having issues with getting things out of sandbox for several years now. I suspect this is why the trend recently has been to skip the sandbox and dive right in with a new subproject. While my personal preference would have been to reform the sandbox, I wasn't really doing any of the work. The folks doing the work have been making the subprojects idea succeed, so from a meritocracy point of view, I'd say that's the future, until something else better comes along. Maybe we're now at the point where some of us do want to see if we can come up with something better. Like I said, I personally think our explosion of subprojects is disorganized and confusing. But if that's our goal, let's say so, and apply it to everything. In the meantime, my opinion is that if we have html5 committers, we allow the html5 committers to have a subproject and move forward with a release. Regards, Mike On Wed, Nov 2, 2011 at 4:13 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: @matthias: apache labs are only for prototyping and the next step is e.g. the incubator for building a community (see [1]). regards, gerhard [1] http://labs.apache.org/bylaws.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Matthias Wessendorf mat...@apache.org: that's stupid :-) Personal releases are IMO possible (e.g. deployment to p.a.o/~asf-id) -M On Wed, Nov 2, 2011 at 6:35 PM, Ali Ok al...@aliok.com.tr wrote: One important point is labs projects are not allowed to make releases. Sent from Android On Nov 2, 2011 1:22 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: see [1] - esp.: Apache Labs are the place where ASF committers can work on innovative, blue-sky and off-the-wall ideas, without having to worry about fitting in an existing project bylaw or building a community around it... we already know that it works and it's just about a community check - imo labs doesn't fit and the alternative would be the incubator itself. regards, gerhard [1] http://labs.apache.org/bylaws.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Matthias Wessendorf mat...@apache.org: I don't get why not just having a simple alpha release ? Does not hurt... Or... move the entire thing to Apache Labs... for future experiments ?! -M On Tue, Nov 1, 2011 at 12:03 AM, Ali Ok al...@aliok.com.tr wrote: Hi, So do you think myfaces/incubator/html5 is a good place? Greetings, Ali On Sat, Oct 22, 2011 at 1:37 PM, Ali Ok al...@aliok.com.tr wrote: Hi, In my opinion as long this lib is html5 only it should not be part of the tomahawk project I agree, no relation with Tomahawk. a different idea would be a small myfaces-incubator for new project-ideas (esp. for gsoc projects). Makes more sense to me than
Re: [html5] alpha release for myfaces html5
hi matthias, perfect for new GSoC projects, IMO agreed - if the student is a committer (see [1]). however, we would have the same issue afterwards. with codi we started with a community check before adding btw. releasing a new sub-project and imo we have to continue with this approach. regards, gerhard [1] http://labs.apache.org/bylaws.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Matthias Wessendorf mat...@apache.org: On Wed, Nov 2, 2011 at 9:13 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: @matthias: apache labs are only for prototyping and the next step is e.g. the incubator for building a community (see [1]). perfect for new GSoC projects, IMO However, generally Apache Labs is (unfortunately) pretty limited (not sure I why would actually do stuff there (instead of at github etc)) -M regards, gerhard [1] http://labs.apache.org/bylaws.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Matthias Wessendorf mat...@apache.org: that's stupid :-) Personal releases are IMO possible (e.g. deployment to p.a.o/~asf-id) -M On Wed, Nov 2, 2011 at 6:35 PM, Ali Ok al...@aliok.com.tr wrote: One important point is labs projects are not allowed to make releases. Sent from Android On Nov 2, 2011 1:22 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: see [1] - esp.: Apache Labs are the place where ASF committers can work on innovative, blue-sky and off-the-wall ideas, without having to worry about fitting in an existing project bylaw or building a community around it... we already know that it works and it's just about a community check - imo labs doesn't fit and the alternative would be the incubator itself. regards, gerhard [1] http://labs.apache.org/bylaws.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Matthias Wessendorf mat...@apache.org: I don't get why not just having a simple alpha release ? Does not hurt... Or... move the entire thing to Apache Labs... for future experiments ?! -M On Tue, Nov 1, 2011 at 12:03 AM, Ali Ok al...@aliok.com.tr wrote: Hi, So do you think myfaces/incubator/html5 is a good place? Greetings, Ali On Sat, Oct 22, 2011 at 1:37 PM, Ali Ok al...@aliok.com.tr wrote: Hi, In my opinion as long this lib is html5 only it should not be part of the tomahawk project I agree, no relation with Tomahawk. a different idea would be a small myfaces-incubator for new project-ideas (esp. for gsoc projects). Makes more sense to me than Tomahawk. I think (almost) everyone is in favor of moving the project to somewhere else, I am also ok with it. Important thing for the project is having the ability for releases and the jars are deployed to maven repo. Cheers, Ali On Sat, Oct 22, 2011 at 11:05 AM, Mark Struberg strub...@yahoo.de wrote: including our very own little 'attic' :) Actually the big difference between the incubator and a mf subproject would be the IP clearance. We really need to do this upfront before importing. But actually I like this much more than having projects developed outside and only later brought into our SVN - because this causes lots of paperwork (gas grants and a IP clearance review is mandatory). Thus a +1 LieGrue, strub From: Gerhard Petracek gerhard.petra...@gmail.com To: MyFaces Development dev@myfaces.apache.org Sent: Saturday, October 22, 2011 10:58 AM Subject: Re: [html5] alpha release for myfaces html5 a different idea would be a small myfaces-incubator for new project-ideas (esp. for gsoc projects). we can release parts easily and drop them if we see that something doesn't work for our community. if an idea works for the community, we can discuss the correct place for it. we might see new gsoc projects (related to myfaces) every year. imo it's the wrong approach to just add them as new sub-project and we don't have the resources/community to maintain them. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/10/22 Bernd Bohmann bernd.bohm...@atanion.com Ha, I don't think we should wait for the jsf-eg. Hey guys they are asking for a alpha release. In my opinion as long this lib is html5 only it should not be part of the tomahawk project. I don't see any problems in releasing an alpha release. But before a beta we should decide own extension or tomahawk. Regards Bernd
Re: [html5] alpha release for myfaces html5
Well, if that's the case, I don't think we need to make this so complicated. If you are an committer for MyFaces, and you are interested in maintaining the html5 subproject, speak up! If no one speaks up, then we don't have a reason to add it to MyFaces. If someone does, then let's move on and create a subproject. :-) I don't think it was a bad idea to suggest it go into Tomahawk or Sandbox, but if the folks maintaining it don't think that's the best solution, I say let them have a standard sub-project like we've done with everything else. That mode of development is working, and it's a good fit with those who do the work make the decisions On Wed, Nov 2, 2011 at 6:15 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi mike, i agree with you and that's the reason why i didn't suggest the asf-incubator. imo we just need a quick community check (esp. for gsoc projects) because the overall community is pretty clear. all of our gsoc projects which might become a sub-project started with one student and we never saw other community members working on them actively (after gsoc) and the activities of all students decreased (a lot) after gsoc. actually we already changed our approach. before starting codi we made such a community check. and yes - in the past we missed to do that with some other sub-projects - but we learned from it. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Mike Kienenberger mkien...@gmail.com: I guess the question is what are you (all) trying to accomplish? If we have active committers who want to create an html5 subproject, it seems like our policy thus far is to create it. If we only have a code-dump, it should go through the incubator -- we have done this with other things which are now myfaces subprojects. If enough of the incubated project members are myfaces committers, then it would likely become a myfaces subproject. If there is no overlap, it would have to find its own place. Working out how much is enough and training up non-myfaces-committers would be the task of incubation. If the goal is to change our policies for new subprojects, then I don't see that incubation or apache labs is really relevant -- we're only talking about our own internal organization. And if we're changing our policies, I would hope that whatever we come up with applies to all existing projects as well as new projects. Or, in other words, we shouldn't be treating the html5 subproject any differently than we do anything else. Sandbox was a good start, but we've been having issues with getting things out of sandbox for several years now. I suspect this is why the trend recently has been to skip the sandbox and dive right in with a new subproject. While my personal preference would have been to reform the sandbox, I wasn't really doing any of the work. The folks doing the work have been making the subprojects idea succeed, so from a meritocracy point of view, I'd say that's the future, until something else better comes along. Maybe we're now at the point where some of us do want to see if we can come up with something better. Like I said, I personally think our explosion of subprojects is disorganized and confusing. But if that's our goal, let's say so, and apply it to everything. In the meantime, my opinion is that if we have html5 committers, we allow the html5 committers to have a subproject and move forward with a release. Regards, Mike On Wed, Nov 2, 2011 at 4:13 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: @matthias: apache labs are only for prototyping and the next step is e.g. the incubator for building a community (see [1]). regards, gerhard [1] http://labs.apache.org/bylaws.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/11/2 Matthias Wessendorf mat...@apache.org: that's stupid :-) Personal releases are IMO possible (e.g. deployment to p.a.o/~asf-id) -M On Wed, Nov 2, 2011 at 6:35 PM, Ali Ok al...@aliok.com.tr wrote: One important point is labs projects are not allowed to make releases. Sent from Android On Nov 2, 2011 1:22 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: see [1] - esp.: Apache Labs are the place where ASF committers can work on innovative, blue-sky and off-the-wall ideas, without having to worry about fitting in an existing project bylaw or building a community around it... we already know that it works and it's just about a community check - imo labs doesn't fit and the alternative would be the incubator itself. regards, gerhard [1] http://labs.apache.org/bylaws.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and
