Well there should be a CNF error if you happen to run the message broker.
Danushka
On Thu, Jan 20, 2011 at 1:13 PM, Sumedha Rubasinghe wrote:
>
>
> On Thu, Jan 20, 2011 at 12:55 PM, Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>>
>>
>> On Wed, Jan 19, 2011 at 4:52 AM, Danushka Menik
On Thu, Jan 20, 2011 at 12:55 PM, Selvaratnam Uthaiyashankar <
shan...@wso2.com> wrote:
>
>
> On Wed, Jan 19, 2011 at 4:52 AM, Danushka Menikkumbura
> wrote:
>
>> Qpid has introduced a new class to the standard package log4j.xml (yes
>> they should not have done that). Since we can not export a g
On Wed, Jan 19, 2011 at 4:52 AM, Danushka Menikkumbura wrote:
> Qpid has introduced a new class to the standard package log4j.xml (yes they
> should not have done that). Since we can not export a given package from two
> different OSGi bundle, the solution has been to have it exported from the
> l
Qpid has introduced a new class to the standard package log4j.xml (yes they
should not have done that). Since we can not export a given package from two
different OSGi bundle, the solution has been to have it exported from the
logging bundle.
Thanks,
Danushka
On Tue, Jan 18, 2011 at 11:25 AM, Sum
I am getting the same trying to build the trunk
--Srinath
On Tue, Jan 18, 2011 at 11:25 AM, Sumedha Rubasinghe wrote:
> Why are we having a dependency to qpid-broker from logging component?
> /sumedha
> Missing:
> --
> 1) org.apache.qpid:qpid-broker:jar:0.9-wso2v1
> Try downloading the
Why are we having a dependency to qpid-broker from logging component?
/sumedha
Missing:
--
1) org.apache.qpid:qpid-broker:jar:0.9-wso2v1
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apach
