[
https://jira.jboss.org/browse/JBOSGI-393?page=com.atlassian.jira.plugin.s...
]
David Bosschaert commented on JBOSGI-393:
-----------------------------------------
I think things were a little different in the AS6. In AS6 we always shipped as a loosely
coupled addon (our jars were put in a deployment folder), whereas in AS7 we are part of
the distribution (we are in the modules tree). Let's say the as integration layer
needs to change due to a change in AS itself. That means that just replacing
jboss-as-osgi.jar is not enough. It may require additional AS jars to be replaced as well.
Effectively you might end up patching the whole of AS instead of just the OSGi component,
and I think patching AS as a whole is an entirely different topic.
> This methodology ensures that we provide backward compatible
artefacts that are QAed against the latest stable AS. There should be no manual steps
required by the user to get the latest jbosgi release installed in the last stable AS.
<<
I think this may be impossible to do (but correct me if I'm wrong). Let's say
there is a change in jboss-modules that we have to react to in OSGi. This would mean that
our OSGi distribution will only work in AS versions that also contain this change.
What I think we can do is have automated runs that check a particular version of our
components with the accompanying version of AS.
So we have an installer that installs the version of our examples in AS7.0.0.Alpha1 and
tests that they work with that. Additional the installer can install the version of our
examples that work AS7.0.0.Alpha2-SNAPSHOT in that and test those. Having a single set of
artefacts that work in both would only work if the underlying AS infrastructure is very
stable, and I don't think we have hit that point yet.
Provide installer support for AS7
---------------------------------
Key: JBOSGI-393
URL:
https://jira.jboss.org/browse/JBOSGI-393
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assignee: David Bosschaert
Fix For: JBossOSGi 1.0.0 Beta10
Create dependencies to these bundles and install/start them in AS
Configuration should be explicit in standalone.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira