setting exclude unlisted = true should maybe help. That said tomee doesnt read persistence.xml so can be hibernate in your setup which needs the persistence.xml.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-05-17 14:59 GMT+02:00 Gregory Orciuch <g.orci...@gmail.com>: > Thanks I try building and using snapshot. > > But small question, how I can kinda blacklist that particular > persistence.xml ? > I thought that if I create PU from scratch in ApplicationComposer then any > other persistence.xml wont be used ?(scanned) > > Check this out: http://hastebin.com/qoruvocaba.avrasm > > So as soon as I dont need that persistence.xml in one of dependent jars > then > I name classes one-by-one so. > Shouldnt that be persistence.xml agnostic? > > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/IllegalArgumentException-on-weird-constructed-URL-tp4678460p4678471.html > Sent from the TomEE Dev mailing list archive at Nabble.com. >
