| 
     
      
      
      From: Lukas T. <lth...@ap...> - 2007-12-17 09:33:19
      
     
   | 
Any reason for not trying Maven 1.1 final? :) There was a classloader bug in beta-2 ( http://jira.codehaus.org/browse/MAVEN-1690 ) which is supposed to be fixed. That would be my first guess. If not we'd need more details about the problem. (And probably the main maven user list is a better place to ask...) HTH, -Lukas Jack wrote: > Hi, > > I have a problem / question. > > In our larger projects we get a lot of "missing classes" messages even > though these classes are either in the project themselves or included > in the project. > > We are running Maven 1.1-beta-2, findbugs-plugin 1.4 and have both > JDK 1.4 and JDK 1.5 projects. > > I have run findbugs with -Dfindbugs.debug.enable=true and the classes > that it says are missing are definitely _not_ specified in the > auxClasspath. > > Is there a solution to this problem, or a way to add to the auxClasspath? > > Cheers > Jack... > > The claim "natural" is not synonymous with safe. > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services > for just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Maven-plugins-user mailing list > Mav...@li... > https://lists.sourceforge.net/lists/listinfo/maven-plugins-user >  |