2016-06-29 16:08 GMT+02:00 Dignesh <[email protected]>: > Hi, > I haven't understood the answer. > > 1.Does it mean every jar should have META-INF/MANIFEST.MF ? >
yes was a (now fixed) bug in tomcat > 2.How to exclude the jar from the scanning - Any configuration available ? > easiest is to add the jar prefix (for foo-1.2.3.jar add "foo-") in conf/exclusions.list file should look like: default-list foo- bar- #... > 3.What will be the impact if I exclude the jar from scanning? > > If it contains EE components (EJB, CDI beans, @WebXXX...) it will be ignored. The container will be able to load the classes when needed but will ignore them at processing time. If it is your jar just fix your build tool to generate this file (mvn, gradle, ant should do it by default), if not your jar and just a utility jar exclude it. Last note: as mentionned upgrading is an alternative now since 7.0.1 is released > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Server-not-getting-started-tp4679116p4679119.html > Sent from the TomEE Dev mailing list archive at Nabble.com. >
