At this point all of my project are based on JSF 1.1, primarily because
the infrastructure to support JSF 1.2 is not available on the deployment
platforms.
Paul Spencer
Adam Winer wrote:
"Why not": how many users are ready to make the jump to
JSF 1.2? Many of our users, Tomahawk, Trinidad, Tobago, are
on JSP 2.0 or earlier.
It'd make my life way easier if the Trinidad trunk were 1.2,
definitely, I just doubt that would hold true for the users.
Just for starters, what about the committers? How many
of us can stick to 1.2?
-- Adam
On 7/20/07, Cagatay Civici <[EMAIL PROTECTED]> wrote:
About subprojects, I think the case is same for them, if we make 1.2 the
trunk for api, why not set 1.2 branches of subprojects as trunks too?
Also
after doing it, we may need to reconfigure current and current12 too.
On 7/19/07, Paul Spencer <[EMAIL PROTECTED]> wrote:
> Assuming MyFaces 1.1.7 is released so the SVN configuration in the POM
> of next version of MyFaces will be correct. Otherwise people,
including
> Continuum, who are using 1.1.7-SNAPSHOT from the repository will be in
> for a very big surprise.
>
> Qualified +1 otherwise -0 for the above reason
>
> Although I missed the discussion, my preference would be for a MyFaces
> 1.1 and 1.2 trunk/branch since both are active products.
>
> Paul Spencer
>
> Matthias Wessendorf wrote:
> > Hi,
> >
> > this is a vote for making the JSF 1.2 efforts by our group to become
> > the current trunk.
> > Currently the JSF 1.2-work lives on a branch ( 1.2.1-SNAPSHOT is the
> > current version).
> >
> > Please cast your vote
> >
> > ------------------------------------------------
> > [ ] +1 for moving the myfaces 1.2.x to trunk
> > [ ] +0
> > [ ] -1 and why..............
> > ------------------------------------------------
> >
> > -M
> >
>
>
