http://builder3.us1.wso2.org/builds/31-oct-2012/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Hi All
The carbon products build has failed due to the following error which has
caused even the previous build to fail;
30-Oct-2012 22:31:20[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.7.2:test (default-test) on
project identity-integration-tests: There are
---
Developer Studio Eclipse-Tools #487 failed.
---
Code has been updated by viraj.
No failed tests found, a possible compilation error.
**BRS team,
Please make sure to fix the license file since the purpose of releasing BRS
with Carbon-4.0.3 is the issues in license in previous release. I can still
find obsolete versions in license. For example, we have
org.wso2.carbon.rule.backend_4.0.3.jar in repository/components/plugins but
---
WSO2 Carbon 4.0.x Kernel_4.0.3 #16 was successful.
---
Code has been updated by suresh.
http://wso2.org/bamboo/browse/WCB001-KER001-16/
--
Hi,
For the issue [1] we cannot specify whitespaces in state ID. It is a
constraint added by SCXML and it gives an exception when it tries to parse.
According to this [2] release note they have mentioned
not to add white spaces in state IDs. A fix would be to add a temporary
element which will
I have added the IS feature categories into the 4.0.3 release.
Rajika
On Wed, Oct 31, 2012 at 11:20 AM, Dileepa Jayakody dile...@wso2.com wrote:
On Wed, Oct 31, 2012 at 10:44 AM, Rajika Kumarasiri raj...@wso2.comwrote:
I noticed that the current 4.0.3 feature is a copy from the 4.0.2, so
---
Developer Studio Eclipse-Tools #488 was successful.
---
Code has been updated by jasintha, viraj.
http://wso2.org/bamboo/browse/DS0001-DSET01-488/
2012-10-31 17:04:07,047] WARN
{org.apache.axis2.deployment.AxisConfigBuilder} - Unable to instantiate
deployer org.wso2.carbon.dataservices.core.DBDeployer; see debug logs for
more details
[2012-10-31 17:04:07,391] INFO {or
___
Dev mailing list
Hi,
I get this error intermittently when adding to cache...
Can I please know what might be the cause for this?
[2012-10-31 18:04:32,933] ERROR {net.sf.ehcache.store.DiskStore} -
SCIM_CACHECache: Could not read disk store element for key
admin@carbon.super. Initial cause was SCIM_CACHE Cache:
[INFO] Total time: 4:56.700s
[INFO] Finished at: Wed Oct 31 06:49:59 PDT 2012
[INFO] Final Memory: 9M/106M
[INFO]
[ERROR] Failed to execute goal
org.wso2.maven:carbon-p2-plugin:1.5.1:p2-repo-gen (2-p2-repo-generation) on
[ERROR] Failed to execute goal on project org.wso2.carbon.billing.mgt:
Could not resolve dependencies for project
org.wso2.carbon:org.wso2.carbon.billing.mgt:bundle:2.0.3: Failed to collect
dependencies for [org.wso2.carbon:org.wso2.carbon.registry.core:jar:4.0.0
(compile),
The check sum validation was ignored using the -c command line option to
maven.
Rajika
On Wed, Oct 31, 2012 at 7:51 PM, Rajika Kumarasiri raj...@wso2.com wrote:
[ERROR] Failed to execute goal on project org.wso2.carbon.billing.mgt:
Could not resolve dependencies for project
Hi,
Does anyone know $subject. Do we not have unit tests now? Can I please get
some pointers how to do so?
Thanks,
-Chintana
--
Chintana Wilamuna
Senior Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
phone: +94 72 145 4545
blog: http://engwar.com/
photos:
Installing org.wso2.carbon.rule.service.server.feature.group 4.0.2.
Installation failed.
Cannot complete the install because one or more required items could not be
found.
Software being installed: WSO2 Carbon - Logging Management Feature 4.0.3
(org.wso2.carbon.logging.mgt.feature.group 4.0.3)
Your best bet would be to look into one of the integration test module in
one of the products.
Rajika
On Wed, Oct 31, 2012 at 10:23 PM, Chintana Wilamuna chint...@wso2.comwrote:
Hi,
Does anyone know $subject. Do we not have unit tests now? Can I please get
some pointers how to do so?
http://builder3.us1.wso2.org/builds/31-oct-2012-r147004/
These were built with test in a clean repo on r147004. Manager has build
failures reported in the other thread.
Rajika
___
Dev mailing list
Dev@wso2.org
---
WSO2 Carbon 4.0.x Products_4.0.3 #15 failed.
---
This build occurred because it is a dependant of WCB001-PLA001-39.
No failed tests found, a possible
We do have unit tests only for some components such
as org.wso2.carbon.dataservices.core and org.wso2.carbon.registry.core.
No documents available on the subject yet. Rajika's suggestion would be the
best approach.
Thanks,
Krishantha.
On Wed, Oct 31, 2012 at 10:23 PM, Chintana Wilamuna
Hi Shelan,
Did you try defining the state ID by replacing all the whitespaces with
'.' character.
*Eg:- Ready For QA == Ready.For.QA*
IIRC, it should show that correctly in the UI. Also IIRC, similar scenarios
have been tested against lifecycles in past releases. Maybe QA folks can
share more
It has to be the combination of Unit tests and Integration tests IMO. since
they serve different purposes
Regards,
/Nuwan
On Wed, Oct 31, 2012 at 10:47 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
We do have unit tests only for some components such
as
Hi,
As suggested it was really helpful if you look into integration test of a
product. I wrote a small blog post [1] which is very basic at the time we
were assigned to convert Junit based integration tests to Testng last year.
[1] http://blog.shelan.org/2012/02/better-testing-with-testng.html
---
WSO2 Carbon 4.0.x Platform_4.0.3 #41 failed.
---
This build occurred because it is a dependant of WCB001-KER001-18.
No failed tests found, a possible
---
WSO2 Carbon 4.0.x Platform_4.0.3 #42 failed.
---
This build occurred because it is a dependant of WCB001-KER001-19.
No failed tests found, a possible
Hi
I'm looking into this...
Thanks,
Reka
On Wed, Oct 31, 2012 at 10:46 PM, Rajika Kumarasiri raj...@wso2.com wrote:
Installing org.wso2.carbon.rule.service.server.feature.group 4.0.2.
Installation failed.
Cannot complete the install because one or more required items could not
be found.
---
WSO2 Carbon 4.0.x Platform_4.0.3 #43 failed.
---
Code has been updated by hasini.
No failed tests found, a possible compilation error.
On Wed, Oct 31, 2012 at 7:05 PM, Rajika Kumarasiri raj...@wso2.com wrote:
This is in the latest IS pack at
http://builder3.us1.wso2.org/builds/31-oct-2012/.
When creating a tenant following logs can be seen repeatedly. See
https://wso2.org/jira/browse/IDENTITY-536.
[2012-10-31
It seems to be not fixed in the latest packs although the fix for
https://wso2.org/jira/browse/IDENTITY-491 was reverted in
https://wso2.org/jira/browse/IDENTITY-536 with r147001.
Can you please check whether the r147001 is the correct revert?
Thanks,
Hasini.
On Thu, Nov 1, 2012 at 8:51 AM,
On Thu, Nov 1, 2012 at 8:59 AM, Hasini Gunasinghe has...@wso2.com wrote:
It seems to be not fixed in the latest packs although the fix for
https://wso2.org/jira/browse/IDENTITY-491 was reverted in
https://wso2.org/jira/browse/IDENTITY-536 with r147001.
Can you please check whether the
Hi
The attached patch here with will solve the build failure. Can someone
please commit this patches?
Thanks,
Reka
On Thu, Nov 1, 2012 at 8:01 AM, Reka Thirunavukkarasu r...@wso2.com wrote:
Hi
I'm looking into this...
Thanks,
Reka
On Wed, Oct 31, 2012 at 10:46 PM, Rajika Kumarasiri
Yes. We came across this issue while testing G-Reg 4.0.0 release and then
the solution given was to use fullstops instead of spaces. In fact, in
latest G-Reg packs, the default ServiceLifeCycle has a state in this format.
:
state id=Production
datamodel
Patch applied in r147035.
Rajika
On Thu, Nov 1, 2012 at 9:02 AM, Dimuthu Leelarathne dimut...@wso2.comwrote:
On Thu, Nov 1, 2012 at 8:59 AM, Hasini Gunasinghe has...@wso2.com wrote:
It seems to be not fixed in the latest packs although the fix for
https://wso2.org/jira/browse/IDENTITY-491
Patches were applied in r147047.
Rajika
On Thu, Nov 1, 2012 at 9:04 AM, Reka Thirunavukkarasu r...@wso2.com wrote:
Hi
The attached patch here with will solve the build failure. Can someone
please commit this patches?
Thanks,
Reka
On Thu, Nov 1, 2012 at 8:01 AM, Reka Thirunavukkarasu
Hi Senaka,
Currently, we have hard coded the location at [1].
We should be able to pass the key store location as a parameter.
[1]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/products/greg/4.5.2/modules/checkin-client/src/main/java/org/wso2/registry/checkin/ClientUtils.java
https://wso2.org/jira/browse/REGISTRY-1478
Thanks
Ajith
On Thu, Nov 1, 2012 at 10:47 AM, Ajith Vitharana aji...@wso2.com wrote:
Hi Senaka,
Currently, we have hard coded the location at [1].
We should be able to pass the key store location as a parameter.
[1]
Hi All,
Yes.
Without this, we cannot use Check-In client when the default trust stores
are changed.
Thanks and Regards,
Harshana
On Thu, Nov 1, 2012 at 12:17 PM, Ajith Vitharana aji...@wso2.com wrote:
Hi Senaka,
Currently, we have hard coded the location at [1].
We should be able to pass
Hi Ajith,
Where can we add this configuration?
thanks
Eranda
On Thu, Nov 1, 2012 at 10:53 AM, Harshana Martin harsh...@wso2.com wrote:
Hi All,
Yes.
Without this, we cannot use Check-In client when the default trust stores
are changed.
Thanks and Regards,
Harshana
On Thu, Nov 1,
Hi Eranda,
The location is available on the carbon.xml, and if someone has already set
the property, we should use it instead of overriding it. Anyway we should
see what and what check-in client needs from carbon.home, because ideally
this should work in an environment that does not have a Carbon
---
WSO2 Carbon 4.0.x Platform_4.0.3 #44 failed.
---
This build occurred because it is a dependant of WCB001-KER001-20.
No failed tests found, a possible
Thanks..!
Reka
On Thu, Nov 1, 2012 at 10:44 AM, Rajika Kumarasiri raj...@wso2.com wrote:
Patches were applied in r147047.
Rajika
On Thu, Nov 1, 2012 at 9:04 AM, Reka Thirunavukkarasu r...@wso2.comwrote:
Hi
The attached patch here with will solve the build failure. Can someone
please
40 matches
Mail list logo