On Mon, 2007-04-02 at 15:16 +0200, Alon Bar-Lev wrote: > On 4/2/07, Vlastimil Babka wrote: > > > When will we be able to use jdk-1.5 only system? > > > > When > > a) everything is migrated to gen-2 > > b) everything can build with 1.5(+) (even some gen-2 packages can't...) > > Oh... This is what I know... > Just thought you have some kind of time-line, There is no time line, we have discussed it a bit. We might bring it up at our next meeting. > since there should be a > small number of generation-1 packages now. There is not http://dev.gentoo.org/~nelchael/java-generation-2/not-migrated-current http://dev.gentoo.org/~betelgeuse/unported.txt > Since I didn't like what you have done... We discussed this long > ago... I like only one jdk to be installed on my system, created patch > for every one which does not work... Thanks for submitting these patches. I assume they are just ebuild patches because if it's more than that. Submissions of patches would surely be useful. > But then you came with the > generation-2 build which forces 1.4 to be installed, so I faked 1.5 to > be generation-1 and continue to have one jdk on my system. Great, where's the patch for Eclipse? Since it REQUIRES 1.4 to be present to be built. At least that was the last state of the sources from upstream. > But nevermind... All packages listed above are working with 1.5 so > please convert them to generation-2. Might want to look to see if stabilization requests have been filed. Or if the gen 2 versions have been in tree long enough to be stabilized. Because your requesting what has been done already, and there is a process to migrating packages. > I think you should switch into the top-bottom tree scanning selecting > popular packages like tomcat Tomcat is one of our best maintained Java apps, if I can toot my own horn for a bit. Also FYI, your rush to 1.5 causes problems. For example that patch you provided dropping deps for Tomcat 5.5.x when using 1.5, via java5 USE flag. Caused several bugs to pop up, a few deps were over aggressively dropped and I added them back. There is still one remaining problem with catalina.jar and the manager app when deploying, restarting, and undeploying an app. A user wasted considerable time tracking that down. So we are not looking to introduce breakage, bugs, or problems like that to our stable tree. By rushing to get everything compiling with, and using 1.5. Although it is a goal. Others teams might feel that is acceptable, but we on the Java team and with our Java herd of packages have pretty high QA standards. > and make sure the whole stable tree of > dependencies is generation-2 compliant. Thank you for your input. We have been desperately working on this. Schedule meetings so we can all stay focused, goal oriented, and be working as a team. However some of us (like me) have lost considerable time due to breakage else where in the tree. If time was not lost like that, then we might be further along. We have been recruiting for some time, and bringing on new people as fast as we can reasonably. But we are all volunteers, and can only do as much as we can in our free time. If you are unhappy with the state of things, I would suggest helping out in the process. Also doing a bit of home work on said packages or the state of things. Before commenting in a negative manner towards those busting there rears to maintain 400+ java applications in the Java herd alone. Much less in other parts of the tree. Math alone breaks down to like ~40 packages per dev, and with my efforts on Tomcat and etc. I have little time for gen 2 migration or maintenance of other packages. All the while trying to increase our package offerings by packaging stuff like glassfish. Much less virtuals so users can choose implementations of things like jaf, javamail, jmx, servlet-api, and etc. -- William L. Thomson Jr. Gentoo/Java