2008/9/19 Sahoo <[EMAIL PROTECTED]> > Peter, > > You are right. I wrote a small dtrace[1] script to monitor open system > calls for that file. I attached it to a build m/c and after around 150 > builds, once it occurred. Every time open system call was made with that > file handle, I print the java stack. The output of dtrace is attached here > with. That file got opened three times. As the stack suggests, first by > maven-compiler-plugin, then by maven-bundle-plugin and finally by > maven-jar-plugin. So, it is the compiler-plugin that is responsible for > creating that servlet class in jacc target dir. Next task is to find out why > it does so. I don't understand why it does so. >
the only thing I can think of at the moment is that javac will generate classfiles for any classes that it has the sources for but no binaries so possibly when this happens the servlet classes are missing from the build classpath, but the sources are there instead - however I've no idea how this could happen, especially as it is so intermittent! as a side-note this is one area where bnd is better than jar, because bnd uses the given instructions to pull the bundle together rather than zipping up everything in the directory - so even if additional cruft did manage to get into target/classes it shouldn't affect bnd... > Thanks, > Sahoo > -- Cheers, Stuart
