Exactly the same as removing blueprint by default. Let's talk about it together
off side.
Sent from my Samsung device
-------- Original message --------
From: Morgan Hautman <[email protected]>
Date: 15/05/2016 08:34 (GMT+01:00)
To: [email protected]
Subject: Re: Can't resolve org.osgi.service.component 1.2 ?
Hi,
Ok, I thought most of the people where positive about it when I
proposed on the mailing list.
I remember you told me only Guillaume was not convinced.
So now I don't know the reasons for the turn around, can someone
explain that to me?
Regards,
Morgan
On 2016-05-14 21:33, Jean-Baptiste
Onofré wrote:
Hi
There was a jira. But I resolved as won't fix. It's up to the
users to know they depend to the scr feature and it's better to
keep it light by default.
Regards
JB
Sent from my Samsung
device
-------- Original message --------
From: Morgan Hautman <[email protected]>
Date: 14/05/2016 08:49 (GMT+01:00)
To: [email protected]
Subject: Re: Can't resolve org.osgi.service.component 1.2 ?
Hi,
That's one of the reasons why I proposed to put the "scr" feature
in the default build of Karaf..
Because usually people forget or don't know they need to install
the "scr" feature.
I don't know if this has already been done or if there is a Jira
to track it?
Regards,
Morgan
On 2016-05-13 18:15, Leschke, Scott
wrote:
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:black;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
OK,
it’s official, I’m an idiot. You’d think I could have
figured that out on my own. I have a script that
configures Karaf when I upgrade. Since I’ve been using
Blueprint prior to this I’ve never had to install it
before so I missed that. Thanks so much.
BTW,
just want to tell everyone involved in both Karaf and
BndTools what a great job both teams have done. Truly
excellent work all the way around.
From:
Achim Nierbeck [mailto:[email protected]]
Sent: Friday, May 13, 2016 10:57 AM
To: [email protected]
Subject: Re: Can't resolve
org.osgi.service.component 1.2 ?
Hi,
did you also install the scr feature,
and did you make sure it's actually the required version
;)
regards, Achim
2016-05-13 17:51 GMT+02:00 Leschke,
Scott <[email protected]>:
Hi all,
I’ve been messing
around with OSGi and Karaf for a bit over 2
years now. Technically I’m no longer a
developer, although if you want to get stuff
done, sometimes you just have to do it yourself.
I’ve built a BAM (Business Activity Monitoring)
platform using OSGi (I wasn’t aware of Decanter
when I originally did this but it sounds very
similar in many ways. Looking more closely at
that is a future).
To date, I’ve done
everything using Blueprint which has worked
quite well but I thought it might be time to
take a look at DS to see where that might fit
in. To get a feel, I had BndTools create a
component bundle and tweaked things a bit so
that it should run in Karaf 4.0.5 as BndTools
appears to be anticipating OSGi R6 support. I
changed the build to reference osgi.cmpn;
version=5.0 for example.
When I deploy the
bundle, the resolver complains about not being
able to satisfy the package requirement:
org.osgi.service.component - version [1.2-2.0).
I’ve looked at the manifest and verified that
the package is actually imported so I’m at a
loss. The component code and actual bundle
manifest are shown below, for completeness. Any
thoughts on what might be going on would be
appreciated.
Regards, Scott
Manifest-Version:
1.0
Bnd-LastModified:
1463152495066
Bundle-ManifestVersion:
2
Bundle-Name:
zCompTest
Bundle-SymbolicName:
zCompTest
Bundle-Version:
1.0.0.201605131514
Created-By:
1.8.0_71 (Oracle Corporation)
Export-Package:
com.medline.zcomptest;version="1.0.0";uses:="org.osgi.
service.component"
Import-Package:
org.osgi.service.component;version="[1.2,2)"
Require-Capability:
osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"
Service-Component:
OSGI-INF/com.medline.zcomptest.Example.xml
Tool:
Bnd-3.2.0.201605070046-SNAPSHOT
import
org.osgi.service.component.ComponentContext;
import
org.osgi.service.component.annotations.Activate;
import
org.osgi.service.component.annotations.Component;
import
org.osgi.service.component.annotations.Deactivate;
@Component(
immediate =
true
)
public class Example {
@Activate
protected void
activate(ComponentContext c)
{
System.out.println("++
ACTIVATE");
}
@Deactivate
protected void
deactivate(ComponentContext c)
{
System.out.println("--
DEACTIVATE");
}
}
--
Apache Member
Apache Karaf <http://karaf.apache.org/>
Committer & PMC
OPS4J Pax Web
<http://wiki.ops4j.org/display/paxweb/Pax+Web/>
Committer & Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf
Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project
Manager / Scrum Master
