Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: pass (nike.apache.org: domain of mconcini@gmail.com designates
 74.125.92.148 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        b=q2WS+WJPc4oGcPyFQSEz7hQVPOPE0tBqxpqW3mfrnqM16DXO+W5kA9aDVM35UaOo4y
         1clxmQ7o56uO5oifSvR3CPSAd2VyppbsZsoVpILP2kB+qlTlldd0TOYMrG7GsADEh5G1
         +gKXyBX/bZmXbKmCIRGLUo/DqPg3raXGODIgs=
Message-ID: <4A524182.6030703@gmail.com>
Date: Mon, 06 Jul 2009 14:25:06 -0400
From: Michael Concini <mconcini@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: MyFaces Development <dev@myfaces.apache.org>
Subject: [JSF 2.0] which shared source branch for 2.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

What branch of shared should we be using for JSF 2.0 specific changes?  
Looking at the pom for impl, it looks like right now both 1.2.x and 2.0 
builds are using the shared 3.0.6 branch. 

I have some changes that will be ready to check in this week that 
following the current implementation should be in the shared sources.  
Specifically I'm referring to the RendererBase classes and ELTagBase 
classes for the new OutcomeTarget components (h:link and h:button). 

If we wanted to maintain the same shared source level for both 1.2 and 
2.0, I guess I could just put the base classes in the impl somewhere 
instead, but that doesn't seem ideal since it wouldn't follow the same 
pattern as every other component.

Any advice/instruction here would be appreciated. 

Thanks,
Mike