Hi All,
The logic we used to have separate orbits is like below.
carbon project
|--orbit (top level orbit) : bundled 3rd party libraries with no
modifications to the source (eg: rabbitmq)
|
|--kernel/dependencies : forked non-osgi libraries used in kernel with
source code modifications (eg:
Please note that we have now completed uploading the Stratos2 Beta3 AMI to
US East region, and have updated instances in both Singapore and US East
region. Please disregard the AMI ids which were in the previous mail and
refer below for the list of updated AMI ids in the respective regions. The
Hi,
Getting the following when trying to build 4.1.3 patch release:
[ERROR] The project org.apache.juddi:juddiv3-war:3.1.5.wso2v1
(/home/ravi/PACK/platform/4.1.0/products/greg/4.6.0/modules/juddiv3-war/pom.xml)
has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact
Hi Yangjin,
It's done to preserve decimal portions of the results. If we return those
as Long values, those decimal portions will be lost.
In order to avoid cast exceptions, please use the correct output mappings
(i.e. Double type)
Thanks
Rajeev
On Wed, May 22, 2013 at 10:27 AM, Yangjin Wu
Fixed in 173034
On Wed, May 22, 2013 at 1:30 PM, Subash Chaturanga sub...@wso2.com wrote:
On Wed, May 22, 2013 at 12:24 PM, Ravi Undupitiya r...@wso2.com wrote:
Hi,
Getting the following when trying to build 4.1.3 patch release:
[ERROR] The project
Hi,
When I tried to build component platform/trunk/components I get the
following compilations on Governance - Notifications User Interface
component. Please check
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 6:38.965s
Hi all;
Senaka/Anjana/PrabathA found the root cause, that JNDI lookup for webapps
is different and the default javaURLContextFactory is not visible to
webapps.
This issue is fixed for AS 5.1.0.
We have introduced another carbon implementation of the
javaURLContextFactory , which we have to
Hi all,
Following is the jira status of API-M 1.4.0
https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hiderequestId=10990
There are 2 L2s and few L3s
Except Google analytics and login to API store with SAML2 web SSO , we've
tested other features. Please refer [1] for more detail. We've run
Most of the issues have been fixed by the team. Only there are L3s.
The pack building is on the way and we (QA team) need time to verify the
reported jiras and for regression, before giving the ok to release.
On Wed, May 22, 2013 at 3:40 PM, Nirodha Pramod niro...@wso2.com wrote:
Hi,
Hi all,
I am getting following build failure from Thrift Agent Server Feature. We
are building on clean repo to get the release packs and got this issue when
building platform 4.1.2 branch. Please have a look and provide a fix.
[INFO] WSO2 Carbon - Analytics UI Feature SUCCESS
Hi Nandika,
When we build the Appfactory product we encounter below issue:
Installing org.wso2.carbon.registry.commentstream.feature.group 1.0.0.
Installation failed.
An error occurred while configuring the installed items
session context was:(profile=WSO2CarbonProfile,
Hi
I am building from patch release 4.1.3.
] WSO2 Carbon - Patch releases - Platform Automated Test Suite SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
AFAIK this was fixed a while ago. Can you update the
patch-release/4.1.2/feature pom and retry?
Thanks,
NuwanD.
On Wed, May 22, 2013 at 4:02 PM, Malith Dhanushka mal...@wso2.com wrote:
Hi all,
I am getting following build failure from Thrift Agent Server Feature. We
are building on clean
This is fixed now.
On Wed, May 22, 2013 at 4:02 PM, Malith Dhanushka mal...@wso2.com wrote:
Hi all,
I am getting following build failure from Thrift Agent Server Feature. We
are building on clean repo to get the release packs and got this issue when
building platform 4.1.2 branch. Please
Hi all,
I followed the steps in [1] but it I was not able to complete it since the
feature installation not succeeded. As in the document I add the repo and
ESB didn't identify any feature inside it.
thanks
Eranda
[1]. http://docs.wso2.org/wiki/display/ESB460/TTRabbitMQ+AMQP+Transportpdf
--
HI all,
I was able to copy the two jars to dropins and make it work. But as per
the sample its a work around.
thanks
Eranda
On Wed, May 22, 2013 at 9:26 PM, Eranda Sooriyabandara era...@wso2.comwrote:
Hi all,
I followed the steps in [1] but it I was not able to complete it since the
On Sun, May 19, 2013 at 8:46 PM, Afkham Azeez az...@wso2.com wrote:
On Mon, May 20, 2013 at 8:04 AM, Supun Malinga sup...@wso2.com wrote:
Hi Guys,
For C5 I think we need to permanently fix the CC related issues. This
includes both the API related issues we have and the user level issues
See https://wso2.org/jira/browse/ESBJAVA-1432
Please respond.
Thanks,
Samisa...
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Guys. what about the pending fix verification effort before the release?
That also matters, to get an idea in terms of when exactly we could
release.
On Wed, May 22, 2013 at 3:28 PM, Pavithra Madurangi pavit...@wso2.comwrote:
Hi all,
Following is the jira status of API-M 1.4.0
Hi Eranda,
On which ESB version you tried this? The feature repo was
created against 4.5.1. This documentation should point to that version. But
for 4.6.0, need to test /create a new repo.
@Nirdesha, This documentation heading is wrong - TTRabbitMQ AMQP
Transportpdf. It should be corrected as
Copying documentat...@wso2.com
On Thu, May 23, 2013 at 7:55 AM, Eranda Sooriyabandara era...@wso2.comwrote:
HI Kishanthan,
Its ESB 4.6.0.
thanks
Eranda
On Thu, May 23, 2013 at 7:50 AM, Kishanthan Thangarajah
kishant...@wso2.com wrote:
Hi Eranda,
On which ESB version you tried
Copying documentat...@wso2.com. Missed it last time.
On Thu, May 23, 2013 at 8:12 AM, Nirdesha Munasinghe nirde...@wso2.comwrote:
Copying documentat...@wso2.com
On Thu, May 23, 2013 at 7:55 AM, Eranda Sooriyabandara era...@wso2.comwrote:
HI Kishanthan,
Its ESB 4.6.0.
thanks
Eranda
--
Supun Malinga
Sent from my phone.
On 23 May 2013 04:06, Shariq Muhammed sha...@wso2.com wrote:
On Sun, May 19, 2013 at 8:46 PM, Afkham Azeez az...@wso2.com wrote:
On Mon, May 20, 2013 at 8:04 AM, Supun Malinga sup...@wso2.com wrote:
Hi Guys,
For C5 I think we need to permanently fix
23 matches
Mail list logo
