When I look at the sources, the OSGi import for Commons Lang look correct. What am I missing?
Gary On Fri, Jul 25, 2025 at 10:01 AM Gary Gregory <garydgreg...@gmail.com> wrote: > Hello Zac, > > The POM for Text has a custom section for OSGi imports that wasn't > manually updated. There might be a way to generate this automatically with > a Maven Plug-in, not sure. In the meantime, would you please provide a PR > in GitHub? > > Gary > > > On Fri, Jul 25, 2025, 09:54 Zac Spitzer <zac.spit...@gmail.com> 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? >> >> For example, here is the MANIFEST.mf section from common-text 1.13.1 >> >> Import-Package: org.apache.commons.lang3;version="3.17.0",org.apache.com >> mons.lang3.function;version="3.17.0",org.apache.commons.lang3.time;vers >> ion="3.17.0",javax.script,javax.xml.xpath,org.xml.sax >> >> 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 >> >> Is this intended behavior? >> >
