gemmellr commented on PR #5663: URL: https://github.com/apache/activemq-artemis/pull/5663#issuecomment-2891482481
It appears to be complaining about an unsatisified osgi dependency around jakarta.servlet, which is being required and passed on from commons-configuration 2.12.0: > Error: Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.4.7:verify (verify) on project artemis-features: Verification failures: Verification failures: Error: Feature resolution failed for [artemis/2.42.0.SNAPSHOT] Error: Message: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=artemis; type=karaf.feature; version=2.42.0.SNAPSHOT; filter:="(&(osgi.identity=artemis)(type=karaf.feature)(version>=2.42.0.SNAPSHOT))" [caused by: Unable to resolve artemis/2.42.0.SNAPSHOT: missing requirement [artemis/2.42.0.SNAPSHOT] osgi.identity; osgi.identity=artemis-amqp; type=karaf.feature [caused by: Unable to resolve artemis-amqp/2.42.0.SNAPSHOT: missing requirement [artemis-amqp/2.42.0.SNAPSHOT] osgi.identity; osgi.identity=artemis-core; type=karaf.feature [caused by: Unable to resolve artemis-core/2.42.0.SNAPSHOT: missing requirement [artemis-core/2.42.0.SNAPSHOT] osgi.identity; osgi.identity=org.apache.activemq.artemis-server-osgi; type=osgi.bundle; version="[2.42.0.SNAPSHOT,2.42.0.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve org.apache.activemq.artemis-server-osgi/2.42.0.SNAPSHOT: missing requirement [org.apache.activemq.artemis-server-osgi/2.42.0.SNAP SHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.apache.commons.configuration2.builder)(version>=2.12.0)(!(version>=3.0.0)))" **[caused by: Unable to resolve org.apache.commons.commons-configuration2/2.12.0: missing requirement [org.apache.commons.commons-configuration2/2.12.0] osgi.wiring.package; filter:="(osgi.wiring.package=jakarta.servlet)"]]**]]] Comparing the jar manifest to the working 2.11.0 manifest, its visible that the 2.12.0 release indeed added a new _jakarta.servlet_ hard requirement. Which probably it shouldn't have, since its easy to imagine folks using it in places not doing servlets, and also since the existing _javax.servlet_ requirement already present was and still is marked optional, and which I'd assume was there for supporting similar config to whatever new bits were just added. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org For additional commands, e-mail: gitbox-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
