That will not affect blueprints ability to run. It is an optional dependancy 
you probably don't need for your application.

Alasdair Nottingham

On 1 Aug 2011, at 21:22, hans sausage <hasnoadditi...@gmail.com> wrote:

> Hi Valentin,
> 
> Thank you for the quick reply! You helped me remove the error.
> 
> However there's still one problem remaining:
> 
> [...]
> Auto-properties start: file:bundles/slf4j.jdk14_1.6.1.jar 
> (org.osgi.framework.BundleException: Fragment bundles can not be started.)
> Aug 1, 2011 10:13:59 PM 
> org.apache.aries.blueprint.container.BlueprintExtender start
> INFO: No quiesce support is available, so blueprint components will not 
> participate in quiesce operations
> ____________________________
> Welcome to Apache Felix Gogo
> 
> g! lb
> START LEVEL 6
>    ID|State      |Level|Name
>     0|Active     |    0|System Bundle (3.2.1)
>     1|Active     |    5|Apache Aries Blueprint Bundle (0.3.0)
>     2|Active     |    5|Apache Aries Util (0.3.0)
>     3|Active     |    5|Apache Aries Proxy (0.3.0)
>     4|Active     |    5|Apache Felix Configuration Admin Service (1.2.8)
>     5|Resolved   |    5|slf4j-jdk14 (1.6.1)
>     6|Active     |    5|slf4j-api (1.6.1)
>     7|Active     |    5|interfaceBundle (1.0.0.SNAPSHOT)
>     8|Active     |    5|implBundle (1.0.0.SNAPSHOT)
>     9|Active     |    5|callerBundle (1.0.0.SNAPSHOT)
>    10|Active     |    1|Apache Felix Gogo Command (0.8.0)
>    11|Active     |    1|Apache Felix Gogo Runtime (0.8.0)
>    12|Active     |    1|Apache Felix Gogo Shell (0.8.0)
> 
> 
> My dependencies in provision/pom.xml now look like this:
> 
> <dependencies>
>       <dependency>
>               <groupId>org.apache.aries.blueprint</groupId>
>               <artifactId>org.apache.aries.blueprint</artifactId>
>               <version>0.3</version>
>               <exclusions>
>                   <exclusion>
>                               <groupId>org.apache.aries.testsupport</groupId>
>                               
> <artifactId>org.apache.aries.testsupport.unit</artifactId>
>                   </exclusion>
>               </exclusions>
>       </dependency>
>       <dependency>
>               <groupId>org.apache.felix</groupId>
>               <artifactId>org.apache.felix.configadmin</artifactId>
>               <version>1.2.8</version>
>       </dependency>
>       <dependency>
>               <groupId>org.slf4j</groupId>
>               <artifactId>slf4j-simple</artifactId>
>               <version>1.6.1</version>
>       </dependency>
>       <dependency>
>               <groupId>org.slf4j</groupId>
>               <artifactId>slf4j-api</artifactId>
>               <version>1.6.1</version>
>       </dependency>
> </dependencies>
> 
> I saw other threads regarding fragment bundles but I couldn't make a 
> connection to my problem here.
> Also, what's with the 'INFO: No quiesce support is available, so blueprint 
> components will not participate in quiesce operations' message? Is it 
> important? (I did not define any blueprint components in my blueprints xml)
> 
> Regards,
> Christoph
> 
> On Mon, Aug 1, 2011 at 9:59 PM, Valentin Mahrwald <vmahrw...@googlemail.com> 
> wrote:
> Hi Christoph,
> 
> as the system shows you don't need testsupport to get Blueprint running in 
> PaxConstruct or elsewhere. The test support bundle is meant for inclusion in 
> Pax Exam itests and as such depends on a junit bundle available in the 
> runtime. PaxExam has very convenient support for installing a wrapped version 
> of JUnit since the actual tests need as well, in your case I imagine you 
> should not need it and could just get rid of it.
> 
> In terms of maven pom setup I imagine you should be able to do an exclusion 
> on the aries test support element in the dependency element to make sure it 
> does not get pulled in as an unnecessary transitive dependency ... I suppose 
> there is a problem in one of the poms that does not declare it as a test 
> scoped dependency.
> 
> Hope this helps,
> 
> Valentin
> 
> On 1 Aug 2011, at 20:52, hans sausage wrote:
> 
>> Hi,
>> 
>> I want to run blueprint using pax-construct.
>> 
>> In my project directory I have a provision/pom.xml where I define 
>> dependencies to provision the project directly to pax runner.
>> 
>> However I get the following error message along with the following bundle 
>> states after running pax-provision:
>> 
>> [...]
>> Auto-properties start: file:bundles/slf4j.jdk14_1.6.1.jar 
>> (org.osgi.framework.BundleException: Fragment bundles can not be started.)
>> Aug 1, 2011 9:20:35 PM 
>> org.apache.aries.blueprint.container.BlueprintExtender start
>> INFO: No quiesce support is available, so blueprint components will not 
>> participate in quiesce operations
>> ERROR: Bundle org.apache.aries.testsupport.unit [3] Error starting 
>> file:bundles/org.apache.aries.testsupport.unit_0.3.0.jar 
>> (org.osgi.framework.BundleException: Unresolved constraint in bundle 
>> org.apache.aries.testsupport.unit [3]: Unable to resolve 3.0: missing 
>> requirement [3.0] package; (package=junit.framework))
>> org.osgi.framework.BundleException: Unresolved constraint in bundle 
>> org.apache.aries.testsupport.unit [3]: Unable to resolve 3.0: missing 
>> requirement [3.0] package; (package=junit.framework)
>>     at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3518)
>>     at org.apache.felix.framework.Felix.startBundle(Felix.java:1750)
>>     at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1179)
>>     at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
>>     at java.lang.Thread.run(Thread.java:636)
>> ____________________________
>> Welcome to Apache Felix Gogo
>> 
>> g! lb
>> START LEVEL 6
>>    ID|State      |Level|Name
>>     0|Active     |    0|System Bundle (3.2.1)
>>     1|Active     |    5|Apache Aries Blueprint Bundle (0.3.0)
>>     2|Active     |    5|Apache Aries Util (0.3.0)
>>     3|Installed  |    5|Apache Aries Unit Test Support (0.3.0)
>>     4|Active     |    5|Apache Aries Proxy (0.3.0)
>>     5|Active     |    5|Apache Felix Configuration Admin Service (1.2.8)
>>     6|Resolved   |    5|slf4j-jdk14 (1.6.1)
>>     7|Active     |    5|slf4j-api (1.6.1)
>>     8|Active     |    5|interfaceBundle (1.0.0.SNAPSHOT)
>>     9|Active     |    5|implBundle (1.0.0.SNAPSHOT)
>>    10|Active     |    5|callerBundle (1.0.0.SNAPSHOT)
>>    11|Active     |    1|Apache Felix Gogo Command (0.8.0)
>>    12|Active     |    1|Apache Felix Gogo Runtime (0.8.0)
>>    13|Active     |    1|Apache Felix Gogo Shell (0.8.0)
>> 
>> ===================================================
>> 
>> Below is the dependencies part of my provision/pom.xml:
>> 
>> <dependencies>
>>     <dependency>
>>         <groupId>org.apache.aries.blueprint</groupId>
>>         <artifactId>org.apache.aries.blueprint</artifactId>
>>         <version>0.3</version>
>>     </dependency>
>>     <dependency>
>>         <groupId>org.apache.felix</groupId>
>>         <artifactId>org.apache.felix.configadmin</artifactId>
>>         <version>1.2.8</version>
>>     </dependency>
>>     <dependency>
>>         <groupId>org.slf4j</groupId>
>>         <artifactId>slf4j-jdk14</artifactId>
>>         <version>1.6.1</version>
>>     </dependency>
>>     <dependency>
>>         <groupId>org.slf4j</groupId>
>>         <artifactId>slf4j-api</artifactId>
>>         <version>1.6.1</version>
>>     </dependency>
>>     <dependency>
>>         <groupId>junit</groupId>
>>         <artifactId>junit</artifactId>
>>         <version>3.8.1</version>
>>     </dependency>
>> </dependencies>
>> 
>> ==================================================
>> 
>> I'm new to Blueprint so all I can understand from the error Message is that 
>> there's a problem either with slf4j or junit (or both..).
>> 
>> What dependencies am I missing?
>> 
>> Thanks,
>> Christoph
> 
> 

Reply via email to