Has anyone else come across the problem with the building and deploying of PAR files from eclipse ?
I've found, to my cost, that you can be working happily with a project and testing it in your local PDK when for no apparent reason the build of the PAR file seems to take on a life of it's own.
This becomes apparent when changes stop taking effect in the deployed code, e.g. a new Bean setter/getter is unavailable but you can see it in the code
The compile in eclipse works ok and you can see the correct source in the PDK/Real Portal but the actual PAR file deployed contains old versions of classes.
The only way I've found of sorting the problem out is to copy out the classes to a temp project, delete the original project, create it again and cutting and pasting the classes back in again.
I'd say the problem seems to happen after creating a project from an imported PAR file resource but couldnt swear to it.
Anybody got a answer to this ?