[ https://jira.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.sys... ] luca stancapiano updated ISPN-800: ---------------------------------- Description: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67) jgroups 2.10.1.GA (fixing in jgroups 2.12) river 1.2.3.GA marshalling-api 1.2.3.GA jboss common core 2.2.14.GA jboss logging spi 2.0.5.GA rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754) i18nlog 1.0.9 log4j 1.2.16 We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. was: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67) jgroups 2.10.1.GA (fixing in jgroups 2.12) river 1.2.3.GA marshalling-api 1.2.3.GA jboss common core 2.2.14.GA jboss logging spi 2.0.5.GA rhq plugin annotations 1.4.0.B01 i18nlog 1.0.9 log4j 1.2.16 We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.sys... ] luca stancapiano commented on ISPN-800: --------------------------------------- Actually I have some doublt how migrate jboss marshalling as a OSGI bundle. This project delegates the creation of the package to the client package. This forces the client package to get the jboss marshalling classes inside own package but infinispan-core cannot host them. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.sys... ] luca stancapiano updated ISPN-800: ---------------------------------- Description: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67) jgroups 2.10.1.GA (fixing in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml) jboss common core 2.2.14.GA jboss logging spi 2.0.5.GA rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754) i18nlog 1.0.9 log4j 1.2.16 We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. was: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67) jgroups 2.10.1.GA (fixing in jgroups 2.12) river 1.2.3.GA marshalling-api 1.2.3.GA jboss common core 2.2.14.GA jboss logging spi 2.0.5.GA rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754) i18nlog 1.0.9 log4j 1.2.16 We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. Opened some issues for jboss marshalling 1.4.0: https://jira.jboss.org/browse/JBMAR-118 ,https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ,https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.sys... ] luca stancapiano updated ISPN-800: ---------------------------------- Description: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116) jboss logging spi 2.0.5.GA rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754) i18nlog 1.0.9 log4j 1.2.16 We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. was: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67) jgroups 2.10.1.GA (fixing in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116) jboss logging spi 2.0.5.GA rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754) i18nlog 1.0.9 log4j 1.2.16 We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. jgroups 2.12 will be a bundle osgi in the next release -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] luca stancapiano updated ISPN-800: ---------------------------------- Description: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116) jboss logging spi 2.0.5.GA (very hard. This project seems deprecated) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754) i18nlog 1.0.9 log4j 1.2.16 We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. was: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116) jboss logging spi 2.0.5.GA rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754) i18nlog 1.0.9 log4j 1.2.16 We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. I visited 'jboss logging spi' repository. There are sources files distributed by nexus but there is not svn or github repository. This project seems moved to jboss-logmanager project and it is very different by the original. I think a migration is mandatory to convert infinispan in OSGI -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] luca stancapiano updated ISPN-800: ---------------------------------- Description: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67 ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (very hard. This project seems deprecated) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response) log4j 1.2.16 We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. was: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67 ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (very hard. This project seems deprecated) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 log4j 1.2.16 We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] luca stancapiano updated ISPN-800: ---------------------------------- Description: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67 ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. was: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67 ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (very hard. This project seems deprecated) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] luca stancapiano updated ISPN-800: ---------------------------------- Description: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67 ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.14) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. was: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67 ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. i18nlo with the OSGI patch was released in the 1.14 version -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] luca stancapiano updated ISPN-800: ---------------------------------- Description: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67 ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.14) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) jcip-annotations 1.0 (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. was: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67 ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.14) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño updated ISPN-800: ---------------------------------- Fix Version/s: 5.0.0.BETA1 (was: 5.0.0.ALPHA1) Affects Version/s: (was: 4.2.0.CR1) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] luca stancapiano commented on ISPN-800: --------------------------------------- Hi Manik. This issue is only for core project so I cannot help you about sub-projects. Actually I consider all packages showed in https://issues.jboss.org/browse/ISPN-800 as mandatory for a OSGI installation. Once all theese libraries will be OSGI compliant I will do a installation document. Theese libraries seem enough to use infinispan inside a OSGI repo. I don't see other optional libraries. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] luca stancapiano updated ISPN-800: ---------------------------------- Description: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67 ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.14) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) jcip-annotations 1.0 (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too. They responded to me. There is a OSGI version with a different artifact name. I changed the dependency in the pom.xml of the parent project) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. was: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67 ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.14) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) jcip-annotations 1.0 (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] luca stancapiano updated ISPN-800: ---------------------------------- Description: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67 ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.15) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) jcip-annotations 1.0 (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too. They responded to me. There is a OSGI version with a different artifact name. I changed the dependency in the pom.xml of the parent project) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. was: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67 ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.14) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) jcip-annotations 1.0 (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too. They responded to me. There is a OSGI version with a different artifact name. I changed the dependency in the pom.xml of the parent project) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño reassigned ISPN-800: ------------------------------------- Assignee: Galder Zamarreño (was: Manik Surtani) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] luca stancapiano commented on ISPN-800: --------------------------------------- Hi Galder.... there is no response by jboss marshalling. That library is inside the infinispan core and it is not osgi. It must become a osgi bundle. Here the jira issue: https://issues.jboss.org/browse/JBMAR-118 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño commented on ISPN-800: --------------------------------------- Luca, I managed to talk to David and he's evaluating the right approach to this problem. Is this the last stumble, or are you waiting on other libraries too? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño updated ISPN-800: ---------------------------------- Fix Version/s: 5.0.0.CR1 (was: 5.0.0.BETA2) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño commented on ISPN-800: --------------------------------------- Luca, JBMAR-118 is closed now. I think you can ignore JBLOGGING-51 cos we don't use the old JBoss Logging SPI any more. We now use JBoss Logging 3.0.5. I think JBoss Commons is out of the dependency list now too, so maybe you don't need JBCOMMON-116. I'll ping Shelly about JBEE-67. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] luca stancapiano updated ISPN-800: ---------------------------------- Description: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA We patched it. There is a new OSGI version here: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.15) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) jcip-annotations 1.0 (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too. They responded to me. There is a OSGI version with a different artifact name. I changed the dependency in the pom.xml of the parent project) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. was: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67 ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.15) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) jcip-annotations 1.0 (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too. They responded to me. There is a OSGI version with a different artifact name. I changed the dependency in the pom.xml of the parent project) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño edited comment on ISPN-800 at 5/4/11 3:52 AM: --------------------------------------------------------------- Ok.... I write the opened issues about osgi. Below there are the issues resolved by me but not still committed: JBEE-67 (JTA api in jboss maven repository. Updated the MANIFEST.MF but there is no response) JBCOMMON-116 (JBoss Common. added a patch in the pom.xml but there is no response) JBLOGGING-51 (JBoss Logging. added a patch in the pom.xml but there is no response) https://bugzilla.redhat.com/show_bug.cgi?id=657754 (RHQ. added a patch in the pom.xml but there is no response) was (Author: sviluppatorefico): Ok.... I write the opened issues about osgi. Below there are the issues resolved by me but not still committed: https://jira.jboss.org/browse/JBEE-67 (JTA api in jboss maven repository. Updated the MANIFEST.MF but there is no response) https://jira.jboss.org/browse/JBCOMMON-116 (JBoss Common. added a patch in the pom.xml but there is no response) https://issues.jboss.org/browse/JBLOGGING-51 (JBoss Logging. added a patch in the pom.xml but there is no response) https://bugzilla.redhat.com/show_bug.cgi?id=657754 (RHQ. added a patch in the pom.xml but there is no response) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño updated ISPN-800: ---------------------------------- Description: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA We patched it. There is a new OSGI version here: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.15) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) jcip-annotations 1.0 (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too. They responded to me. There is a OSGI version with a different artifact name. I changed the dependency in the pom.xml of the parent project) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. was: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA We patched it. There is a new OSGI version here: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in https://jira.jboss.org/browse/JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See https://jira.jboss.org/browse/JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in https://issues.jboss.org/browse/JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.15) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) jcip-annotations 1.0 (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too. They responded to me. There is a OSGI version with a different artifact name. I changed the dependency in the pom.xml of the parent project) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] luca stancapiano edited comment on ISPN-800 at 5/6/11 5:57 AM: --------------------------------------------------------------- Ok Galder. I tested JBMAR-118 now and it is ok. About RHQ . It is required by infinispan. Without it we cannot install infinispan in a OSGI repository. We have no response on it was (Author: sviluppatorefico): Ok Galder. I tested JBMAR-118 now and it is ok. About JBCOMMON-116 . It is required by infinispan. Without it we cannot install infinispan in a OSGI repository -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] Manik Surtani updated ISPN-800: ------------------------------- Fix Version/s: 5.0.0.CR3 (was: 5.0.0.CR2) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-800: ------------------------------- Fix Version/s: (was: 5.0.0.CR4) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] Luca Stancapiano updated ISPN-800: ---------------------------------- Description: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA We patched it. There is a new OSGI version here: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... ) jgroups 2.10.1.GA (patched in jgroups 2.12 but not yet fixed) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.15) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) jcip-annotations 1.0 (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too. They responded to me. There is a OSGI version with a different artifact name. I changed the dependency in the pom.xml of the parent project) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. was: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA We patched it. There is a new OSGI version here: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... ) jgroups 2.10.1.GA (fixed in jgroups 2.12) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.15) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) jcip-annotations 1.0 (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too. They responded to me. There is a OSGI version with a different artifact name. I changed the dependency in the pom.xml of the parent project) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. I've seen in theese days that jgroups 1.12 has not still the OSGI metadatas in the MANIFEST.MF. I need more info about it.. waiting for a response -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] Luca Stancapiano updated ISPN-800: ---------------------------------- Description: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA We patched it. There is a new OSGI version here: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... ) jgroups 2.10.1.GA (patched in jgroups 2.12 but not yet fixed) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss logging spi 2.0.5.GA (added a jira issue in JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.15) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) jcip-annotations 1.0 (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too. They responded to me. There is a OSGI version with a different artifact name. I changed the dependency in the pom.xml of the parent project) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. was: We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA We patched it. There is a new OSGI version here: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... ) jgroups 2.10.1.GA (patched in jgroups 2.12 but not yet fixed) river 1.2.3.GA (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) marshalling-api 1.2.3.GA (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) jboss common core 2.2.14.GA (fixing in 2.2.18-SNAPSHOT. See JBCOMMON-116 ) jboss logging spi 2.0.5.GA (added a jira issue in JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version) rhq plugin annotations 1.4.0.B01 (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) i18nlog 1.0.9 (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.15) log4j 1.2.16 (that's ok...it is a osgi bundle ;)) jcip-annotations 1.0 (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too. They responded to me. There is a OSGI version with a different artifact name. I changed the dependency in the pom.xml of the parent project) We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] Luca Stancapiano commented on ISPN-800: --------------------------------------- Ok.... jgroups is now a complete OSGI bundle since the 3.x version -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] Luca Stancapiano edited comment on ISPN-800 at 9/20/11 10:58 AM: ----------------------------------------------------------------- I have not still news on rhq project was (Author: sviluppatorefico): I have not stll news on rhq project -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] Manik Surtani commented on ISPN-800: ------------------------------------ What news are you looking for? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] SBS JIRA Integration updated ISPN-800: -------------------------------------- Forum Reference: http://community.jboss.org/message/560096#560096 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira