Hi Zac, On 25.07.2025 13:01, Zac Spitzer wrote: > I've noticed with quite a few of the latest commons releases (i.e.lang3, > io,fileupload2), the Import-Package list has grown, including a lot > of java.* packages, which normally are not listed as imports?
The presence of `java.*` is normal. According to BND documentation[1], these appear if: - either OSGi Core R7 or later is used. - or the bundle includes class files targeting Java 11 or later. > While 1.14.0 has > > Import-Package: org.apache.commons.lang3;version="3.18.0",org.apache.com > mons.lang3.function;version="3.18.0",org.apache.commons.lang3.time;vers > ion="3.18.0",java.io,java.lang,java.lang.invoke,java.lang.reflect,java. > net,java.nio,java.nio.charset,java.nio.file,java.text,java.util,java.ut > il.concurrent,java.util.function,java.util.regex,java.util.stream,javax > .script,javax.xml.xpath,org.xml.sax > > Which causes wiring problems with OSGI and Felix, the only solution at the > moment > is adding all these java packages to org.osgi.framework.system.packages What kind of problems are you experiencing? The only problem I can see is that the imports should use ranges like `[3.18,4)` instead of pinned versions `3.18.0`. Piotr References [1] https://bnd.bndtools.org/instructions/noimportjava.html --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
