which app server was this? tomcat, jboss, ...? this is a good practice in environments without good change management, where sometimes knowing exactly *which* source version is in prod is impossible or at least very difficult. Of course if there's good change management then you don't need to package source in this manner... :-)
2008/9/30 Robert Mark Bram <[EMAIL PROTECTED]> > > Hi All, > > I have gotten into the habit of creating my jar files with source in > place i.e. my jar files contain .class and .java files in the same > directory tree. > > Recently I encountered a problem with this: after deployment of an ear > file containing my jar file, a JSP threw an error: > > jasper.JasperException tossed:Unable to compile class for ***: Public > class *** must be defined in a file called "***". > > A friend told me to remove the source files, which I did - and the > problem went away. > > So, what is the best practice for packaging source? I know the Apache > libraries provide separate source downloads, but I always thought that > was just to keep file sizes low.. > > Rob > :) > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
