On Mar 21, 2012, at 10:12 PM, Steve Ebersole wrote: > On Wed 21 Mar 2012 09:04:28 AM CDT, Strong Liu wrote: >> m9 doesn't causes the new problem, it just does not fix it. the issue exists >> in m8 as well. > > I dont have build hangs on documentation with m8a…
w/o documentation namespace change, m9 just take more time than i expected, it didn't hang forever, i was wrong yesterday. and I think that's because you're using linux, as said in my first mail in this thread, using m8 to build docs, it takes much longer on mac than linux actually, on my mac, m9 takes almost same time as m8 to build docs ( w/o namespace change) > >> and since the changes (lots of deprecated methods were removed in this m9 >> release) I made will be needed even we wait for CR, and then we have to >> take resource to do this again > > Sure, but most likely CR will introduce the need for even more changes. This > is the problem with constant micro-upgrading. Its the reason I waited so > long to upgrade off m3. i agree with this > >> but anyway, it is your call > > Can the changes you made still be run with my local m8a install? If not, I'd > rather wait for CR1. In which case, I'd say to keep your changes > branched-away, we can use that as the starting point when they do CR1. > no, it doesn't compatible with m8a > If you have the changes to make the manual documentation name-spaced as a > seperate commit, I'd say lets apply that now even. > > -- > st...@hibernate.org > http://hibernate.org _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
