> In v2 there was a whole mechanism for installing and configuring
> addons. Obviously none of that is supported in v3. (Right?)
>
> If we start a v2 domain with v3, and there's anything in the addons
> directory, shouldn't we produce a warning?
Tom sent that info to me and I've created a little niche to dump
upgrade concerns here:
http://wiki.glassfish.java.net/Wiki.jsp?page=V3.1UpgradeDashboard
I don't think there's any code to handle what you're talking about
now. Modules mark themselves as interested in upgrading something and
then upgrade their part of the domain config. But there's no
"catchall" chunk of code for handling all the parts that no one uses
(right?).
I think I should add some class to pick up these things, warn users,
remove config info if we want it removed, etc. It's not terribly
elegant, but it's better than nothing. I hope. Let me know what you
think. There are tasks like this about which people ask me "can't the
upgrade tool just do it?" The answer is no (*). So having something in
the core module to handle generic upgrade tasks might be the answer.
(*) Well, yeah, it can, but that doesn't do any good in the cases when
it's not run.
Cheers,
Bobby