We CAN... But the compile time requirements will be different. And the
real concern I have is that this commons project is a slave to another
project which means we are at the mercy of the JSF api's. If they
change, implementations need to change and it may not always be possible
to have both classes exist in the classpath at any given time.
Unfortunately.
The approach we originally took in Trinidad was to commit changes to the
1.1 branch and then upmerge them to the 1.2 branch. The problem is that
this proved cumbersome and error prone so we've taken recently to a
dual-trunk type system. The real issue is this. We are all open source
developers. Our time, as a result, is limited. IMO maintaining two
branches hampers new development and innovation. I know it has in
Trinidad to a large extent because nobody likes making patches to dual
code lines.
Scott
Glauco P. Gomes wrote:
Scott O'Bryan escreveu:
If 1.1 is a must then I don't see any way around having 2 trunks.
WDYT about use different pakages for different versions (incompatible
stuff only) like Spring did for Hibernate version 2 and 3?
org.springframework.orm.hibernate => for Hibernate 2.x
and
org.springframework.orm.hibernate3 => for Hibernate 3.x
Glauco P. Gomes
