Hi Team,
We have faced below issue after upgrading the carbon-transports version for
product-sp milestone release.
Cannot complete the install because one or more required items could not be
found.
Software being installed: WSO2 MSF4J Feature 2.3.0.m2
(org.wso2.msf4j.feature.group 2.3.0.m2)
Missing requirement: quartz 2.3.0.wso2v1 (quartz 2.3.0.wso2v1) requires
'package commonj.work 0.0.0' but it could not be found
Cannot satisfy dependency:
From: WSO2 Carbon Transport Connector Framework Feature 4.4.17
(org.wso2.carbon.connector.framework.feature.group 4.4.17)
To: quartz [2.3.0.wso2v1]
Cannot satisfy dependency:
From: WSO2 MSF4J Feature 2.3.0.m2 (org.wso2.msf4j.feature.group 2.3.0.m2)
To: org.wso2.carbon.connector.framework.feature.group [4.3.0.m2,5.0.0)
When we analyzed the related orbit bundle, I could see there are some
external dependencies are defined in the Import-Package section of the
manifest as shown below.
Import-Package: com.mchange.v2.c3p0,com.zaxxer.hikari;version="[2.3,3)
",commonj.work;resolution:=optional,javax.ejb;resolution:=optional,ja
vax.jms;resolution:=optional,javax.mail;resolution:=optional,javax.ma
il.internet;resolution:=optional,javax.management,javax.management.op
enmbean,javax.naming,javax.servlet;resolution:=optional,javax.servlet
.http;resolution:=optional,javax.sql;resolution:=optional,javax.trans
action;resolution:=optional,javax.xml.bind,javax.xml.namespace,javax.
xml.parsers,javax.xml.xpath,oracle.sql;resolution:=optional,org.jboss
.logging;resolution:=optional,org.jboss.naming;resolution:=optional,o
rg.jboss.system;resolution:=optional,org.quartz,org.quartz.impl.match
ers,org.quartz.impl.triggers,org.quartz.jobs;resolution:=optional,org
.quartz.spi,org.slf4j;version="[1.7,2)",org.terracotta.toolkit;resolu
tion:=optional,org.terracotta.toolkit.atomic;resolution:=optional,org
.terracotta.toolkit.builder;resolution:=optional,org.terracotta.toolk
it.cluster;resolution:=optional,org.terracotta.toolkit.collections;re
solution:=optional,org.terracotta.toolkit.concurrent.locks;resolution
:=optional,org.terracotta.toolkit.config;resolution:=optional,org.ter
racotta.toolkit.internal;resolution:=optional,org.terracotta.toolkit.
internal.concurrent.locks;resolution:=optional,org.terracotta.toolkit
.rejoin;resolution:=optional,org.terracotta.toolkit.search;resolution
:=optional,org.terracotta.toolkit.search.attribute;resolution:=option
al,org.terracotta.toolkit.store;resolution:=optional,org.w3c.dom,org.
xml.sax,weblogic.jdbc.jts;resolution:=optional,weblogic.jdbc.vendor.o
racle;resolution:=optional
IMO, above is not correct, then we'll ended up adding more and more
external dependencies to use this orbit bundle. @Pubudu, Have we tested
above orbit bundle in any product distribution before doing the release ?
I have checked the pom file of existing orbit release of quartz
(2.1.1.wso2v1) and it has below entries. IMO, below should be the correct
way to handle this..
<plugins>
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>1.4.0</version>
<extensions>true</extensions>
<configuration>
<instructions>
<Bundle-SymbolicName>${pom.artifactId}</Bundle-SymbolicName>
<Bundle-Name>${pom.artifactId}</Bundle-Name>
<Export-Package>
org.quartz.*;version="2.1.1"
</Export-Package>
*<Import-Package />*
* <DynamicImport-Package>*</DynamicImport-Package>*
</instructions>
</configuration>
</plugin>
</plugins>
@Thusitha, Nira and team, appreciate your input on this ?
Thanks,
Mohan
--
*V. Mohanadarshan*
*Associate Tech Lead,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com <http://wso2.com> *
*lean.enterprise.middleware.*
email: [email protected]
phone:(+94) 771117673
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
