I gave that a shot too, Vamsi. It didn't work either and after poking around a bit I figured out what is going on but not why. I took a close look at the maven output and found that despite the fact that there were actually changes in the files it was trying to compile, it was indicating that there were none and just went ahead and built the jars using the previously compiled classes. Because of this, none of my changes were making it into the jar. I fixed it by deleting every class file in the directory I had made changes in, thereby forcing it to compile the classes. What I don't understand though is why it would work for a while and then all of the sudden decide that any new changes made don't actually count as changes. Am I missing a step in the build process? Should I be removing the class files before building each time? Thanks for all the help!
Jason On 12/5/06, Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
May be there are some jars in the repo that are being used at assembly time instead of the jars created when you build javamail. Why don't you remove the corresponding jars from the repo and build javamail afresh and then G. --vamsi On 12/5/06, Jason Warner <[EMAIL PROTECTED]> wrote: > > That is a thought I had and I just checked again to confirm that I was > editing the right files and that they were getting saved. I probably should > have mentioned that it did work for a while, which I thought was odd. It > reached a certain point though when the changes stopped taking effect after > compiling. > > On 12/5/06, David Jencks < [EMAIL PROTECTED]> wrote: > > > > > > On Dec 5, 2006, at 12:07 AM, Jason Warner wrote: > > > > > Hey all, > > > > > > In working with the javamail code I've come across a strange > > > issue. It might not be for javamail only, but this is where I am > > > working with the code. I am finding that after I make changes to > > > the code in eclipse and then save, when I run mvn in the javamail/ > > > trunk directory none of my changes seem to be picked up. When I > > > go to run javamail after building, nothing has changed. I have > > > done things that should result in an obvious change such as > > > changing a println statement that is definitely being printed out > > > or changing the functionality of the code such that it should > > > undoubtedly do the change I made but to no avail. Is there > > > something wrong with my build/test process that's resulting in > > > this? I've done an mvn clean on all applicable directories just in > > > case, but that had no effect either. Any suggestions? > > > > cat <file you think you modifed> will tell you pretty quickly if > > eclipse actually saved your changes where you think it did. It > > sounds to me as if eclipse is working on different files than maven, > > or is not saving anything. > > > > thanks > > david jencks > > > > > > > > Jason > > > > >
