Interesting, you're right - I just checked latest trunk which is nearly
the same as the 4.2.12 release. Not sure how that one got in during the
release.
I totally agree, that org.osgi.service.component should not be in the
import list and I guess we should do a new release.

Thanks
Carsten

Am 02.10.15 um 15:47 schrieb Balázs Zsoldos:
> I downloaded it from maven-central and checked the MANIFEST file:
> http://search.maven.org/#artifactdetails%7Corg.apache.felix%7Corg.apache.felix.webconsole%7C4.2.12%7Cbundle
> 
> It contains *org.osgi.service.component* in the Import-Package section, too.
> 
> Regards,
> *Balázs Zsoldos*
> 
> On Fri, Oct 2, 2015 at 3:30 PM, Carsten Ziegeler <cziege...@apache.org>
> wrote:
> 
>> I don't think that these imports are from the web console, this is the
>> list of imports of the 4.2.12 release:
>> Import-Package
>>   javax.servlet                          {version=2.4}
>>   javax.servlet.http                     {version=2.4}
>>   org.apache.commons.fileupload          {version=[1.2,2)}
>>   org.apache.commons.fileupload.disk     {version=[1.2,2)}
>>   org.apache.commons.fileupload.servlet  {version=[1.2,2)}
>>   org.apache.commons.io                  {version=[1.4,3)}
>>   org.apache.felix.webconsole            {version=[3.2,3.3)}
>>   org.apache.felix.webconsole.bundleinfo {version=[1.0,1.1)}
>>   org.json                               {version=0}
>>   org.osgi.framework                     {version=[1.6,2)}
>>   org.osgi.service.http                  {version=[1.2,2)}
>>   org.osgi.service.packageadmin          {version=[1.2,2)}
>>   org.osgi.service.startlevel            {version=[1.1,2)}
>>   org.osgi.util.tracker                  {version=[1.3,2)}
>>
>>
>> So I'm pretty sure, it's a different bundle you have problems with
>>
>> Carsten
>>
>> Am 02.10.15 um 15:26 schrieb Balázs Zsoldos:
>>> Hi,
>>>
>>> we have just upgraded to Felix Webconsole 4.2.12.
>>>
>>> There was a missing requirement: org.osgi.service.component
>>>
>>> It is a bit strange to me, why we need it as the webconsole itself should
>>> not dependent on DS API, but ok.
>>>
>>> Then I had another missing requirement: org.osgi.util.promise
>>>
>>> It is a bit strange to me why the API of DS needs the promise package,
>> but
>>> ok.
>>>
>>> Than I had another missing requirement: org.osgi.util.function
>>>
>>> This is not strange. I can undestand why promise API needs this package.
>>>
>>> Are you sure you wanted to do this? You included 3 new bundles in the
>>> dependency graph and not really used the functionality of any of them
>>> directly. It feels a bit monolithic.
>>>
>>> Kind regards,
>>> *Balázs **Zsoldos*
>>>
>>
>>
>> --
>> Carsten Ziegeler
>> Adobe Research Switzerland
>> cziege...@apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
>> For additional commands, e-mail: users-h...@felix.apache.org
>>
>>
> 


-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org

Reply via email to