P. Ottlinger
2018-09-06 18:49:11 UTC
Hi,
I've just stumbled upon a problem that prevents me from updating from
3.7 to 3.8 in an OSGi context.
Although the release has just been a patch one, the bundle's symbolic
name changed
from "Bundle-SymbolicName org.apache.commons.lang3" in 3.7.0
to "Bundle-SymbolicName org.apache.commons.commons-lang3" in 3.8.0.
That makes it impossible to do a drop-in update, as it is a breaking change.
Is that change an error in 3.8.0 or a wanted one that could be
communicated more directly to downstream users?
May I file a bugticket in the LANG-Jira for it? I assume there has been
a hickup when building the OSGi release JAR and the change was not intended.
Thanks,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: user-***@commons.apache.org
For additional commands, e-mail: user-***@commons.apache.org
I've just stumbled upon a problem that prevents me from updating from
3.7 to 3.8 in an OSGi context.
Although the release has just been a patch one, the bundle's symbolic
name changed
from "Bundle-SymbolicName org.apache.commons.lang3" in 3.7.0
to "Bundle-SymbolicName org.apache.commons.commons-lang3" in 3.8.0.
That makes it impossible to do a drop-in update, as it is a breaking change.
Is that change an error in 3.8.0 or a wanted one that could be
communicated more directly to downstream users?
May I file a bugticket in the LANG-Jira for it? I assume there has been
a hickup when building the OSGi release JAR and the change was not intended.
Thanks,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: user-***@commons.apache.org
For additional commands, e-mail: user-***@commons.apache.org