I am experiencing an issue where sometimes my builds work and sometimes they do not.
One thing I am seeing is that if I introduce a compile error into my code, and then launch my maven build, the build does fail, after about 15 seconds, but the "problems" tab in eclipse does not list my error. If I right click my project in the package explorer and select "build project" the compile immediately shows up in the problem tab in < 1 second. Of a bigger worry to me is that if I run the project, it does not do a build first, so If I run my project and see it is working, and then I fire off my install tool to package up my deployment area, and forget to fire off the build manually first, the install is not the latest code as the build did not occur. Is there any way to make "run" do a build first, but only if any source code has changed? Of the biggest concern though, is that sometimes (but not always) if I do a build, the code in the generated jar does not seem to get updated. I know this is not enough information to go on, I am just asking first if anyone has experienced anything like this before? I will start digging more tomorrow to see if I can get to the cause. Thoughts? +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Please consider the environment before printing this email WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender by return email and delete this message and any attachments. The views expressed in this email are those of the sender and do not necessarily reflect the official views of SirTrack. see http://www.sirtrack.com +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
