Hi Everyone, I found the root of this problem. For some reason the ClassPath order changed in Maven 2.0.7 and Maven 2.0.8 and it exposed that an older version of the servlet-api code was being pulled as a dependency. In 2.0.7 and 2.0.8, the older version shows up first and causes the failure. It took me a little while to find this because the jars were not named the same.
Thanks, David On Tue, Feb 5, 2008 at 10:44 AM, Wayne Fay <[EMAIL PROTECTED]> wrote: > Create a sample project jar that demonstrates the problem and attach > it to a new JIRA issue. > > Wayne > > On 2/5/08, David Williams <[EMAIL PROTECTED]> wrote: > > Hi Everyone, > > > > I have seen this twice now so I thought I would throw this out and see > if > > anyone else had seen this problem. We have two projects that compile > fine > > with Maven 2.0.6 that does not with Maven 2.0.7 nor Maven 2.0.8. In > both > > cases it is a cannot find symbol error. > > > > In the first instance, the problem was the *tomcat/jsp-api/5.0.18/jsp- > > api-5.0.18.jar* and the *tomcat/servlet-api/5.0.18/servlet- > api-5.0.18.jar*. > > > > > > The second instance is with the * > > org/apache/myfaces/core/myfaces-api/1.2.2/myfaces-api-1.2.2.jar *and* ** > > org/apache/myfaces/core/myfaces-impl/1.2.2/myfaces-impl-1.2.2.jar > > > > *I checked the the correct version of the jar is on the classpath and > again > > everything works fine with Maven 2.0.6. Has anyone seen anything like > this? > > > > Thanks for your help, > > > > David > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
