+1 On Thu, Jun 19, 2008 at 5:39 PM, Leonardo Uribe <[EMAIL PROTECTED]> wrote:
> Hi > > After several discussions about how myfaces-commons should be, there are > strong reasons to believe that this project > should have some layout that allow myfaces 1.1 projects to use it. > > There was a vote about had 1.1 stuff on a different branch and the trunk > be 1.2. This vote should be honored, but the times change, and with > the enhancements done in the last time this issue became a problem. > > One example of the problem present right now is the class > ExternalContextUtils of myfaces-commons-utils. This class is > used on tomahawk, but since tomahawk is 1.1 compatible, this should have a > copy of this class inside tomahawk instead a > dependency to myfaces commons. > > There was some comments about differentiate 1.1 and 1.2 code versions with > the maven version number is a bad idea. > > But jsf 2.0 is near.... > > The proposed layout is this: > > myfaces-commons-utils > myfaces-commons-utils12 > myfaces-commons-converters > myfaces-commons-converters12 > myfaces-commons-validator > myfaces-commons-validator12 > > I know this is controversial, but better to know if the people think the > same as before or not. > > Suggestions are welcome > > regards > > Leonardo Uribe >
