You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Scott O'Bryan <da...@gmail.com> on 2012/03/25 18:17:35 UTC
Move Trinidad Trunk to JSF 2.1
Hey all,
Currently the Trinidad Trunk is set to JSF 2.0. There have been a
number of blocker bugs recently (namely some issues with the
ViewDeclarationLanguages and composite components) which have generated
some blocking bugs. These problems were cause by additional methods in
the ViewDeclarationLanguage syntax which we have to wrap for some of the
functionality in Trinidad to be complete.
At this time I propose the following:
1. Copy the current Trinidad Trunk to be branches/trinidad-2.0.x
2. Change the version of Trinidad Trunk to be 2.1.0-SNAPSHOT
3. Change the JSF dependency for trunk to be MyFaces 2.1
4. Change the trinidad plugins trunk to be 2.1.0 for consistency.
5. Change both branches/trinidad-2.0.x and trunk to use the new trinidad
plugins snapshot.
I'm hoping everyone will agree to this so that we can fix some of the
blocker issues we've had show up after the the last Trinidad release.
Many of which seem to be JSF 2.1 related.
Please respond to this email with a +1 or a -1 and don't forget to
include any any reasons why you do not wish to support the move.
Thanks,
Scott
Re: Move Trinidad Trunk to JSF 2.1
Posted by Max Starets <ma...@oracle.com>.
+1
On 3/25/2012 12:17 PM, Scott O'Bryan wrote:
> Hey all,
>
> Currently the Trinidad Trunk is set to JSF 2.0. There have been a
> number of blocker bugs recently (namely some issues with the
> ViewDeclarationLanguages and composite components) which have
> generated some blocking bugs. These problems were cause by additional
> methods in the ViewDeclarationLanguage syntax which we have to wrap
> for some of the functionality in Trinidad to be complete.
>
> At this time I propose the following:
>
> 1. Copy the current Trinidad Trunk to be branches/trinidad-2.0.x
> 2. Change the version of Trinidad Trunk to be 2.1.0-SNAPSHOT
> 3. Change the JSF dependency for trunk to be MyFaces 2.1
> 4. Change the trinidad plugins trunk to be 2.1.0 for consistency.
> 5. Change both branches/trinidad-2.0.x and trunk to use the new
> trinidad plugins snapshot.
>
> I'm hoping everyone will agree to this so that we can fix some of the
> blocker issues we've had show up after the the last Trinidad release.
> Many of which seem to be JSF 2.1 related.
>
> Please respond to this email with a +1 or a -1 and don't forget to
> include any any reasons why you do not wish to support the move.
>
> Thanks,
> Scott
Re: Move Trinidad Trunk to JSF 2.1
Posted by Anand Nath <an...@oracle.com>.
+1
On 3/26/2012 8:44 PM, Prakash Udupa wrote:
> +1
>
> On 3/26/2012 9:45 AM, Matt Cooper wrote:
>> +1
>>
>> On Mon, Mar 26, 2012 at 8:42 AM, <gabrielle.crawford@oracle.com
>> <ma...@oracle.com>> wrote:
>>
>> +1
>>
>>
>>
>> On Mar 25, 2012, at 9:17 AM, Scott O'Bryan <darkarena@gmail.com
>> <ma...@gmail.com>> wrote:
>>
>> > Hey all,
>> >
>> > Currently the Trinidad Trunk is set to JSF 2.0. There have
>> been a number of blocker bugs recently (namely some issues with
>> the ViewDeclarationLanguages and composite components) which have
>> generated some blocking bugs. These problems were cause by
>> additional methods in the ViewDeclarationLanguage syntax which we
>> have to wrap for some of the functionality in Trinidad to be
>> complete.
>> >
>> > At this time I propose the following:
>> >
>> > 1. Copy the current Trinidad Trunk to be branches/trinidad-2.0.x
>> > 2. Change the version of Trinidad Trunk to be 2.1.0-SNAPSHOT
>> > 3. Change the JSF dependency for trunk to be MyFaces 2.1
>> > 4. Change the trinidad plugins trunk to be 2.1.0 for consistency.
>> > 5. Change both branches/trinidad-2.0.x and trunk to use the new
>> trinidad plugins snapshot.
>> >
>> > I'm hoping everyone will agree to this so that we can fix some
>> of the blocker issues we've had show up after the the last
>> Trinidad release. Many of which seem to be JSF 2.1 related.
>> >
>> > Please respond to this email with a +1 or a -1 and don't forget
>> to include any any reasons why you do not wish to support the move.
>> >
>> > Thanks,
>> > Scott
>>
>>
Re: Move Trinidad Trunk to JSF 2.1
Posted by Scott O'Bryan <da...@gmail.com>.
Cool, it looks like we have a lazy consensus on this item. In the past
I think that's been enough to simply move code around. Unless anyone
raises an objection, I'll probably plan on doing this tomorrow.
Thanks for all your input. Now we can fix those pesky
CompositeComponent issues for the 2.1 folks.. ;)
Scott
On Tue 27 Mar 2012 10:26:21 AM MDT, Jeanne Waldman wrote:
> +1
>
> Prakash Udupa wrote, On 3/26/2012 8:14 AM PT:
>> +1
>>
>> On 3/26/2012 9:45 AM, Matt Cooper wrote:
>>> +1
>>>
>>> On Mon, Mar 26, 2012 at 8:42 AM, <gabrielle.crawford@oracle.com
>>> <ma...@oracle.com>> wrote:
>>>
>>> +1
>>>
>>>
>>>
>>> On Mar 25, 2012, at 9:17 AM, Scott O'Bryan <darkarena@gmail.com
>>> <ma...@gmail.com>> wrote:
>>>
>>> > Hey all,
>>> >
>>> > Currently the Trinidad Trunk is set to JSF 2.0. There have
>>> been a number of blocker bugs recently (namely some issues with
>>> the ViewDeclarationLanguages and composite components) which
>>> have generated some blocking bugs. These problems were cause by
>>> additional methods in the ViewDeclarationLanguage syntax which
>>> we have to wrap for some of the functionality in Trinidad to be
>>> complete.
>>> >
>>> > At this time I propose the following:
>>> >
>>> > 1. Copy the current Trinidad Trunk to be branches/trinidad-2.0.x
>>> > 2. Change the version of Trinidad Trunk to be 2.1.0-SNAPSHOT
>>> > 3. Change the JSF dependency for trunk to be MyFaces 2.1
>>> > 4. Change the trinidad plugins trunk to be 2.1.0 for consistency.
>>> > 5. Change both branches/trinidad-2.0.x and trunk to use the
>>> new trinidad plugins snapshot.
>>> >
>>> > I'm hoping everyone will agree to this so that we can fix some
>>> of the blocker issues we've had show up after the the last
>>> Trinidad release. Many of which seem to be JSF 2.1 related.
>>> >
>>> > Please respond to this email with a +1 or a -1 and don't
>>> forget to include any any reasons why you do not wish to support
>>> the move.
>>> >
>>> > Thanks,
>>> > Scott
>>>
>>>
Re: Move Trinidad Trunk to JSF 2.1
Posted by Prakash Udupa <pr...@oracle.com>.
+1
On 3/26/2012 9:45 AM, Matt Cooper wrote:
> +1
>
> On Mon, Mar 26, 2012 at 8:42 AM, <gabrielle.crawford@oracle.com <ma...@oracle.com>> wrote:
>
> +1
>
>
>
> On Mar 25, 2012, at 9:17 AM, Scott O'Bryan <darkarena@gmail.com <ma...@gmail.com>> wrote:
>
> > Hey all,
> >
> > Currently the Trinidad Trunk is set to JSF 2.0. There have been a number of blocker bugs recently (namely some
> issues with the ViewDeclarationLanguages and composite components) which have generated some blocking bugs. These
> problems were cause by additional methods in the ViewDeclarationLanguage syntax which we have to wrap for some of
> the functionality in Trinidad to be complete.
> >
> > At this time I propose the following:
> >
> > 1. Copy the current Trinidad Trunk to be branches/trinidad-2.0.x
> > 2. Change the version of Trinidad Trunk to be 2.1.0-SNAPSHOT
> > 3. Change the JSF dependency for trunk to be MyFaces 2.1
> > 4. Change the trinidad plugins trunk to be 2.1.0 for consistency.
> > 5. Change both branches/trinidad-2.0.x and trunk to use the new trinidad plugins snapshot.
> >
> > I'm hoping everyone will agree to this so that we can fix some of the blocker issues we've had show up after the
> the last Trinidad release. Many of which seem to be JSF 2.1 related.
> >
> > Please respond to this email with a +1 or a -1 and don't forget to include any any reasons why you do not wish
> to support the move.
> >
> > Thanks,
> > Scott
>
>
Re: Move Trinidad Trunk to JSF 2.1
Posted by Matt Cooper <mc...@apache.org>.
+1
On Mon, Mar 26, 2012 at 8:42 AM, <ga...@oracle.com> wrote:
> +1
>
>
>
> On Mar 25, 2012, at 9:17 AM, Scott O'Bryan <da...@gmail.com> wrote:
>
> > Hey all,
> >
> > Currently the Trinidad Trunk is set to JSF 2.0. There have been a
> number of blocker bugs recently (namely some issues with the
> ViewDeclarationLanguages and composite components) which have generated
> some blocking bugs. These problems were cause by additional methods in the
> ViewDeclarationLanguage syntax which we have to wrap for some of the
> functionality in Trinidad to be complete.
> >
> > At this time I propose the following:
> >
> > 1. Copy the current Trinidad Trunk to be branches/trinidad-2.0.x
> > 2. Change the version of Trinidad Trunk to be 2.1.0-SNAPSHOT
> > 3. Change the JSF dependency for trunk to be MyFaces 2.1
> > 4. Change the trinidad plugins trunk to be 2.1.0 for consistency.
> > 5. Change both branches/trinidad-2.0.x and trunk to use the new trinidad
> plugins snapshot.
> >
> > I'm hoping everyone will agree to this so that we can fix some of the
> blocker issues we've had show up after the the last Trinidad release. Many
> of which seem to be JSF 2.1 related.
> >
> > Please respond to this email with a +1 or a -1 and don't forget to
> include any any reasons why you do not wish to support the move.
> >
> > Thanks,
> > Scott
>
Re: Move Trinidad Trunk to JSF 2.1
Posted by ga...@oracle.com.
+1
On Mar 25, 2012, at 9:17 AM, Scott O'Bryan <da...@gmail.com> wrote:
> Hey all,
>
> Currently the Trinidad Trunk is set to JSF 2.0. There have been a number of blocker bugs recently (namely some issues with the ViewDeclarationLanguages and composite components) which have generated some blocking bugs. These problems were cause by additional methods in the ViewDeclarationLanguage syntax which we have to wrap for some of the functionality in Trinidad to be complete.
>
> At this time I propose the following:
>
> 1. Copy the current Trinidad Trunk to be branches/trinidad-2.0.x
> 2. Change the version of Trinidad Trunk to be 2.1.0-SNAPSHOT
> 3. Change the JSF dependency for trunk to be MyFaces 2.1
> 4. Change the trinidad plugins trunk to be 2.1.0 for consistency.
> 5. Change both branches/trinidad-2.0.x and trunk to use the new trinidad plugins snapshot.
>
> I'm hoping everyone will agree to this so that we can fix some of the blocker issues we've had show up after the the last Trinidad release. Many of which seem to be JSF 2.1 related.
>
> Please respond to this email with a +1 or a -1 and don't forget to include any any reasons why you do not wish to support the move.
>
> Thanks,
> Scott