> Well, at the moment, I downgraded the dependency in there (tika 0.8 -> > tika 0.7), and this seems to eliminate the problem so I kow it's either > about 0.8 (plus transitive dependencies) being way larger or tika 0.8 > being somehow broken. However, at the moment, given the error messages > seen in there, I failed to even see which jar might cause this kind of > trouble. Is there any way of how to get more qualified output on that?
Did you try "mvn -e ..." or "mvn -X ..." to get more debugging information during the build? I doubt you would get anything that would help in this specific case, though. If you really want to debug it, you probably need to trace it in an IDE or add some additional logging in AbstractZipArchiver.zipFile(). > seems to come with some more dependencies / features, think it's about > to be somewhere in between 20 and 30 megs... No, I'm talking about assemblies that are hundreds of megs or multiple gigs. There should not be any troubles building assemblies that are merely tens of megs. I suspect there is something wrong with the Tika 0.8 jar or one of its dependencies. Did you ask the Tika people about any of this? Perhaps one of their users has some experiences to share. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
