Dear David, I finally found a configuration that worked for our environment with the released version (3.1.1). Basically we allow only deployments of *easycredit* artefacts and the current target directory. Third party artefacts like ant, jexcel, jaxb-jxc are not scanned anymore.
openejb.deployments.classpath.include=.*(easycredit|target).* openejb.deployments.classpath.filter.descriptors=true I would like to test the current fixes on 3.1.2-SNAPSHOT, could you give me a hint where to download the binaries (maven repo). Then I could give you feedback on it. regards, andreas David Blevins wrote: > > Andreas, > > Figured out the "issue" with the include/exclude feature. I use issue > in quotes as it works fine, I simply forgot some of the nuances with > it. Definitely need to add them to the documentation. > > Long story short, in 3.0 through 3.1.x the include/exclude properties > will filter out modules that have descriptors if you set this flag: > > openejb.deployments.classpath.filter.descriptors=true > > Note that the default include/exclude setting does not allow anything > through, so you will want to open it up a bit. The current code > filters the classpath using the exclude setting then the filters the > resulting list using the includes. So it's exclude then include -- > therefore include cannot include anything that has been excluded via > the exclude setting. > > Working on two features here: > 1. Should be possible to specify the order you want include and > exclude applied. > 2. Really "app client" jars that just have Main-Class specified and > have no META-INF/application-client.xml should be treated as > "annotated" jars and should be ignored with the default settings. > > -David > -- View this message in context: http://www.nabble.com/openejb-tries-to-start-org.apache.tools.ant.Main-tp24623745p25118025.html Sent from the OpenEJB User mailing list archive at Nabble.com.
