+1, this is good way to make lives easier for dev in a proper standards
way. We should do this as part of improving quality.
On Sun, Dec 18, 2011 at 12:16 PM, Thilina Buddhika thili...@wso2.comwrote:
Hi Folks,
Since we have a lot of developers(both internal and external) writing
Carbon
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
(default-compile) on project org.wso2.carbon.bpel.ui: Compilation failure:
Compilation failure:
[ERROR]
Hi Suresh,
Can you build the package service-stubs/org.wso2.carbon.bpel.stub , and
retry? Apparently, this has not been installed to the m2 repo for some
reason.
Thanks,
--KasunG
On Sun, Dec 18, 2011 at 5:45 PM, Suresh Attanayaka sur...@wso2.com wrote:
[ERROR] Failed to execute goal
What your proposing is Carbon Maven archetypes. We can have two different
archetypes, one for FE components one for BE/generic components.
http://maven.apache.org/guides/mini/guide-creating-archetypes.html
On Sun, Dec 18, 2011 at 12:16 PM, Thilina Buddhika thili...@wso2.comwrote:
Hi Folks,
yeah, that worked. thanks.
On Sun, Dec 18, 2011 at 6:27 PM, KasunG Gajasinghe kas...@wso2.com wrote:
Hi Suresh,
Can you build the package service-stubs/org.wso2.carbon.bpel.stub , and
retry? Apparently, this has not been installed to the m2 repo for some
reason.
Thanks,
--KasunG
On
Noticed that the followings are removed/commented out from test module pom
files after checking it with several products.
system properties
--
property
nameextracted.dir/name
+1 from a lurker, first thing I did was search for maven archetypes.
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
+1 for introducing maven archetypes for BE/FE components, and features.
This also reduces time spent on unwanted duplication, and also makes pom
files more organized.
Thanks,
Senaka.
On Sun, Dec 18, 2011 at 12:16 PM, Thilina Buddhika thili...@wso2.comwrote:
Hi Folks,
Since we have a lot of
Denis, what way are the not accurate?
On Sat, Dec 17, 2011 at 8:30 PM, Denis Weerasiri de...@wso2.com wrote:
On Fri, Dec 16, 2011 at 5:14 PM, Afkham Azeez az...@wso2.com wrote:
When we run the integration tests we notice that some Emma instrumentation
happens. But where are these reports?
+1
This will help not only new devs to Carbon, but also others as well.
Thanks,
Waruna
sent from my mobile.
On Dec 18, 2011 12:17 PM, Thilina Buddhika thili...@wso2.com wrote:
Hi Folks,
Since we have a lot of developers(both internal and external) writing
Carbon components and features, how
Big +1 .. and we should document them from Carbon developer guide. We
should addd this as a TODO to carbon team roadmap.
--Srinath
On Mon, Dec 19, 2011 at 7:49 AM, Waruna Ranasinghe war...@wso2.com wrote:
+1
This will help not only new devs to Carbon, but also others as well.
Thanks,
Waruna
+1 for maven archetypes for Carbon BE/FE components, and please host the
preferred WSO2 coding style sheets somewhere appropriate
so all devs can use that.
thanks
Suho
On Mon, Dec 19, 2011 at 8:10 AM, Srinath Perera srin...@wso2.com wrote:
Big +1 .. and we should document them from Carbon
Now its fixed,
Thanks,
Suho
On Fri, Dec 16, 2011 at 8:54 PM, Afkham Azeez az...@wso2.com wrote:
[ERROR] Error parsing
/Users/azeez/projects/wso2/org/trunk/carbon2/products/cep/modules/distribution/service/src/site/xdoc/samples/twitter_stock_quote_esper_local.xml:
line [-1] Error parsing the
It'a a relative result. We had the uncertainty on how to select the jarlist
(jarlist refers to text file which contains set of jar names).
i.e:
repository/components/plugins/org.wso2.carbon.bpel-3.2.0.SNAPSHOT.jar
repository/components/plugins/ode-1.3.5.SNAPSHOTwso2v2.jar
Hi Eranda,
Congratulations.
Its my pleasure to welcome you aboard as a WSO2 Committer. We really
appreciate the effort you've put in, and all the hard work behind your
contributions. Please do keep it up.
Thanks and Best Regards,
Senaka.
--
*Senaka Fernando*
Product Manager - WSO2 Governance
Hi Subash,
Congratulations.
Its my pleasure to welcome you aboard as a WSO2 Committer. We really
appreciate the effort you've put in, and all the hard work behind your
contributions. Please do keep it up.
Thanks and Best Regards,
Senaka.
--
*Senaka Fernando*
Product Manager - WSO2 Governance
Hi all,
Its better if we could use an alternative approach than using the site
plugin for this. The site plugin already has issues in javadoc generation
and introducing other variables like this one could cause further problems,
and it will be hard to solve such problems.
Thanks,
Senaka.
On
It is a great pleasure to become a carbon committer and hope to continue
the good work.
Thank you,
Eranda
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Hi
There was a possible test failure at axis2 while running unit test,
this failure scenario happens at arbitrary mode please ref trace
for further ref,
17-Dec-2011 03:54:04Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time
elapsed: 0.013 sec17-Dec-2011 03:54:04*Running
Hi Dushan,
I still see Abdera tests failures in the trunk? what is their status?
Can we fix it with the same as the branch?
--Srinath
--
Srinath Perera, Ph.D.
Senior Software Architect, WSO2 Inc.
Visiting Faculty, University of Moratuwa
Member, Apache
Hi Srinath,
Please find the thread [Carbon-build] [Bamboo-Build] WSO2 Carbon Trunk
WSO2 Carbon - Platform Trunk #10 has FAILED (73 tests failed, 6 failures
were new). Change made by 11 authors. discussing this issue.
Thanks,
Senaka.
On Mon, Dec 19, 2011 at 9:57 AM, Srinath Perera
There are no commits to the 3.2.0 dependancies since we did the last build
to QA - which was built with tests...
Sanjeewa/Madhuka, can you please have a look...
Thanks regards
-Prabath
On Mon, Dec 19, 2011 at 9:44 AM, Dushan Abeyruwan dus...@wso2.com wrote:
Hi
There was a possible test
Hi Dushan,
Looks like Bamboo is passing a lot of clover stuff and due to this not
being configured properly, the tests are failing. Can you please have a
look into the exceptions in [1] and fix this.
/home/bamboo/software/apache-maven-2.2.1/bin/mvn
Hi G-reg folks,
Following test is failing on Windows.
[INFO] --- maven-surefire-plugin:2.11:test (test-set0) @
org.wso2.carbon.registry.core ---
[INFO] Surefire report directory:
F:\wso2\trunk\core\org.wso2.carbon.registry.core\target\surefire-reports-0
On Mon, Dec 19, 2011 at 8:35 AM, Thilini Ishaka thil...@wso2.com wrote:
It'a a relative result. We had the uncertainty on how to select the
jarlist (jarlist refers to text file which contains set of jar names).
+1,
i.e:
repository/components/plugins/org.wso2.carbon.bpel-3.2.0.SNAPSHOT.jar
Why don't you include all jars? All jars should have test cases...
On Mon, Dec 19, 2011 at 10:48 AM, Denis Weerasiri de...@wso2.com wrote:
On Mon, Dec 19, 2011 at 8:35 AM, Thilini Ishaka thil...@wso2.com wrote:
It'a a relative result. We had the uncertainty on how to select the
jarlist
But I assume it is useful. Let say value was 70% last week and now 80%
.. that is good .. vs if it is 65% then bad.
The exact value is not that important IMO.
--Srinath
On Mon, Dec 19, 2011 at 10:48 AM, Denis Weerasiri de...@wso2.com wrote:
On Mon, Dec 19, 2011 at 8:35 AM, Thilini Ishaka
On Mon, Dec 19, 2011 at 10:54 AM, Srinath Perera srin...@wso2.com wrote:
But I assume it is useful. Let say value was 70% last week and now 80%
.. that is good .. vs if it is 65% then bad.
+1, If it's possible to store the results and compare them in Bamboo.
The exact value is not that
On Mon, Dec 19, 2011 at 10:54 AM, Srinath Perera srin...@wso2.com wrote:
But I assume it is useful. Let say value was 70% last week and now 80%
.. that is good .. vs if it is 65% then bad.
+1
The exact value is not that important IMO.
Yes. In that case this is a valid measure.
There are some regression issues in G-Reg and Senaka is working on the
fixes...
Please do not commit anything other than that..
Thanks regards,
-Prabath
On Sun, Dec 18, 2011 at 9:44 PM, Prabath Siriwardena prab...@wso2.comwrote:
We'll be tagging the branch tomorrow afternoon to do the 3.2.3
Hi Srinath,
I'm wondering whether its not important to have a proper coverage report?
I don't want to know relatively, but exactly how much code in my component
is covered by tests... And from that I want to identify sections that are
not covered and cover them with tests...
I hope my concern
Hi Tharindu,
On Mon, Dec 19, 2011 at 11:36 AM, Tharindu Mathew thari...@wso2.com wrote:
Hi Srinath,
I'm wondering whether its not important to have a proper coverage report?
I don't want to know relatively, but exactly how much code in my component
is covered by tests... And from that I
Done and Sanjeewa just started building.
Thanks,
Senaka.
On Mon, Dec 19, 2011 at 11:29 AM, Prabath Siriwardena prab...@wso2.comwrote:
There are some regression issues in G-Reg and Senaka is working on the
fixes...
Please do not commit anything other than that..
Thanks regards,
-Prabath
Hi Kishanthan,
Looks very nice... Any ETA for this?
On Mon, Dec 19, 2011 at 12:41 PM, Kishanthan Thangarajah
kishant...@wso2.com wrote:
Hi Tharindu,
On Mon, Dec 19, 2011 at 11:36 AM, Tharindu Mathew thari...@wso2.comwrote:
Hi Srinath,
I'm wondering whether its not important to have a
Hi,
Stack trace given below:
INFO] WSO2 Carbon - Mediation Tracer Stub ... SUCCESS [3.460s]
[INFO] WSO2 Carbon - Messagebox Stub . SUCCESS [15.104s]
[INFO] WSO2 Carbon - Message Store Stub .. SUCCESS [3.665s]
[INFO] WSO2 Carbon - Module Management
35 matches
Mail list logo
