[JBoss JIRA] (ISPN-4853) OSGI metadata import-package version ranges are too narrow
by Andrew Scully (JIRA)
[ https://issues.jboss.org/browse/ISPN-4853?page=com.atlassian.jira.plugin.... ]
Andrew Scully commented on ISPN-4853:
-------------------------------------
Just to confirm, I checked 6.0.2.Final and it doesn't suffer from this issue.
> OSGI metadata import-package version ranges are too narrow
> ----------------------------------------------------------
>
> Key: ISPN-4853
> URL: https://issues.jboss.org/browse/ISPN-4853
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 7.0.0.CR1
> Environment: Any OSGI environment (but found on Glassfish / Apache Felix).
> Reporter: Andrew Scully
> Labels: OSGI, bundle, import, package
>
> The OSGI import-package statement is specifying specific dependencies on a number of packages, rather than a range. This makes it impossible to install Infinispan 7 in any OSGI environment that doesn't have the exact versions of the dependencies present.
> Normally, the version range for dependencies would range from the major:minor:revision of the minimum requirement, up to the next major version (exclusive).
> I've copied and pasted the "Imported Packages" output below from my Apache Felix bundle console for the infinispan-core bundle.
> The bundle will not resolve because the versions of javax.transaction, JGroups, jboss-marshalling and jboss-logging are slightly newer than those required.
> The org.osgi.service.blueprint dependency is also dubious -- I'm not sure you usually have a runtime dependency on this package (even if you use Blueprint).
> For example, the following statement...
> org.jboss.marshalling;version="[1.4.4.Final,1.4.4.Final]"
> ...should probably be...
> org.jboss.marshalling;version="[1.4.4.Final,2)"
> ...in order to comply with standard semantic versioning policy.
> Felix output:
> javax.management from org.apache.felix.framework (0)
> javax.naming from org.apache.felix.framework (0)
> javax.security.auth from org.apache.felix.framework (0)
> javax.transaction,version=[1.1.0,1.1.0] -- Cannot be resolved
> javax.transaction.xa,version=[1.1.0,1.1.0] -- Cannot be resolved
> javax.xml.namespace from org.apache.felix.framework (0)
> javax.xml.parsers from org.apache.felix.framework (0)
> javax.xml.stream from org.apache.felix.framework (0)
> javax.xml.transform from org.apache.felix.framework (0)
> javax.xml.transform.dom from org.apache.felix.framework (0)
> javax.xml.transform.stream from org.apache.felix.framework (0)
> net.jcip.annotations from com.springsource.net.jcip.annotations (62)
> org.infinispan.commons,version=[7.0.0.CR1,7.0.0.CR1] from org.infinispan.commons (159)
> org.infinispan.commons.api,version=[7.0.0.CR1,7.0.0.CR1] from org.infinispan.commons (159)
> org.infinispan.commons.configuration,version=[7.0.0.CR1,7.0.0.CR1] from org.infinispan.commons (159)
> org.infinispan.commons.equivalence,version=[7.0.0.CR1,7.0.0.CR1] from org.infinispan.commons (159)
> org.infinispan.commons.executors,version=[7.0.0.CR1,7.0.0.CR1] from org.infinispan.commons (159)
> org.infinispan.commons.hash,version=[7.0.0.CR1,7.0.0.CR1] from org.infinispan.commons (159)
> org.infinispan.commons.io,version=[7.0.0.CR1,7.0.0.CR1] from org.infinispan.commons (159)
> org.infinispan.commons.logging,version=[7.0.0.CR1,7.0.0.CR1] from org.infinispan.commons (159)
> org.infinispan.commons.marshall,version=[7.0.0.CR1,7.0.0.CR1] from org.infinispan.commons (159)
> org.infinispan.commons.marshall.jboss,version=[7.0.0.CR1,7.0.0.CR1] from org.infinispan.commons (159)
> org.infinispan.commons.util,version=[7.0.0.CR1,7.0.0.CR1] from org.infinispan.commons (159)
> org.infinispan.commons.util.concurrent,version=[7.0.0.CR1,7.0.0.CR1] from org.infinispan.commons (159)
> org.infinispan.commons.util.concurrent.jdk8backported,version=[7.0.0.CR1,7.0.0.CR1] from org.infinispan.commons (159)
> org.jboss.logging,version=[3.1.2.GA,3.1.2.GA] -- Cannot be resolved
> org.jboss.marshalling,version=[1.4.4.Final,1.4.4.Final] -- Cannot be resolved
> org.jboss.marshalling.util,version=[1.4.4.Final,1.4.4.Final] -- Cannot be resolved
> org.jgroups,version=[3.5.0.Final,3.5.0.Final] -- Cannot be resolved
> org.jgroups.blocks,version=[3.5.0.Final,3.5.0.Final] -- Cannot be resolved
> org.jgroups.blocks.mux,version=[3.5.0.Final,3.5.0.Final] -- Cannot be resolved
> org.jgroups.jmx,version=[3.5.0.Final,3.5.0.Final] -- Cannot be resolved
> org.jgroups.logging,version=[3.5.0.Final,3.5.0.Final] -- Cannot be resolved
> org.jgroups.protocols,version=[3.5.0.Final,3.5.0.Final] -- Cannot be resolved
> org.jgroups.protocols.relay,version=[3.5.0.Final,3.5.0.Final] -- Cannot be resolved
> org.jgroups.protocols.tom,version=[3.5.0.Final,3.5.0.Final] -- Cannot be resolved
> org.jgroups.stack,version=[3.5.0.Final,3.5.0.Final] -- Cannot be resolved
> org.jgroups.util,version=[3.5.0.Final,3.5.0.Final] -- Cannot be resolved
> org.osgi.service.blueprint,version=[1.0.0,2.0.0) -- Cannot be resolved
> org.w3c.dom from org.apache.felix.framework (0)
> org.xml.sax from org.apache.felix.framework (0)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4884) Deployment scanner should be enabled to allow filter/converter jar deployment
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4884?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-4884:
-----------------------------------
Status: Open (was: New)
> Deployment scanner should be enabled to allow filter/converter jar deployment
> -----------------------------------------------------------------------------
>
> Key: ISPN-4884
> URL: https://issues.jboss.org/browse/ISPN-4884
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 7.0.0.CR2
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Priority: Critical
> Fix For: 7.0.0.Final
>
>
> When we want to copy JARS and deploy it on JDG server in standalone/clustered.xml is no deployment-scanner element defined. It should be added when server is built
> Steps to Reproduce:
> 1. cp filter-converter.jar infinispan-server-7.0.0.CR2/standalone/deployments/
> 2. look at console output of server
> 3. check if there is no output from deployment scanner
> Current results: not output from deployment scanner, because it is not enabled
> Expected results: we should see following output in console log
> JBAS015012: Started FileSystemDeploymentService for directory /home/infinispan-server-7.0.0.CR2/standalone/deployments
> JBAS015876: Starting deployment of "filter-converter.jar" (runtime-name: "filter-converter.jar")
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4885) Deployment Commands does not exist in CLI
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4885?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-4885:
-----------------------------------
Status: Open (was: New)
> Deployment Commands does not exist in CLI
> -----------------------------------------
>
> Key: ISPN-4885
> URL: https://issues.jboss.org/browse/ISPN-4885
> Project: Infinispan
> Issue Type: Enhancement
> Components: JMX, reporting and management, Server
> Affects Versions: 7.0.0.CR2
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Priority: Critical
> Fix For: 7.0.0.Final
>
>
> There is NO deploy or undeploy command in JDG CLI. When we want to deploy some JAR file we should provide user deployment functionality via CLI
> Steps to Reproduce:
> 1. run infinispan-server/bin/cli.sh
> 2. connect
> 3. press <TAB>
> Actual results: no deploy/undeploy command is available
> Expected results: deploy/undeploy commands should be available for user
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4884) Deployment scanner should be enabled to allow filter/converter jar deployment
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4884?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-4884:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/2993
> Deployment scanner should be enabled to allow filter/converter jar deployment
> -----------------------------------------------------------------------------
>
> Key: ISPN-4884
> URL: https://issues.jboss.org/browse/ISPN-4884
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 7.0.0.CR2
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Priority: Critical
> Fix For: 7.0.0.Final
>
>
> When we want to copy JARS and deploy it on JDG server in standalone/clustered.xml is no deployment-scanner element defined. It should be added when server is built
> Steps to Reproduce:
> 1. cp filter-converter.jar infinispan-server-7.0.0.CR2/standalone/deployments/
> 2. look at console output of server
> 3. check if there is no output from deployment scanner
> Current results: not output from deployment scanner, because it is not enabled
> Expected results: we should see following output in console log
> JBAS015012: Started FileSystemDeploymentService for directory /home/infinispan-server-7.0.0.CR2/standalone/deployments
> JBAS015876: Starting deployment of "filter-converter.jar" (runtime-name: "filter-converter.jar")
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4885) Deployment Commands does not exist in CLI
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4885?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-4885:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1156401
> Deployment Commands does not exist in CLI
> -----------------------------------------
>
> Key: ISPN-4885
> URL: https://issues.jboss.org/browse/ISPN-4885
> Project: Infinispan
> Issue Type: Enhancement
> Components: JMX, reporting and management, Server
> Affects Versions: 7.0.0.CR2
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Priority: Critical
> Fix For: 7.0.0.Final
>
>
> There is NO deploy or undeploy command in JDG CLI. When we want to deploy some JAR file we should provide user deployment functionality via CLI
> Steps to Reproduce:
> 1. run infinispan-server/bin/cli.sh
> 2. connect
> 3. press <TAB>
> Actual results: no deploy/undeploy command is available
> Expected results: deploy/undeploy commands should be available for user
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months