Hi,
This can be skipped when building from graphite level instead of building
each module separately.
On Mon, Mar 5, 2012 at 3:44 PM, Subash Chaturanga wrote:
> Hi,
>
> I am experiencing this in a clean repo build from the src
> revision 121949. Have any body came across with this ?
>
> [INFO]
This issue had been caused by adding a proxy in Nexus to the external
Jarvana Repository and this repo does not allow direct access. It's fixed
now by removing this proxy in Nexus.
On Fri, Feb 17, 2012 at 12:20 PM, Chethiya Abeysinghe wrote:
> Try different internet connection to see whether thes
Try different internet connection to see whether these URLs exist.
On Fri, Feb 17, 2012 at 12:10 PM, Denis Weerasiri wrote:
> From graphite/dependencies/webharvest getting the same behavior.
>
> [INFO]
>
> [INFO] Building W
>From graphite/dependencies/webharvest getting the same behavior.
[INFO]
[INFO] Building Webharvest 2.0.wso2v1
[INFO]
Downloading:
http://maven.wso2.org
@Pradeep
Thanks. It worked.
On Thu, Feb 9, 2012 at 1:54 PM, Pradeep Fernando wrote:
> you have to build,
> org.eclipse.equinox.p2.touchpoint.eclipse:jar:2.1.0.v20110511-wso2v1 module
> found under /dependencies
>
> --Pradeep
>
> ___
> Carbon-dev maili
you have to build,
org.eclipse.equinox.p2.touchpoint.eclipse:jar:2.1.0.v20110511-wso2v1 module
found under /dependencies
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Hi
I could build the core successfully with yesterday's updates. Could you
able to get full update without any errors?
On Thu, Feb 9, 2012 at 1:22 PM, Maninda Edirisooriya wrote:
> This build error came since yesterday. This may be a problem with nexus.
>
> [INFO]
> -
I too experienced this issue with clean-repo. Had to ignore validations to
get rid of them. IMO, clean repo builds will be helpful to resolve these
issues.
On Wed, Feb 1, 2012 at 5:03 PM, Shammi Jayasinghe wrote:
>
>
> On Wed, Feb 1, 2012 at 5:01 PM, Amila Maha Arachchi wrote:
>
>> Hi Shammi,
>>
On Wed, Feb 1, 2012 at 5:01 PM, Amila Maha Arachchi wrote:
> Hi Shammi,
>
> These checksums are in the repository (I checked). I built today with a
> clean repo and didnt face this issue.
>
Thanks amila, seems to be local to me.
Thanks
Shammi
>
> Regards,
> AmilaM.
>
>
> On Wed, Feb 1, 2012 at
Hi Shammi,
These checksums are in the repository (I checked). I built today with a
clean repo and didnt face this issue.
Regards,
AmilaM.
On Wed, Feb 1, 2012 at 4:49 PM, Shammi Jayasinghe wrote:
> Hi ,
>
> When building with a clean repo, i am getting following. How this can be
> fixed?
>
>
This has been fixed
Please take a svn up from the logging-mgt feature.
On Wed, Feb 1, 2012 at 2:48 PM, Amani Soysa wrote:
> I am looking into this
>
> On Wed, Feb 1, 2012 at 1:53 PM, Srinath Perera wrote:
>
>> INFO] BUILD FAILURE
>> [INFO]
>>
I am looking into this
On Wed, Feb 1, 2012 at 1:53 PM, Srinath Perera wrote:
> INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3:10:47.980s
> [INFO] Finished at: Wed Feb 01 13:16:42 IST 2012
> [INFO] Final Memory: 1082M
Oops! wrong thread
On Wed, Feb 1, 2012 at 2:28 PM, Fazlan Sabar wrote:
> Please follow, [Carbon-dev] [Trunk]Build issue : p2-profile-generation on
> carbon-dev, a mail thread initiated by Ajith.
>
>
> On Wed, Feb 1, 2012 at 2:26 PM, Shelan Perera wrote:
>
>> HI,
>>
>> I am getting this in DSS
Please follow, [Carbon-dev] [Trunk]Build issue : p2-profile-generation on
carbon-dev, a mail thread initiated by Ajith.
On Wed, Feb 1, 2012 at 2:26 PM, Shelan Perera wrote:
> HI,
>
> I am getting this in DSS and AS as well.
>
> Thanks.
>
> On Wed, Feb 1, 2012 at 1:53 PM, Srinath Perera wrote:
HI,
I am getting this in DSS and AS as well.
Thanks.
On Wed, Feb 1, 2012 at 1:53 PM, Srinath Perera wrote:
> INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3:10:47.980s
> [INFO] Finished at: Wed Feb 01 13:16:42 IST
We can use -N option to skip building sub projects.
-N,--non-recursive Do not recurse into sub-projects
Regards
Buddhika
On Tue, Jan 17, 2012 at 7:06 PM, KasunG Gajasinghe wrote:
>
>
> On Tue, Jan 17, 2012 at 6:21 PM, Subash Chaturanga wrote:
>
>> Hi ,
>> Today i got a full trunk update and go
Got the same error. Building from root solved the problem.
On Tue, Jan 17, 2012 at 7:20 PM, Afkham Azeez wrote:
> If pom relative paths are properly defined, you will not see this error
>
> --
> Afkham Azeez
> Sent from my phone
>
> On Jan 17, 2012 6:36 PM, "KasunG Gajasinghe" wrote:
>>
>>
>>
>>
On Tue, Jan 17, 2012 at 6:21 PM, Subash Chaturanga wrote:
> Hi ,
> Today i got a full trunk update and got a build failure when building
> service stubs which is $subject .
>
Hi Subash,
The conclusion we came up was that either trunk should be built from root,
or you need to manually copy the ca
Hi ,
Today i got a full trunk update and got a build failure when building
service stubs which is $subject .
Here is the error log.
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.972s
[INFO] Finished at: Tue Jan 17 17:55:5
yeah, that worked. thanks.
On Sun, Dec 18, 2011 at 6:27 PM, KasunG Gajasinghe 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 Sun, De
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 wrote:
> [ERROR] Failed to execute goal
> org.apache.maven.plugi
On Sat, Dec 17, 2011 at 7:47 PM, Ruchira Wageesha wrote:
> Hi Harshana,
>
> As Azeez mentioned, e4ximpl was added properly and it is an external.
>
Yeap.. i also updated with ignoring externals :)
>
> Seems someone has added e4ximpl module entry to dependency pom but has not
>> committed the co
Hi Harshana,
As Azeez mentioned, e4ximpl was added properly and it is an external.
Seems someone has added e4ximpl module entry to dependency pom but has not
> committed the code to dependency.
>
> Yet another way to break the build :)
>
Yes, but not updating your code properly :P
>
>
Thanks.
>
Sorry Ruchira. Harshana & I both made the mistake of getting an svn update
with --ignore-externals. :(
On Sat, Dec 17, 2011 at 2:25 PM, Harshana Martin wrote:
> I got the e4ximpl module after taking the svn up again. Not sure why i
> didn't get it previously.
>
> Thanks.
> Harshana
> On Dec 17,
I got the e4ximpl module after taking the svn up again. Not sure why i
didn't get it previously.
Thanks.
Harshana
On Dec 17, 2011 2:19 PM, "Afkham Azeez" wrote:
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinf
Why didn't Bamboo send a build failed mail?
On Sat, Dec 17, 2011 at 2:15 PM, Afkham Azeez wrote:
> The culprit is Ruchira
>
>
> On Sat, Dec 17, 2011 at 2:07 PM, Harshana Martin wrote:
>
>> I'm too getting this.
>>
>> Seems someone has added e4ximpl module entry to dependency pom but has
>> not c
The culprit is Ruchira
On Sat, Dec 17, 2011 at 2:07 PM, Harshana Martin wrote:
> I'm too getting this.
>
> Seems someone has added e4ximpl module entry to dependency pom but has not
> committed the code to dependency.
>
> Yet another way to break the build :)
>
> Thanks.
> /Harshana
>
> On Sat,
I'm too getting this.
Seems someone has added e4ximpl module entry to dependency pom but has not
committed the code to dependency.
Yet another way to break the build :)
Thanks.
/Harshana
On Sat, Dec 17, 2011 at 1:56 PM, Afkham Azeez wrote:
> [INFO] Scanning for projects...
> [ERROR] The build
Harshana,
I have trigger build with clean repo and test this. After that will update
you.
Thanks.
On Wed, Dec 14, 2011 at 11:53 AM, Harshana Martin wrote:
>
>
> On Wed, Dec 14, 2011 at 10:50 AM, Sanjeewa Malalgoda wrote:
>
>> Harshana,
>> please take svn update on carbon root pom. build it once.
On Wed, Dec 14, 2011 at 10:50 AM, Sanjeewa Malalgoda wrote:
> Harshana,
> please take svn update on carbon root pom. build it once. This happens due
> to your axis2 1.6.1 wso2v4 has not updated with latest changes. Here Tenant
> activity component found axis2 v4 but it dont have latest changes. Sa
Harshana,
please take svn update on carbon root pom. build it once. This happens due
to your axis2 1.6.1 wso2v4 has not updated with latest changes. Here Tenant
activity component found axis2 v4 but it dont have latest changes. Same
thing happens to pradeeban as well and we sorted it out.
Thanks.
Sanjeewa,
Please look into this.
On Wed, Dec 14, 2011 at 8:03 AM, Harshana Martin wrote:
> Hi,
>
> See the error below.
>
> ==
>
> [ERROR] Failed to execute goal
> org.apache.felix:maven-scr-plugin:1.0.10:scr (generate-scr-scrdescriptor
Thanks,
Will do.
On Tue, Dec 13, 2011 at 5:16 PM, Senaka Fernando wrote:
> Hi Dileepa,
>
> I believe that you have not taken an update of the entire trunk. Some
> changes were also made to carbon.ui, which you have unfortunately missed.
> Can you take an update of the whole trunk and rebuild?
>
Hi Dileepa,
I believe that you have not taken an update of the entire trunk. Some
changes were also made to carbon.ui, which you have unfortunately missed.
Can you take an update of the whole trunk and rebuild?
Thanks,
Senaka.
On Tue, Dec 13, 2011 at 5:08 PM, Dileepa Jayakody wrote:
> Hi,
>
>
Seems the pom is invalid. did you check ?
Regards,
/Nuwan
On Mon, Dec 12, 2011 at 10:05 PM, Chintana Wilamuna wrote:
> Hi,
>
> Trying to build with a clean repo,
>
> C:\src\wso2\carbon\dependencies>mvn --version
> Apache Maven 3.0.3 (r1075438; 2011-02-28 23:01:09+0530)
> Maven home: C:\bin\apach
Oops, I had the assembly plugin commented out previous and had a conflict
during an svn up.
Sorted now.
-Chintana
On Mon, Dec 12, 2011 at 10:05 PM, Chintana Wilamuna wrote:
> Hi,
>
> Trying to build with a clean repo,
>
> C:\src\wso2\carbon\dependencies>mvn --version
> Apache Maven 3.0.3 (r
It was due to that feature was not built (org.wso2.carbon.deployment.syn
chronizer.subversion.feature) eventhough i tried to build from the root.It
was rectified after building it after navigating.
Immediate pom has included those modules in default pom so might be a
random error that it was not bu
Shelan,
Your suppose to fix this !!! ;-)
/sumedha
On Mon, Dec 12, 2011 at 3:30 PM, Shelan Perera wrote:
> Hi,
>
> I am having a build failure with the following error log in
> revision Revision: 117429
>
> [INFO] WSO2 DataServices - DataServices Profile Generation SUCCESS
> [2:09.854s]
> [INFO
Hi Pradeep,
Thank you for the instructions, Shelan is looking into this.
Cheers,
Anjana.
On Sun, Dec 11, 2011 at 4:01 PM, Pradeep Fernando wrote:
> Hi Anjana,
>
> you have to check the generated manifests to find out what exactly
> happened.
>
> you will find a .tmpXXX file inside p2-profilege
Hi,
Fixed this error in trunk.Please take a svn up of
products/ms/modules/org.wso2.stratos.ms.deployment.
Thanks;
On Fri, Dec 9, 2011 at 10:46 PM, Harshana Martin wrote:
> Hi,
>
> See the error below, Please fix this ASAP.
>
> LOCATION: *products/ms/modules/org.wso2.stratos.ms.deployment*
>
>
Hi Anjana,
you have to check the generated manifests to find out what exactly happened.
you will find a .tmpXXX file inside p2-profilegen/target.
run this shell script against the jar found inside those. then search for
that weird string within MANIFEST files( find . iname MANIFEST.MF | xargs
gr
On Sun, Dec 11, 2011 at 10:49 AM, Afkham Azeez wrote:
> Pradeeban recently copied the LB product from the branch to the trunk. I
> think there is some cleaning up to do.
>
>
oh. yes. That must be the reason. Will look and fix the mismatches.
Thank you.
Regards,
Pradeeban.
>
> On Sun, Dec 11, 20
Hi,
I added some missing features into the DSS service p2-profile, and also
created the missing
"org.wso2.carbon.deployment.synchronizer.subversion.feature". Now when I
build DSS, I get the following error,
[INFO] Running Equinox P2 Publisher Application for Repository Generation
[INFO] Command
Yes, I got the same failure.
On Sun, Dec 11, 2011 at 11:09 AM, Harshana Martin wrote:
> Hi Sanjeewa, Anjana,
>
> There is a build failure in DSS Service distribution. Please fix this ASAP.
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached (di
Hi,
I'm checking it.
Cheers,
Anjana.
On Sun, Dec 11, 2011 at 11:09 AM, Harshana Martin wrote:
> Hi Sanjeewa, Anjana,
>
> There is a build failure in DSS Service distribution. Please fix this ASAP.
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:at
Hi Tharindu,
On Sun, Dec 11, 2011 at 1:02 PM, Tharindu Mathew wrote:
> So Harshana, the initial problem seems to be local to you is it not?
Yes. It is local to me and It was due to some missing content from external
and build works fine. Sorry for the noise! :(
Thanks and Regards,
Harshana
>
Hi Tharindu
On Sun, Dec 11, 2011 at 11:14 AM, Tharindu Mathew wrote:
> We built this under a clean repo and managed to build without any issue...
> have you missed a svn external at the feature level?
>
Yes. it builds fine. Sorry for the noise! For some reason my checkout did
not contain all th
So Harshana, the initial problem seems to be local to you is it not?
There is NO break in the build...
I will fix up the integration tests... we have not looked into the running
of integration tests in trunk...
On Sun, Dec 11, 2011 at 12:34 PM, Harshana Martin wrote:
> Hi Anjana,
>
> On Sun, D
Hi Anjana,
On Sun, Dec 11, 2011 at 12:30 PM, Afkham Azeez wrote:
> BAM distribution builds successfully. However, in the integration tests,
> when the server starts up, the following stacktrace is printed.
>
> 2011-12-11 12:29:11,309] ERROR
> {org.wso2.carbon.coordination.core.internal.Coordinat
BAM integration tests have been conveniently commented out from the pom by
someone. BAM integration tests don't even compile!
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 3:57.369s
[INFO] Finished at: Sun Dec 11 12:32:16 IS
BAM distribution builds successfully. However, in the integration tests,
when the server starts up, the following stacktrace is printed.
2011-12-11 12:29:11,309] ERROR
{org.wso2.carbon.coordination.core.internal.CoordinationClientDSComponent}
- Eror in initializing Coordination component: null
E
Hi Tharindu,
On Sun, Dec 11, 2011 at 11:14 AM, Tharindu Mathew wrote:
> We built this under a clean repo and managed to build without any issue...
> have you missed a svn external at the feature level?
>
I build with a fresh checkout. But I'll try with another checkout and let
you know.
Thanks
We built this under a clean repo and managed to build without any issue...
have you missed a svn external at the feature level?
Regards,
Tharindu
Sent from Transformer
On Dec 11, 2011 10:39 AM, "Harshana Martin" wrote:
> Hi Tharindu,
>
> There is a build failure in BAM. Manager product also fai
On Sun, Dec 11, 2011 at 10:43 AM, Afkham Azeez wrote:
> LB does not need eventing
>
+1
>
> On Sun, Dec 11, 2011 at 10:24 AM, Harshana Martin wrote:
>
>> Hi Pradeeban,
>>
>> There is a build failure in LB.
>>
>> [ERROR] Failed to execute goal on project wso2lb: Could not resolve
>> dependencies
On Sun, Dec 11, 2011 at 10:43 AM, Afkham Azeez wrote:
> LB does not need eventing
>
+1
When I commented out the entire event related dependencies from LB
distribution pom, it build without any issue.
Thanks and Regards,
Harshana
>
> On Sun, Dec 11, 2011 at 10:24 AM, Harshana Martin wrote:
>
>
Pradeeban recently copied the LB product from the branch to the trunk. I
think there is some cleaning up to do.
On Sun, Dec 11, 2011 at 10:43 AM, Harshana Martin wrote:
> Hi Pradeep,
>
> On Sun, Dec 11, 2011 at 10:39 AM, Pradeep Fernando wrote:
>
>> I think we are not using eventing component an
LB does not need eventing
On Sun, Dec 11, 2011 at 10:24 AM, Harshana Martin wrote:
> Hi Pradeeban,
>
> There is a build failure in LB.
>
> [ERROR] Failed to execute goal on project wso2lb: Could not resolve
> dependencies for project org.wso2.lb:wso2lb:pom:1.0.0-SNAPSHOT: The
> following artifac
Hi Pradeep,
On Sun, Dec 11, 2011 at 10:39 AM, Pradeep Fernando wrote:
> I think we are not using eventing component any-more. We agreed to use
> event, AFAIR.
Ok. Thanks for the info.
This means the dependencies in the LB product are outdated and needs to be
removed. Will do that.
Thanks and
I think we are not using eventing component any-more. We agreed to use
event, AFAIR.
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Hi Ratha,
Yeah, there was another problem in the feature pom, in specifying the
relative path. Fixed it now.
Cheers,
Anjana.
On Fri, Dec 9, 2011 at 1:58 PM, Vijayaratha Vijayasingam wrote:
> Hi anjana,
> Now i face issue at Coordination Core Feature..pls check
>
>
> 2\carbon\org.wso2.carbon.dat
Hi anjana,
Now i face issue at Coordination Core Feature..pls check
2\carbon\org.wso2.carbon.datasource.feature\3.2.3\org.wso2.carbon.datasource.feature-3.2.3.zip
[INFO]
[INFO] Building WSO2 Carbon - Coordination Core Feature
Hi Anjana,
How about sharing that with the 'How we break the build" mail thread
on carbon-dev :-)
Thanks & regards,
-Prabath
On Fri, Dec 9, 2011 at 1:31 PM, Anjana Fernando wrote:
> Hi Ratha,
>
> Yeah, there was a problem, thanks for reporting it, it's fixed now.
>
> Cheers,
> Anjana.
>
>
> On
Hi Ratha,
Yeah, there was a problem, thanks for reporting it, it's fixed now.
Cheers,
Anjana.
On Fri, Dec 9, 2011 at 12:57 PM, Vijayaratha Vijayasingam
wrote:
> my orbit has
> apache-zookeeper-3.3.4.wso2v1
>
> this asks older version..i got update today morning..
>
> -Rtaha
>
> On 9 December 20
my orbit has
apache-zookeeper-3.3.4.wso2v1
this asks older version..i got update today morning..
-Rtaha
On 9 December 2011 12:49, Harshana Martin wrote:
> Hi Ratha,
>
> This is because you haven't build the zookeeper module in the orbit. Build
> zookeeper orbit bundle first and then build compo
Hi Ratha,
This is because you haven't build the zookeeper module in the orbit. Build
zookeeper orbit bundle first and then build components.
Thanks and Regards,
Harshana
On Fri, Dec 9, 2011 at 12:45 PM, Vijayaratha Vijayasingam
wrote:
> is anybody checking this?
>
> -Ratha
>
> On 9 December 201
is anybody checking this?
-Ratha
On 9 December 2011 12:09, Vijayaratha Vijayasingam wrote:
> Please fix asap
>
> INFO]
> INFO] Building WSO2 Carbon - Coordination Server
> INFO] task-segment: [clean, install]
> INFO] ---
Lahiru,
I think Pradeep sent a fix for this yesterday. Can you get a svn up, and
make sure the said issue is gone? (you'll have to delete
wso2-p2-agent-3.2.0-SNAPSHOT.zip from the repo first! )
Thanks,
KasunG
On Friday, December 9, 2011, Lahiru Sandaruwan wrote:
> Hi ,
> I got an error while bu
Hi ,
I got an error while building
trunk/product/carbon,
"Could not find artifact org.wso2.carbon:wso2-p2-agent:zip:3.2.0-SNAPSHOT"
When I copy the "wso2-p2-agent-3.2.0-SNAPSHOT.zip" to relevant repository
it builds successfully.
Thanks.
On Thu, Dec 8, 2011 at 12:21 AM, Harshana Martin wrote:
On Thu, Dec 8, 2011 at 12:17 AM, Harshana Martin wrote:
> On Thu, Dec 8, 2011 at 12:09 AM, KasunG Gajasinghe wrote:
>
>>
>>
>> On Wed, Dec 7, 2011 at 11:06 PM, Nirmal Fernando wrote:
>>
>>> Another error in trunk/orbit/libthrift
>>>
>>> [ERROR] Failed to execute goal on project libthrift: Could
On Thu, Dec 8, 2011 at 12:09 AM, KasunG Gajasinghe wrote:
>
>
> On Wed, Dec 7, 2011 at 11:06 PM, Nirmal Fernando wrote:
>
>> Another error in trunk/orbit/libthrift
>>
>> [ERROR] Failed to execute goal on project libthrift: Could not resolve
>> dependencies for project libthrift.wso2:libthrift:bu
On Wed, Dec 7, 2011 at 11:06 PM, Nirmal Fernando wrote:
> Another error in trunk/orbit/libthrift
>
> [ERROR] Failed to execute goal on project libthrift: Could not resolve
> dependencies for project libthrift.wso2:libthrift:bundle:0.5.wso2v1:
> Could not find artifact org.apache.thrift:libthrift:
Another error in trunk/orbit/libthrift
[ERROR] Failed to execute goal on project libthrift: Could not resolve
dependencies for project libthrift.wso2:libthrift:bundle:0.5.wso2v1:
Could not find artifact org.apache.thrift:libthrift:jar:0.5-wso2v1 in
wso2-nexus (http://maven.wso2.org/nexus/content/g
I've already fixed commons-pool issue. Pls fix the rest.
Thanks.
/Harshana
On Dec 7, 2011 7:38 PM, "KasunG Gajasinghe" wrote:
>
> There's another error popped up in the latest trunk when built with fresh
> repo from carbon root. The reason is that the version
> in orbit/commons-pool/pom.xml is 3
sorry for the inconvenience. will fix those issues.
Regards,
Dinusha.
On Wed, Dec 7, 2011 at 7:37 PM, KasunG Gajasinghe wrote:
>
> There's another error popped up in the latest trunk when built with fresh
> repo from carbon root. The reason is that the version
> in orbit/commons-pool/pom.xml
There's another error popped up in the latest trunk when built with fresh
repo from carbon root. The reason is that the version
in orbit/commons-pool/pom.xml is 3.2.0 instead of 3.2.0-SNAPSHOT. Further,
there's some more non-resolvable parent poms in the samples/ of greg.
[ERROR] The build could
On Wed, Dec 7, 2011 at 1:20 AM, Keheliya Gallaba wrote:
>
>
> On Wed, Dec 7, 2011 at 1:08 AM, Kasun Gajasinghe wrote:
>
>>
>>
>> On Wed, Dec 7, 2011 at 12:48 AM, Suresh Attanayaka wrote:
>>
>>> Hi Guys,
>>>
>>> I could build service stubs other than *org.wso2.carbon.stratos.common.stub
>>> *and
On Wed, Dec 7, 2011 at 1:08 AM, Kasun Gajasinghe wrote:
>
>
> On Wed, Dec 7, 2011 at 12:48 AM, Suresh Attanayaka wrote:
>
>> Hi Guys,
>>
>> I could build service stubs other than *org.wso2.carbon.stratos.common.stub
>> *and *org.wso2.carbon.tenant.register.gapp.stub* successfully.
>>
>> The error
On Wed, Dec 7, 2011 at 12:48 AM, Suresh Attanayaka wrote:
> Hi Guys,
>
> I could build service stubs other than *org.wso2.carbon.stratos.common.stub
> *and *org.wso2.carbon.tenant.register.gapp.stub* successfully.
>
> The error message i get when i'm
> building org.wso2.carbon.stratos.common.stub
Hi Guys,
I could build service stubs other than *org.wso2.carbon.stratos.common.stub
*and *org.wso2.carbon.tenant.register.gapp.stub* successfully.
The error message i get when i'm
building org.wso2.carbon.stratos.common.stub is:
"The parents form a cycle:
org.wso2.carbon:org.wso2.carbon.stratos.
Ideally if you trigger a build from the root level then the root pom would
be copied to the m2 repo. However I tried that approach with Sanjeew now
and it seems this is not happening now. I checked the pom files but
couldn't find any obvious issue, Pradeep/Harshana any idea what could be
the issue?
On Tue, Dec 6, 2011 at 3:18 PM, Kishanthan Thangarajah
wrote:
> Hi,
>
> On Tue, Dec 6, 2011 at 3:05 PM, Muhammed Shariq wrote:
>
>> Building from the carbon root should add the platform pom to the m2 repo
>> ..
>>
>
>
Yes, but we couldn't build carbon from root. So, had to build the top-level
sub
On Tue, Dec 6, 2011 at 3:52 PM, Dileepa Jayakody wrote:
> Hi,
>
> As a workaround for this you can copy the carbon-platform pom from
> carbon/components in to your m2 repo.
>
> Go to carbon/components and copy the pom to m2 repo in the following
> manner.
>
> cp pom.xml
> ~/.m2/repository/org/ws
Hi,
As a workaround for this you can copy the carbon-platform pom from
carbon/components in to your m2 repo.
Go to carbon/components and copy the pom to m2 repo in the following manner.
cp pom.xml
~/.m2/repository/org/wso2/carbon/carbon-platform/3.2.0-SNAPSHOT/carbon-platform-3.2.0-SNAPSHOT.pom
Hi,
On Tue, Dec 6, 2011 at 3:05 PM, Muhammed Shariq wrote:
> Building from the carbon root should add the platform pom to the m2 repo
> ..
>
With maven3, can we build the trunk from carbon root pom for the first time
with fresh repo?
Thanks,
Kishanthan.
>
> On Tue, Dec 6, 2011 at 2:49 PM, Kas
Building from the carbon root should add the platform pom to the m2 repo ..
On Tue, Dec 6, 2011 at 2:49 PM, Kasun Gajasinghe wrote:
> Hi,
>
> I faced the following issue when building carbon/service-stubs/ with Maven
> 3.0.3, and a fresh repo. The log is given below. This error is not produced
>
On Mon, Dec 5, 2011 at 5:20 PM, Sanjaya Vithanagama wrote:
> Hi,
>
> I get the following error when building features in carbon trunk.
>
> [ERROR] Failed to execute goal on project
> org.wso2.carbon.rule.server.feature: Could not resolve dependencies for
> project
> org.wso2.carbon:org.wso2.carbon
This is fixed now. There are multiple pom files which are changed. So it
easier to take an up in components and features level.
Thanks,
Thilina
On Thu, Dec 1, 2011 at 5:25 PM, Thilina Buddhika wrote:
> I am looking into this issue now.
>
> Thanks,
> Thilina
>
> On Thu, Dec 1, 2011 at 5:08 PM, K
I am looking into this issue now.
Thanks,
Thilina
On Thu, Dec 1, 2011 at 5:08 PM, Kathiravelu Pradeeban wrote:
> Installing org.wso2.carbon.qpid.server.feature.group 3.2.0.SNAPSHOT.
> Installing org.wso2.carbon.identity.oauth.server.feature.group
> 3.2.0.SNAPSHOT.
> Installation failed.
> Cannot
Hi Isuru,
We introduced slf4j orbit bundle to the trunk recently. It is not released
yet. It just bundles the standard slfj4-1.5.10 jar as an OSGi bundle.
Also I was able to build the trunk/orbit in a fresh repo without any issue.
Can you please try building this again ?
Thanks,
Thilina
On Mon,
Hi,
On Tue, Nov 29, 2011 at 2:22 PM, Kathiravelu Pradeeban
wrote:
> Hi,
> I took an svn up of the trunk and built from the top most level. It fails
> as below.
>
I've forgotten to add an orbit bundle to the root pom. Fixed now.
Thanks,
Anjana.
>
> [INFO] WSO2 Carbon - Tasks Core .
Can someone from BPS team have a look please, I'm still failing to build
ode in trunk.
thanks,
On Fri, Nov 18, 2011 at 5:30 PM, Ranga Siriwardena wrote:
>
> Hi,
>
> Now it failed with following error. Rampart version defined in ODE is not
> matching with current rampart version.
> Please have a
Hi,
Now it failed with following error. Rampart version defined in ODE is not
matching with current rampart version.
Please have a look.
[INFO]
[INFO] BUILD FAILURE
[INFO]
Hi,
I have changed the axis2-transport-jms version from 1.1.0-wso2v4 to
1.1.0-wso2v6 to fix this issue because that is the correct existing version.
On Fri, Nov 18, 2011 at 3:40 PM, Miyuru Wanninayaka wrote:
> Building trunk/dependencies/transports/1.1.0-wso2v4/modules/jms manually
> worked for
Building trunk/dependencies/transports/1.1.0-wso2v4/modules/jms manually
worked for me
Seems many trunk dependency versions are messed up. Most dependency
versions are even older than 3.2.2 dependency versions. AFIU trunk
dependencies should point to relevant apache svn.
On Fri, Nov 18, 2011 at 3
This is already fixed by Sadeep. Please update service-mgt.
On Mon, Sep 26, 2011 at 5:49 PM, Shammi Jayasinghe wrote:
>
> [INFO]
>
> [INFO] Building WSO2 AppServer - AppServer Profile Generation
> [INFO]task-segment: [c
hi,
Thanks! The compilation error is fixed now..
Lakmali
On Wed, Sep 21, 2011 at 10:02 AM, Muhammed Shariq wrote:
> Hi,
>
> I changed the modifier of terminateTenantConfigContext method to public
> in TenantAxisUtils.java after a clarifying with Azeez, can you please take
> an svn up a
Hi,
I changed the modifier of terminateTenantConfigContext method to public
in TenantAxisUtils.java after a clarifying with Azeez, can you please take
an svn up at org.wso2.carbon.core and continue building.
On Wed, Sep 21, 2011 at 1:04 PM, Muhammed Shariq wrote:
> Hi,
>
> This compilation err
Hi,
This compilation error occurs due to a recent change done by DimuthuL,
112472 dimuthul private static void
terminateTenantConfigContext(ConfigurationContext tenantCfgCtx) {
Is there any other method that could be used to terminate the tenants axis
config?
On Wed, Sep 21, 2011 at 10:01
This is fixed now. Please take an up in trunk/orbit/opensaml2 and do an
online build. Then build the same orbit bundle in 3.2.2. This should fix the
P2 issue in the 3.2.2 branch.
Thanks,
Thilina
On Thu, Aug 18, 2011 at 1:27 AM, Kathiravelu Pradeeban
wrote:
> Is this fixed?
> I am also still gett
Is this fixed?
I am also still getting this error in 3.2.2, and that blocks me. [Everything
is upto-date.]
Yes, I agree with Thilina - I am building both trunk and 3.2.x from the same
local M2 repo.
Thank you.
Regards,
Pradeeban.
On Mon, Aug 15, 2011 at 5:08 PM, Rajika Kumarasiri wrote:
> I a
1 - 100 of 254 matches
Mail list logo
