https://bz.apache.org/bugzilla/show_bug.cgi?id=58617
--- Comment #11 from Uwe Schindler (ASF) <[email protected]> --- Hi, > @POI dependency in the maven POM: > I would preferably skip it, because any kind of version-circular-reference > (e.g. "RELEASE") would cause problems in the user packaging. The problem would be that you depend on a outdated "older version" of POI indirectly. One solution would be to have a ooxml "parent jar" with that class which is a dependency of every ooxml package. Not sure if it is worth the trouble. Another solution is (I am not sure) to add it as "provided" dependency in Maven central (without version!?). But this would not really help users that want to use the ooxml jars alone. > Would there be a problem for OSGI packaging? (I don't much about osgi, only > that's it picky in such conditions...) OSGI is very picky, but I have no idea... I think it already complains if multiple JAR files use the same package name. In Lucene we refused to create OSGI packages, we dropped support for that completely (especially as OSGI does not work with Java's SPI). -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
