|
From: Paul C. <can...@po...> - 2007-10-16 16:53:29
|
Hello Stephane. The jars referenced by your code must in Macker's classpath when it runs. I'm not sure how the maven task sets up Macker's classpath, but apparently this jar is not finding it in there. Does it work for you with Ant? Can you try that as a simple diagnostic? Cheers, Paul On Oct 10, 2007, at 9:11 AM, COUTANT Stephane RD-BIZZ-GRE wrote: > Hi, > > I'm puzzled, your Coding convention example > http://innig.net/macker/example/conventions/src/macker.xml fails on my > small projet. > I have an interface that happens to import the JPA > javax.persistence.EntityExistsException. The exception class > actually is > provided in the classpath. The project does compile. > But when I add macker check to maven compilation phase, i have an > IncompleteClassInfoException, hinting the EntityExistsException file > could not be found in the classpath. > As i run it, i echo the classpath used, i can see the corresponding > persistence-api-1.0.jar is there... > I there any issue regarding exception classes or is it a standard > classpath problem? > > Best regards. > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Macker-user mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/macker-user > > Macker home page: http://innig.net/macker/ > |
