We are starting a Wicket project, we use JDK 1.4 because our old software can't run on 1.5.
It's a problem, to move to 1.5, but we will eventually do it. But will take a few years. So I vote for waiting with Java 1.5 until Wicket version 3.0. On 2/14/06, wang lei <[EMAIL PROTECTED]> wrote: > Here is my opinions: > > >> - should the post 1.2 version of Wicket involve both changes? > Absolutely not. > I support the constructor change ,because it force the programmer to do in a > right way. > I don't want wicket support JDK1.5 soon. > I know generics can bring many benefits.But there is a long time before most > of us move to JDK1.5. > Some projects from my clients are stilling run on JDK1.4 even JDK1.3.One > year ,at least, is necessary for waiting. > My clients would just move to JDK1.4 easily,because they need to pay a lot > of money and not sure the old software can move to the new JDK easily. > > >>- should we make different releases for either change, and thus > postponing 1.5 to Wicket 3? > No, one version is enough. Wicket2 or wicket3 are not important. > I think if you move to JDK1.5 too soon.You will lose many users.It's not > good for wicket. > Wicket still has a long way to go. > > > >>- how many of you s till require for current or future projects to run on > JDK 1.4? > In fact,this question is suitable.Most time,the clients choose the > platform,instead of us. > Many clients are running different jdk, I can't predict. But for you,i would > prefer JDK1.4. > > >> - how many would object to having a retroweaver build of a JDK 5 Wicket, > which enables you to run 1.5 code on a 1.4 JRE? > I never try to do that. > > ________________________________ > 无限容量雅虎相册，原图等大下载，超快速度，赶快抢注！ > >
