#3511 - every hotswap is a "schema change"

Is it me - or is build #3511 reporting every hotswap operation of a
schema change?

I deploy, start debugging, change the contents of a single string
assignment, compile, then see hotswap reload about 20 classes which
hadn't been touched and complain about a schema change...

Previous build (or at least the one before yesterdays) was nicely
hotswapping a single class for me...

Am I the only one? This is debugging remotely a JBoss 3.2.6 install...

1 comment
Comment actions Permalink

It can be related with *.class file timstamps with are "in the future" from the current computer time.

Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
"Develop with pleasure!"



Please sign in to leave a comment.