Just to explain the current situation:
trunk *can't* move to M7 at this time because of API changes in eclipse requires
non-trivial changes in Hibernate
and having to wait for that to be verified we'll most likely be looking at even more
delay of a M1 release.
Thus trunk stays on M6 while Nick is making a jbosstools 3.3.0.M1 site available which
will also contain the
proper M6 dependencies so the installation process for users will not be affected by
trunks future more to M7.
The update site for JBoss Tools 3.3.0.M1 will be available shortly for basic testing(*)
and once that have been
done we'll push it - thus the important part is getting the whatsnew ready.
If everything goes well, we'll be able to open up trunk for M7 within the next 24-48
* testing will have to be just the basic old-school dev testing since our primary QE is
busy with another release.
On May 9, 2011, at 22:03, Max Rydahl Andersen wrote:
Seems like a few components have trivial compile errors but hibernate
got 25 non-easy fixable issues ;(
so the idea about moving to M7 quickly is stalled.
On May 9, 2011, at 20:05, Max Rydahl Andersen wrote:
> 3.3.0.M1 never really materialized last week and Eclipse M7 is already out and i.e.
maven tooling is not possibly to get to run clean on M6 anyway.
> so we are right now discussing moving to Eclipse M7 for trunk and cut a M release out
on that instead.
> Please let me know ASAP if you see any problems with M7 on your component?