Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-07-07 Thread Saminda Wijeratne
Harshana,

Can tycho correctly create eclipse project settings files? If so can we
remove the IDE specific files from the svn?

Saminda

On Sat, Jul 2, 2011 at 11:03 PM, Harshana Martin  wrote:

> Hi All,
>
> I believe now the transition is complete and now it is possible to build CS
> with Maven 3.
>
> Following are the things we've completed.
>
> 1. Tycho integration to build Eclipse plugins.
> 2. Introduced Tycho source plugin to generate source jars for Eclipse
> plugins.
> 3. Moved entire set of properties to CS root-pom so that we can work on
> TOOLS-654 [1].
> 4. Decoupled the CS Maven plugins from CS Eclipse plugins to support
> backward compatibility. (So that users can work with both Maven 3 and Maven
> 2 to build C-App projects.)
>
> [1]. https://wso2.org/jira/browse/TOOLS-654
>
> Thanks and Regards,
> Harshana
>
> On Sat, Jul 2, 2011 at 7:57 PM, Harshana Martin  wrote:
>
>> Hi All,
>>
>> I went ahead and committed the changes in r108855.
>>
>> Thanks and Regards,
>> Harshana
>>
>> On Sat, Jul 2, 2011 at 11:22 AM, Saminda Wijeratne wrote:
>>
>>> +1 for committing changes & moving the build to maven3.
>>>
>>> Saminda
>>>
>>> On Fri, Jul 1, 2011 at 11:18 PM, Chathuri Wimalasena 
>>> wrote:
>>>
 +1 for committing changes to CS branch.

 Regards,
 Chathuri


 On Fri, Jul 1, 2011 at 11:05 PM, Harshana Martin wrote:

> Hi All,
>
> Today I worked on migrating CS to Tycho. I was able to complete the
> task within few hours (Yeah... Tycho is fantastic and pretty easy to use 
> :)
> ) and now it works fine.
>
> But as we discussed before, it needs Maven3. So the question is, should
> i go ahead and commit the changes or do we need to wait till Carbon move 
> to
> Maven3?
>
> I don't see any shortcoming of moving to Maven3 right now for CS since
> current CS build is broken (cannot build on Mac) and we need to move at 
> some
> point. So sooner the better.
>
> Thanks and Regards,
> Harshana
>
> On Wed, May 18, 2011 at 11:17 PM, Harshana Martin 
> wrote:
>
>>
>>
>> On Wed, May 18, 2011 at 6:18 PM, Milinda Pathirage 
>> wrote:
>>
>>> I tried maven 3 for carbon platform and there are couple of issues
>>> left, I couldn't work on them due to release work. But those are very 
>>> easy
>>> to fix issues. We can start maven 3 migration after the 3.2.0 release.
>>
>>
>> +1
>>
>> Thanks and Regards,
>> Harshana
>>
>>>
>>> Thanks
>>> Milinda
>>>
>>>
>>> On Wed, May 18, 2011 at 6:08 PM, Samisa Abeysinghe 
>>> wrote:
>>>
 Milinda looked into m3. I think we can make carbon build work with
 m3 as soon as 3.2.0 release go out.


 On Wed, May 18, 2011 at 4:14 PM, Harshana Martin >>> > wrote:

> Hi Samisa,
>
> On Wed, May 18, 2011 at 3:35 PM, Samisa Abeysinghe <
> sam...@wso2.com> wrote:
>
>> But for CS case, we also need to sensitive to the fact what the
>> client will be using in their dev environment.
>
>
> +1. That's correct.
>
> The version of Maven which we use to build CS will not affect the
> CS users at all. But the main issue is having 2 Maven versions for 
> platform
> and tools, which is awkward.
>
>>
>> What is the % adaption of m3 vs m2?
>>
>
> I could not find solid statistical figures to support. But It seems
> multi module projects which benefit from parallel builds are rapidly
> adopting Maven 3.
>
> The reason for this rapid adoption is, the minimum effort we have
> to put in the migration process, compared to the benefits.
>
> Thanks and Regards,
> Harshana
>
>>
>>
>> On Wed, May 18, 2011 at 3:15 PM, Harshana Martin <
>> harsh...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> Andreas,a committer from Axis2 has pointed out to me recently
>>> that Axis2 Jenkins Server now run Maven 3. So I don't think it will 
>>> be a
>>> huge problem for us to migrate too.
>>>
>>> Thanks and Regards,
>>> Harshana
>>>
>>>
>>> On Wed, Feb 23, 2011 at 3:31 PM, Harshana Martin <
>>> harsh...@wso2.com> wrote:
>>>


 On Wed, Feb 23, 2011 at 3:23 PM, Sameera Jayasoma <
 same...@wso2.com> wrote:

>
>
> On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle  > wrote:
>
>> Can we move to Maven3?
>>
>
> Since we are doing major changes to Carbon trunk builds, It is
> better if we can start working on this migration t

Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-07-02 Thread Harshana Martin
Hi All,

I believe now the transition is complete and now it is possible to build CS
with Maven 3.

Following are the things we've completed.

1. Tycho integration to build Eclipse plugins.
2. Introduced Tycho source plugin to generate source jars for Eclipse
plugins.
3. Moved entire set of properties to CS root-pom so that we can work on
TOOLS-654 [1].
4. Decoupled the CS Maven plugins from CS Eclipse plugins to support
backward compatibility. (So that users can work with both Maven 3 and Maven
2 to build C-App projects.)

[1]. https://wso2.org/jira/browse/TOOLS-654

Thanks and Regards,
Harshana

On Sat, Jul 2, 2011 at 7:57 PM, Harshana Martin  wrote:

> Hi All,
>
> I went ahead and committed the changes in r108855.
>
> Thanks and Regards,
> Harshana
>
> On Sat, Jul 2, 2011 at 11:22 AM, Saminda Wijeratne wrote:
>
>> +1 for committing changes & moving the build to maven3.
>>
>> Saminda
>>
>> On Fri, Jul 1, 2011 at 11:18 PM, Chathuri Wimalasena 
>> wrote:
>>
>>> +1 for committing changes to CS branch.
>>>
>>> Regards,
>>> Chathuri
>>>
>>>
>>> On Fri, Jul 1, 2011 at 11:05 PM, Harshana Martin wrote:
>>>
 Hi All,

 Today I worked on migrating CS to Tycho. I was able to complete the task
 within few hours (Yeah... Tycho is fantastic and pretty easy to use :) ) 
 and
 now it works fine.

 But as we discussed before, it needs Maven3. So the question is, should
 i go ahead and commit the changes or do we need to wait till Carbon move to
 Maven3?

 I don't see any shortcoming of moving to Maven3 right now for CS since
 current CS build is broken (cannot build on Mac) and we need to move at 
 some
 point. So sooner the better.

 Thanks and Regards,
 Harshana

 On Wed, May 18, 2011 at 11:17 PM, Harshana Martin wrote:

>
>
> On Wed, May 18, 2011 at 6:18 PM, Milinda Pathirage 
> wrote:
>
>> I tried maven 3 for carbon platform and there are couple of issues
>> left, I couldn't work on them due to release work. But those are very 
>> easy
>> to fix issues. We can start maven 3 migration after the 3.2.0 release.
>
>
> +1
>
> Thanks and Regards,
> Harshana
>
>>
>> Thanks
>> Milinda
>>
>>
>> On Wed, May 18, 2011 at 6:08 PM, Samisa Abeysinghe 
>> wrote:
>>
>>> Milinda looked into m3. I think we can make carbon build work with m3
>>> as soon as 3.2.0 release go out.
>>>
>>>
>>> On Wed, May 18, 2011 at 4:14 PM, Harshana Martin 
>>> wrote:
>>>
 Hi Samisa,

 On Wed, May 18, 2011 at 3:35 PM, Samisa Abeysinghe >>> > wrote:

> But for CS case, we also need to sensitive to the fact what the
> client will be using in their dev environment.


 +1. That's correct.

 The version of Maven which we use to build CS will not affect the CS
 users at all. But the main issue is having 2 Maven versions for 
 platform and
 tools, which is awkward.

>
> What is the % adaption of m3 vs m2?
>

 I could not find solid statistical figures to support. But It seems
 multi module projects which benefit from parallel builds are rapidly
 adopting Maven 3.

 The reason for this rapid adoption is, the minimum effort we have to
 put in the migration process, compared to the benefits.

 Thanks and Regards,
 Harshana

>
>
> On Wed, May 18, 2011 at 3:15 PM, Harshana Martin <
> harsh...@wso2.com> wrote:
>
>> Hi All,
>>
>> Andreas,a committer from Axis2 has pointed out to me recently that
>> Axis2 Jenkins Server now run Maven 3. So I don't think it will be a 
>> huge
>> problem for us to migrate too.
>>
>> Thanks and Regards,
>> Harshana
>>
>>
>> On Wed, Feb 23, 2011 at 3:31 PM, Harshana Martin <
>> harsh...@wso2.com> wrote:
>>
>>>
>>>
>>> On Wed, Feb 23, 2011 at 3:23 PM, Sameera Jayasoma <
>>> same...@wso2.com> wrote:
>>>


 On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle 
 wrote:

> Can we move to Maven3?
>

 Since we are doing major changes to Carbon trunk builds, It is
 better if we can start working on this migration too.

>>>
>>> +1
>>>

 Maven3 has improved the performance over Maven2. That is just a
 single features. For other improvements, refer [1].

 Maven3 seems be compatible with Maven2 projects. But here are
 some reported compatibility issues.

>>>
>>> Yes. I tried building

Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-07-02 Thread Harshana Martin
Hi All,

I went ahead and committed the changes in r108855.

Thanks and Regards,
Harshana

On Sat, Jul 2, 2011 at 11:22 AM, Saminda Wijeratne wrote:

> +1 for committing changes & moving the build to maven3.
>
> Saminda
>
> On Fri, Jul 1, 2011 at 11:18 PM, Chathuri Wimalasena wrote:
>
>> +1 for committing changes to CS branch.
>>
>> Regards,
>> Chathuri
>>
>>
>> On Fri, Jul 1, 2011 at 11:05 PM, Harshana Martin wrote:
>>
>>> Hi All,
>>>
>>> Today I worked on migrating CS to Tycho. I was able to complete the task
>>> within few hours (Yeah... Tycho is fantastic and pretty easy to use :) ) and
>>> now it works fine.
>>>
>>> But as we discussed before, it needs Maven3. So the question is, should i
>>> go ahead and commit the changes or do we need to wait till Carbon move to
>>> Maven3?
>>>
>>> I don't see any shortcoming of moving to Maven3 right now for CS since
>>> current CS build is broken (cannot build on Mac) and we need to move at some
>>> point. So sooner the better.
>>>
>>> Thanks and Regards,
>>> Harshana
>>>
>>> On Wed, May 18, 2011 at 11:17 PM, Harshana Martin wrote:
>>>


 On Wed, May 18, 2011 at 6:18 PM, Milinda Pathirage wrote:

> I tried maven 3 for carbon platform and there are couple of issues
> left, I couldn't work on them due to release work. But those are very easy
> to fix issues. We can start maven 3 migration after the 3.2.0 release.


 +1

 Thanks and Regards,
 Harshana

>
> Thanks
> Milinda
>
>
> On Wed, May 18, 2011 at 6:08 PM, Samisa Abeysinghe wrote:
>
>> Milinda looked into m3. I think we can make carbon build work with m3
>> as soon as 3.2.0 release go out.
>>
>>
>> On Wed, May 18, 2011 at 4:14 PM, Harshana Martin 
>> wrote:
>>
>>> Hi Samisa,
>>>
>>> On Wed, May 18, 2011 at 3:35 PM, Samisa Abeysinghe 
>>> wrote:
>>>
 But for CS case, we also need to sensitive to the fact what the
 client will be using in their dev environment.
>>>
>>>
>>> +1. That's correct.
>>>
>>> The version of Maven which we use to build CS will not affect the CS
>>> users at all. But the main issue is having 2 Maven versions for 
>>> platform and
>>> tools, which is awkward.
>>>

 What is the % adaption of m3 vs m2?

>>>
>>> I could not find solid statistical figures to support. But It seems
>>> multi module projects which benefit from parallel builds are rapidly
>>> adopting Maven 3.
>>>
>>> The reason for this rapid adoption is, the minimum effort we have to
>>> put in the migration process, compared to the benefits.
>>>
>>> Thanks and Regards,
>>> Harshana
>>>


 On Wed, May 18, 2011 at 3:15 PM, Harshana Martin >>> > wrote:

> Hi All,
>
> Andreas,a committer from Axis2 has pointed out to me recently that
> Axis2 Jenkins Server now run Maven 3. So I don't think it will be a 
> huge
> problem for us to migrate too.
>
> Thanks and Regards,
> Harshana
>
>
> On Wed, Feb 23, 2011 at 3:31 PM, Harshana Martin <
> harsh...@wso2.com> wrote:
>
>>
>>
>> On Wed, Feb 23, 2011 at 3:23 PM, Sameera Jayasoma <
>> same...@wso2.com> wrote:
>>
>>>
>>>
>>> On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle 
>>> wrote:
>>>
 Can we move to Maven3?

>>>
>>> Since we are doing major changes to Carbon trunk builds, It is
>>> better if we can start working on this migration too.
>>>
>>
>> +1
>>
>>>
>>> Maven3 has improved the performance over Maven2. That is just a
>>> single features. For other improvements, refer [1].
>>>
>>> Maven3 seems be compatible with Maven2 projects. But here are
>>> some reported compatibility issues.
>>>
>>
>> Yes. I tried building Carbon with Maven 3 a little while back and
>> found several incompatibilities. But AFAIU, they are manageable. 
>> Most of the
>> problems I faced were related to Parent POM resolution.
>>
>> Thanks and Regards,
>> Harshana
>>
>>>
>>> Thanks
>>> Sameera
>>>
>>> [1]
>>> http://www.developer.com/java/article.php/3908561/Top-10-New-Features-in-Maven-3.htm
>>> [2]
>>> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>>>

 Paul

 On 27 January 2011 11:19, Harshana Martin wrote:

> Hi All,
>
> On Wed, Dec 22, 2010 at 12:27 PM, Saminda Wijeratne <
> samin...@wso2.com> wrote:
>
>>
>>

Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-07-01 Thread Saminda Wijeratne
+1 for committing changes & moving the build to maven3.

Saminda
On Fri, Jul 1, 2011 at 11:18 PM, Chathuri Wimalasena wrote:

> +1 for committing changes to CS branch.
>
> Regards,
> Chathuri
>
>
> On Fri, Jul 1, 2011 at 11:05 PM, Harshana Martin wrote:
>
>> Hi All,
>>
>> Today I worked on migrating CS to Tycho. I was able to complete the task
>> within few hours (Yeah... Tycho is fantastic and pretty easy to use :) ) and
>> now it works fine.
>>
>> But as we discussed before, it needs Maven3. So the question is, should i
>> go ahead and commit the changes or do we need to wait till Carbon move to
>> Maven3?
>>
>> I don't see any shortcoming of moving to Maven3 right now for CS since
>> current CS build is broken (cannot build on Mac) and we need to move at some
>> point. So sooner the better.
>>
>> Thanks and Regards,
>> Harshana
>>
>> On Wed, May 18, 2011 at 11:17 PM, Harshana Martin wrote:
>>
>>>
>>>
>>> On Wed, May 18, 2011 at 6:18 PM, Milinda Pathirage wrote:
>>>
 I tried maven 3 for carbon platform and there are couple of issues left,
 I couldn't work on them due to release work. But those are very easy to fix
 issues. We can start maven 3 migration after the 3.2.0 release.
>>>
>>>
>>> +1
>>>
>>> Thanks and Regards,
>>> Harshana
>>>

 Thanks
 Milinda


 On Wed, May 18, 2011 at 6:08 PM, Samisa Abeysinghe wrote:

> Milinda looked into m3. I think we can make carbon build work with m3
> as soon as 3.2.0 release go out.
>
>
> On Wed, May 18, 2011 at 4:14 PM, Harshana Martin wrote:
>
>> Hi Samisa,
>>
>> On Wed, May 18, 2011 at 3:35 PM, Samisa Abeysinghe 
>> wrote:
>>
>>> But for CS case, we also need to sensitive to the fact what the
>>> client will be using in their dev environment.
>>
>>
>> +1. That's correct.
>>
>> The version of Maven which we use to build CS will not affect the CS
>> users at all. But the main issue is having 2 Maven versions for platform 
>> and
>> tools, which is awkward.
>>
>>>
>>> What is the % adaption of m3 vs m2?
>>>
>>
>> I could not find solid statistical figures to support. But It seems
>> multi module projects which benefit from parallel builds are rapidly
>> adopting Maven 3.
>>
>> The reason for this rapid adoption is, the minimum effort we have to
>> put in the migration process, compared to the benefits.
>>
>> Thanks and Regards,
>> Harshana
>>
>>>
>>>
>>> On Wed, May 18, 2011 at 3:15 PM, Harshana Martin 
>>> wrote:
>>>
 Hi All,

 Andreas,a committer from Axis2 has pointed out to me recently that
 Axis2 Jenkins Server now run Maven 3. So I don't think it will be a 
 huge
 problem for us to migrate too.

 Thanks and Regards,
 Harshana


 On Wed, Feb 23, 2011 at 3:31 PM, Harshana Martin >>> > wrote:

>
>
> On Wed, Feb 23, 2011 at 3:23 PM, Sameera Jayasoma <
> same...@wso2.com> wrote:
>
>>
>>
>> On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle wrote:
>>
>>> Can we move to Maven3?
>>>
>>
>> Since we are doing major changes to Carbon trunk builds, It is
>> better if we can start working on this migration too.
>>
>
> +1
>
>>
>> Maven3 has improved the performance over Maven2. That is just a
>> single features. For other improvements, refer [1].
>>
>> Maven3 seems be compatible with Maven2 projects. But here are some
>> reported compatibility issues.
>>
>
> Yes. I tried building Carbon with Maven 3 a little while back and
> found several incompatibilities. But AFAIU, they are manageable. Most 
> of the
> problems I faced were related to Parent POM resolution.
>
> Thanks and Regards,
> Harshana
>
>>
>> Thanks
>> Sameera
>>
>> [1]
>> http://www.developer.com/java/article.php/3908561/Top-10-New-Features-in-Maven-3.htm
>> [2]
>> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>>
>>>
>>> Paul
>>>
>>> On 27 January 2011 11:19, Harshana Martin wrote:
>>>
 Hi All,

 On Wed, Dec 22, 2010 at 12:27 PM, Saminda Wijeratne <
 samin...@wso2.com> wrote:

>
>
> On Wed, Dec 22, 2010 at 12:18 PM, Harshana Martin <
> harsh...@wso2.com> wrote:
>
>> Hi All,
>>
>> I came across Eclipse Tycho project[0]. It turned out that, it
>> can build Eclipse plugins and OSGi bundles using Apache 
>> Maven.[1]. Thus we
>> ca

Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-07-01 Thread Chathuri Wimalasena
+1 for committing changes to CS branch.

Regards,
Chathuri

On Fri, Jul 1, 2011 at 11:05 PM, Harshana Martin  wrote:

> Hi All,
>
> Today I worked on migrating CS to Tycho. I was able to complete the task
> within few hours (Yeah... Tycho is fantastic and pretty easy to use :) ) and
> now it works fine.
>
> But as we discussed before, it needs Maven3. So the question is, should i
> go ahead and commit the changes or do we need to wait till Carbon move to
> Maven3?
>
> I don't see any shortcoming of moving to Maven3 right now for CS since
> current CS build is broken (cannot build on Mac) and we need to move at some
> point. So sooner the better.
>
> Thanks and Regards,
> Harshana
>
> On Wed, May 18, 2011 at 11:17 PM, Harshana Martin wrote:
>
>>
>>
>> On Wed, May 18, 2011 at 6:18 PM, Milinda Pathirage wrote:
>>
>>> I tried maven 3 for carbon platform and there are couple of issues left,
>>> I couldn't work on them due to release work. But those are very easy to fix
>>> issues. We can start maven 3 migration after the 3.2.0 release.
>>
>>
>> +1
>>
>> Thanks and Regards,
>> Harshana
>>
>>>
>>> Thanks
>>> Milinda
>>>
>>>
>>> On Wed, May 18, 2011 at 6:08 PM, Samisa Abeysinghe wrote:
>>>
 Milinda looked into m3. I think we can make carbon build work with m3 as
 soon as 3.2.0 release go out.


 On Wed, May 18, 2011 at 4:14 PM, Harshana Martin wrote:

> Hi Samisa,
>
> On Wed, May 18, 2011 at 3:35 PM, Samisa Abeysinghe wrote:
>
>> But for CS case, we also need to sensitive to the fact what the client
>> will be using in their dev environment.
>
>
> +1. That's correct.
>
> The version of Maven which we use to build CS will not affect the CS
> users at all. But the main issue is having 2 Maven versions for platform 
> and
> tools, which is awkward.
>
>>
>> What is the % adaption of m3 vs m2?
>>
>
> I could not find solid statistical figures to support. But It seems
> multi module projects which benefit from parallel builds are rapidly
> adopting Maven 3.
>
> The reason for this rapid adoption is, the minimum effort we have to
> put in the migration process, compared to the benefits.
>
> Thanks and Regards,
> Harshana
>
>>
>>
>> On Wed, May 18, 2011 at 3:15 PM, Harshana Martin 
>> wrote:
>>
>>> Hi All,
>>>
>>> Andreas,a committer from Axis2 has pointed out to me recently that
>>> Axis2 Jenkins Server now run Maven 3. So I don't think it will be a huge
>>> problem for us to migrate too.
>>>
>>> Thanks and Regards,
>>> Harshana
>>>
>>>
>>> On Wed, Feb 23, 2011 at 3:31 PM, Harshana Martin 
>>> wrote:
>>>


 On Wed, Feb 23, 2011 at 3:23 PM, Sameera Jayasoma >>> > wrote:

>
>
> On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle wrote:
>
>> Can we move to Maven3?
>>
>
> Since we are doing major changes to Carbon trunk builds, It is
> better if we can start working on this migration too.
>

 +1

>
> Maven3 has improved the performance over Maven2. That is just a
> single features. For other improvements, refer [1].
>
> Maven3 seems be compatible with Maven2 projects. But here are some
> reported compatibility issues.
>

 Yes. I tried building Carbon with Maven 3 a little while back and
 found several incompatibilities. But AFAIU, they are manageable. Most 
 of the
 problems I faced were related to Parent POM resolution.

 Thanks and Regards,
 Harshana

>
> Thanks
> Sameera
>
> [1]
> http://www.developer.com/java/article.php/3908561/Top-10-New-Features-in-Maven-3.htm
> [2]
> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>
>>
>> Paul
>>
>> On 27 January 2011 11:19, Harshana Martin wrote:
>>
>>> Hi All,
>>>
>>> On Wed, Dec 22, 2010 at 12:27 PM, Saminda Wijeratne <
>>> samin...@wso2.com> wrote:
>>>


 On Wed, Dec 22, 2010 at 12:18 PM, Harshana Martin <
 harsh...@wso2.com> wrote:

> Hi All,
>
> I came across Eclipse Tycho project[0]. It turned out that, it
> can build Eclipse plugins and OSGi bundles using Apache 
> Maven.[1]. Thus we
> can use it in Carbon Studio. Anyone tried this before?
>
> I am thinking of this as a solution for getting rid of
> Ant4Eclipse which we are currently using to build Carbon Studio. 
> Planning to
> play around a bit. will keep the list updated.
>

>>

Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-07-01 Thread Milinda Pathirage
+1 for migrating to Maven3. Maven3 also use M2 repo format, so there wont be
an issue using both versions simultaneously. Only thing is you have to
create a alias for Maven3 executable.

Thanks
Milinda



On Fri, Jul 1, 2011 at 11:05 PM, Harshana Martin  wrote:

> Hi All,
>
> Today I worked on migrating CS to Tycho. I was able to complete the task
> within few hours (Yeah... Tycho is fantastic and pretty easy to use :) ) and
> now it works fine.
>
> But as we discussed before, it needs Maven3. So the question is, should i
> go ahead and commit the changes or do we need to wait till Carbon move to
> Maven3?
>
> I don't see any shortcoming of moving to Maven3 right now for CS since
> current CS build is broken (cannot build on Mac) and we need to move at some
> point. So sooner the better.
>
> Thanks and Regards,
> Harshana
>
> On Wed, May 18, 2011 at 11:17 PM, Harshana Martin wrote:
>
>>
>>
>> On Wed, May 18, 2011 at 6:18 PM, Milinda Pathirage wrote:
>>
>>> I tried maven 3 for carbon platform and there are couple of issues left,
>>> I couldn't work on them due to release work. But those are very easy to fix
>>> issues. We can start maven 3 migration after the 3.2.0 release.
>>
>>
>> +1
>>
>> Thanks and Regards,
>> Harshana
>>
>>>
>>> Thanks
>>> Milinda
>>>
>>>
>>> On Wed, May 18, 2011 at 6:08 PM, Samisa Abeysinghe wrote:
>>>
 Milinda looked into m3. I think we can make carbon build work with m3 as
 soon as 3.2.0 release go out.


 On Wed, May 18, 2011 at 4:14 PM, Harshana Martin wrote:

> Hi Samisa,
>
> On Wed, May 18, 2011 at 3:35 PM, Samisa Abeysinghe wrote:
>
>> But for CS case, we also need to sensitive to the fact what the client
>> will be using in their dev environment.
>
>
> +1. That's correct.
>
> The version of Maven which we use to build CS will not affect the CS
> users at all. But the main issue is having 2 Maven versions for platform 
> and
> tools, which is awkward.
>
>>
>> What is the % adaption of m3 vs m2?
>>
>
> I could not find solid statistical figures to support. But It seems
> multi module projects which benefit from parallel builds are rapidly
> adopting Maven 3.
>
> The reason for this rapid adoption is, the minimum effort we have to
> put in the migration process, compared to the benefits.
>
> Thanks and Regards,
> Harshana
>
>>
>>
>> On Wed, May 18, 2011 at 3:15 PM, Harshana Martin 
>> wrote:
>>
>>> Hi All,
>>>
>>> Andreas,a committer from Axis2 has pointed out to me recently that
>>> Axis2 Jenkins Server now run Maven 3. So I don't think it will be a huge
>>> problem for us to migrate too.
>>>
>>> Thanks and Regards,
>>> Harshana
>>>
>>>
>>> On Wed, Feb 23, 2011 at 3:31 PM, Harshana Martin 
>>> wrote:
>>>


 On Wed, Feb 23, 2011 at 3:23 PM, Sameera Jayasoma >>> > wrote:

>
>
> On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle wrote:
>
>> Can we move to Maven3?
>>
>
> Since we are doing major changes to Carbon trunk builds, It is
> better if we can start working on this migration too.
>

 +1

>
> Maven3 has improved the performance over Maven2. That is just a
> single features. For other improvements, refer [1].
>
> Maven3 seems be compatible with Maven2 projects. But here are some
> reported compatibility issues.
>

 Yes. I tried building Carbon with Maven 3 a little while back and
 found several incompatibilities. But AFAIU, they are manageable. Most 
 of the
 problems I faced were related to Parent POM resolution.

 Thanks and Regards,
 Harshana

>
> Thanks
> Sameera
>
> [1]
> http://www.developer.com/java/article.php/3908561/Top-10-New-Features-in-Maven-3.htm
> [2]
> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>
>>
>> Paul
>>
>> On 27 January 2011 11:19, Harshana Martin wrote:
>>
>>> Hi All,
>>>
>>> On Wed, Dec 22, 2010 at 12:27 PM, Saminda Wijeratne <
>>> samin...@wso2.com> wrote:
>>>


 On Wed, Dec 22, 2010 at 12:18 PM, Harshana Martin <
 harsh...@wso2.com> wrote:

> Hi All,
>
> I came across Eclipse Tycho project[0]. It turned out that, it
> can build Eclipse plugins and OSGi bundles using Apache 
> Maven.[1]. Thus we
> can use it in Carbon Studio. Anyone tried this before?
>
> I am thinking of this as a solution for getting rid of
> Ant4Eclipse which we are currently us

Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-07-01 Thread Harshana Martin
Hi All,

Today I worked on migrating CS to Tycho. I was able to complete the task
within few hours (Yeah... Tycho is fantastic and pretty easy to use :) ) and
now it works fine.

But as we discussed before, it needs Maven3. So the question is, should i go
ahead and commit the changes or do we need to wait till Carbon move to
Maven3?

I don't see any shortcoming of moving to Maven3 right now for CS since
current CS build is broken (cannot build on Mac) and we need to move at some
point. So sooner the better.

Thanks and Regards,
Harshana

On Wed, May 18, 2011 at 11:17 PM, Harshana Martin  wrote:

>
>
> On Wed, May 18, 2011 at 6:18 PM, Milinda Pathirage wrote:
>
>> I tried maven 3 for carbon platform and there are couple of issues left, I
>> couldn't work on them due to release work. But those are very easy to fix
>> issues. We can start maven 3 migration after the 3.2.0 release.
>
>
> +1
>
> Thanks and Regards,
> Harshana
>
>>
>> Thanks
>> Milinda
>>
>>
>> On Wed, May 18, 2011 at 6:08 PM, Samisa Abeysinghe wrote:
>>
>>> Milinda looked into m3. I think we can make carbon build work with m3 as
>>> soon as 3.2.0 release go out.
>>>
>>>
>>> On Wed, May 18, 2011 at 4:14 PM, Harshana Martin wrote:
>>>
 Hi Samisa,

 On Wed, May 18, 2011 at 3:35 PM, Samisa Abeysinghe wrote:

> But for CS case, we also need to sensitive to the fact what the client
> will be using in their dev environment.


 +1. That's correct.

 The version of Maven which we use to build CS will not affect the CS
 users at all. But the main issue is having 2 Maven versions for platform 
 and
 tools, which is awkward.

>
> What is the % adaption of m3 vs m2?
>

 I could not find solid statistical figures to support. But It seems
 multi module projects which benefit from parallel builds are rapidly
 adopting Maven 3.

 The reason for this rapid adoption is, the minimum effort we have to put
 in the migration process, compared to the benefits.

 Thanks and Regards,
 Harshana

>
>
> On Wed, May 18, 2011 at 3:15 PM, Harshana Martin wrote:
>
>> Hi All,
>>
>> Andreas,a committer from Axis2 has pointed out to me recently that
>> Axis2 Jenkins Server now run Maven 3. So I don't think it will be a huge
>> problem for us to migrate too.
>>
>> Thanks and Regards,
>> Harshana
>>
>>
>> On Wed, Feb 23, 2011 at 3:31 PM, Harshana Martin 
>> wrote:
>>
>>>
>>>
>>> On Wed, Feb 23, 2011 at 3:23 PM, Sameera Jayasoma 
>>> wrote:
>>>


 On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle wrote:

> Can we move to Maven3?
>

 Since we are doing major changes to Carbon trunk builds, It is
 better if we can start working on this migration too.

>>>
>>> +1
>>>

 Maven3 has improved the performance over Maven2. That is just a
 single features. For other improvements, refer [1].

 Maven3 seems be compatible with Maven2 projects. But here are some
 reported compatibility issues.

>>>
>>> Yes. I tried building Carbon with Maven 3 a little while back and
>>> found several incompatibilities. But AFAIU, they are manageable. Most 
>>> of the
>>> problems I faced were related to Parent POM resolution.
>>>
>>> Thanks and Regards,
>>> Harshana
>>>

 Thanks
 Sameera

 [1]
 http://www.developer.com/java/article.php/3908561/Top-10-New-Features-in-Maven-3.htm
 [2]
 https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html

>
> Paul
>
> On 27 January 2011 11:19, Harshana Martin wrote:
>
>> Hi All,
>>
>> On Wed, Dec 22, 2010 at 12:27 PM, Saminda Wijeratne <
>> samin...@wso2.com> wrote:
>>
>>>
>>>
>>> On Wed, Dec 22, 2010 at 12:18 PM, Harshana Martin <
>>> harsh...@wso2.com> wrote:
>>>
 Hi All,

 I came across Eclipse Tycho project[0]. It turned out that, it
 can build Eclipse plugins and OSGi bundles using Apache Maven.[1]. 
 Thus we
 can use it in Carbon Studio. Anyone tried this before?

 I am thinking of this as a solution for getting rid of
 Ant4Eclipse which we are currently using to build Carbon Studio. 
 Planning to
 play around a bit. will keep the list updated.

>>>
>> I did some digging in to the Tycho and it turns out that it is
>> capable of building p2 sites. But it requires Maven 3 to execute 
>> this.
>> Therefore at least for the time being, we have to hang around 
>> Ant4Eclipse.
>>
>> Thanks and Rega

Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-05-18 Thread Harshana Martin
On Wed, May 18, 2011 at 6:18 PM, Milinda Pathirage  wrote:

> I tried maven 3 for carbon platform and there are couple of issues left, I
> couldn't work on them due to release work. But those are very easy to fix
> issues. We can start maven 3 migration after the 3.2.0 release.


+1

Thanks and Regards,
Harshana

>
> Thanks
> Milinda
>
>
> On Wed, May 18, 2011 at 6:08 PM, Samisa Abeysinghe wrote:
>
>> Milinda looked into m3. I think we can make carbon build work with m3 as
>> soon as 3.2.0 release go out.
>>
>>
>> On Wed, May 18, 2011 at 4:14 PM, Harshana Martin wrote:
>>
>>> Hi Samisa,
>>>
>>> On Wed, May 18, 2011 at 3:35 PM, Samisa Abeysinghe wrote:
>>>
 But for CS case, we also need to sensitive to the fact what the client
 will be using in their dev environment.
>>>
>>>
>>> +1. That's correct.
>>>
>>> The version of Maven which we use to build CS will not affect the CS
>>> users at all. But the main issue is having 2 Maven versions for platform and
>>> tools, which is awkward.
>>>

 What is the % adaption of m3 vs m2?

>>>
>>> I could not find solid statistical figures to support. But It seems multi
>>> module projects which benefit from parallel builds are rapidly adopting
>>> Maven 3.
>>>
>>> The reason for this rapid adoption is, the minimum effort we have to put
>>> in the migration process, compared to the benefits.
>>>
>>> Thanks and Regards,
>>> Harshana
>>>


 On Wed, May 18, 2011 at 3:15 PM, Harshana Martin wrote:

> Hi All,
>
> Andreas,a committer from Axis2 has pointed out to me recently that
> Axis2 Jenkins Server now run Maven 3. So I don't think it will be a huge
> problem for us to migrate too.
>
> Thanks and Regards,
> Harshana
>
>
> On Wed, Feb 23, 2011 at 3:31 PM, Harshana Martin wrote:
>
>>
>>
>> On Wed, Feb 23, 2011 at 3:23 PM, Sameera Jayasoma 
>> wrote:
>>
>>>
>>>
>>> On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle wrote:
>>>
 Can we move to Maven3?

>>>
>>> Since we are doing major changes to Carbon trunk builds, It is better
>>> if we can start working on this migration too.
>>>
>>
>> +1
>>
>>>
>>> Maven3 has improved the performance over Maven2. That is just a
>>> single features. For other improvements, refer [1].
>>>
>>> Maven3 seems be compatible with Maven2 projects. But here are some
>>> reported compatibility issues.
>>>
>>
>> Yes. I tried building Carbon with Maven 3 a little while back and
>> found several incompatibilities. But AFAIU, they are manageable. Most of 
>> the
>> problems I faced were related to Parent POM resolution.
>>
>> Thanks and Regards,
>> Harshana
>>
>>>
>>> Thanks
>>> Sameera
>>>
>>> [1]
>>> http://www.developer.com/java/article.php/3908561/Top-10-New-Features-in-Maven-3.htm
>>> [2] https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>>>

 Paul

 On 27 January 2011 11:19, Harshana Martin wrote:

> Hi All,
>
> On Wed, Dec 22, 2010 at 12:27 PM, Saminda Wijeratne <
> samin...@wso2.com> wrote:
>
>>
>>
>> On Wed, Dec 22, 2010 at 12:18 PM, Harshana Martin <
>> harsh...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I came across Eclipse Tycho project[0]. It turned out that, it
>>> can build Eclipse plugins and OSGi bundles using Apache Maven.[1]. 
>>> Thus we
>>> can use it in Carbon Studio. Anyone tried this before?
>>>
>>> I am thinking of this as a solution for getting rid of
>>> Ant4Eclipse which we are currently using to build Carbon Studio. 
>>> Planning to
>>> play around a bit. will keep the list updated.
>>>
>>
> I did some digging in to the Tycho and it turns out that it is
> capable of building p2 sites. But it requires Maven 3 to execute this.
> Therefore at least for the time being, we have to hang around 
> Ant4Eclipse.
>
> Thanks and Regards,
> Harshana
>
>
>>   +1
>>
>> Saminda
>>
>>>
>>>
>>> [0]. http://www.eclipse.org/tycho/
>>> [1].
>>> http://mattiasholmqvist.se/2010/02/building-with-tycho-part-1-osgi-bundles/
>>>
>>> Thanks and Regards,
>>> Harshana
>>> --
>>> Harshana Martin
>>> Software Engineer
>>> WSO2 Inc.
>>> Web:http://wso2.com
>>>
>>> Mobile: +94 716062650
>>> Blog: http://harshana05.blogspot.com
>>> Profile: https://www.google.com/profiles/harshana05
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>

Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-05-18 Thread Milinda Pathirage
I tried maven 3 for carbon platform and there are couple of issues left, I
couldn't work on them due to release work. But those are very easy to fix
issues. We can start maven 3 migration after the 3.2.0 release.

Thanks
Milinda

On Wed, May 18, 2011 at 6:08 PM, Samisa Abeysinghe  wrote:

> Milinda looked into m3. I think we can make carbon build work with m3 as
> soon as 3.2.0 release go out.
>
>
> On Wed, May 18, 2011 at 4:14 PM, Harshana Martin wrote:
>
>> Hi Samisa,
>>
>> On Wed, May 18, 2011 at 3:35 PM, Samisa Abeysinghe wrote:
>>
>>> But for CS case, we also need to sensitive to the fact what the client
>>> will be using in their dev environment.
>>
>>
>> +1. That's correct.
>>
>> The version of Maven which we use to build CS will not affect the CS users
>> at all. But the main issue is having 2 Maven versions for platform and
>> tools, which is awkward.
>>
>>>
>>> What is the % adaption of m3 vs m2?
>>>
>>
>> I could not find solid statistical figures to support. But It seems multi
>> module projects which benefit from parallel builds are rapidly adopting
>> Maven 3.
>>
>> The reason for this rapid adoption is, the minimum effort we have to put
>> in the migration process, compared to the benefits.
>>
>> Thanks and Regards,
>> Harshana
>>
>>>
>>>
>>> On Wed, May 18, 2011 at 3:15 PM, Harshana Martin wrote:
>>>
 Hi All,

 Andreas,a committer from Axis2 has pointed out to me recently that Axis2
 Jenkins Server now run Maven 3. So I don't think it will be a huge problem
 for us to migrate too.

 Thanks and Regards,
 Harshana


 On Wed, Feb 23, 2011 at 3:31 PM, Harshana Martin wrote:

>
>
> On Wed, Feb 23, 2011 at 3:23 PM, Sameera Jayasoma wrote:
>
>>
>>
>> On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle wrote:
>>
>>> Can we move to Maven3?
>>>
>>
>> Since we are doing major changes to Carbon trunk builds, It is better
>> if we can start working on this migration too.
>>
>
> +1
>
>>
>> Maven3 has improved the performance over Maven2. That is just a single
>> features. For other improvements, refer [1].
>>
>> Maven3 seems be compatible with Maven2 projects. But here are some
>> reported compatibility issues.
>>
>
> Yes. I tried building Carbon with Maven 3 a little while back and found
> several incompatibilities. But AFAIU, they are manageable. Most of the
> problems I faced were related to Parent POM resolution.
>
> Thanks and Regards,
> Harshana
>
>>
>> Thanks
>> Sameera
>>
>> [1]
>> http://www.developer.com/java/article.php/3908561/Top-10-New-Features-in-Maven-3.htm
>> [2] https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>>
>>>
>>> Paul
>>>
>>> On 27 January 2011 11:19, Harshana Martin  wrote:
>>>
 Hi All,

 On Wed, Dec 22, 2010 at 12:27 PM, Saminda Wijeratne <
 samin...@wso2.com> wrote:

>
>
> On Wed, Dec 22, 2010 at 12:18 PM, Harshana Martin <
> harsh...@wso2.com> wrote:
>
>> Hi All,
>>
>> I came across Eclipse Tycho project[0]. It turned out that, it can
>> build Eclipse plugins and OSGi bundles using Apache Maven.[1]. Thus 
>> we can
>> use it in Carbon Studio. Anyone tried this before?
>>
>> I am thinking of this as a solution for getting rid of Ant4Eclipse
>> which we are currently using to build Carbon Studio. Planning to 
>> play around
>> a bit. will keep the list updated.
>>
>
 I did some digging in to the Tycho and it turns out that it is
 capable of building p2 sites. But it requires Maven 3 to execute this.
 Therefore at least for the time being, we have to hang around 
 Ant4Eclipse.

 Thanks and Regards,
 Harshana


>   +1
>
> Saminda
>
>>
>>
>> [0]. http://www.eclipse.org/tycho/
>> [1].
>> http://mattiasholmqvist.se/2010/02/building-with-tycho-part-1-osgi-bundles/
>>
>> Thanks and Regards,
>> Harshana
>> --
>> Harshana Martin
>> Software Engineer
>> WSO2 Inc.
>> Web:http://wso2.com
>>
>> Mobile: +94 716062650
>> Blog: http://harshana05.blogspot.com
>> Profile: https://www.google.com/profiles/harshana05
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>

Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-05-18 Thread Samisa Abeysinghe
Milinda looked into m3. I think we can make carbon build work with m3 as
soon as 3.2.0 release go out.

On Wed, May 18, 2011 at 4:14 PM, Harshana Martin  wrote:

> Hi Samisa,
>
> On Wed, May 18, 2011 at 3:35 PM, Samisa Abeysinghe wrote:
>
>> But for CS case, we also need to sensitive to the fact what the client
>> will be using in their dev environment.
>
>
> +1. That's correct.
>
> The version of Maven which we use to build CS will not affect the CS users
> at all. But the main issue is having 2 Maven versions for platform and
> tools, which is awkward.
>
>>
>> What is the % adaption of m3 vs m2?
>>
>
> I could not find solid statistical figures to support. But It seems multi
> module projects which benefit from parallel builds are rapidly adopting
> Maven 3.
>
> The reason for this rapid adoption is, the minimum effort we have to put in
> the migration process, compared to the benefits.
>
> Thanks and Regards,
> Harshana
>
>>
>>
>> On Wed, May 18, 2011 at 3:15 PM, Harshana Martin wrote:
>>
>>> Hi All,
>>>
>>> Andreas,a committer from Axis2 has pointed out to me recently that Axis2
>>> Jenkins Server now run Maven 3. So I don't think it will be a huge problem
>>> for us to migrate too.
>>>
>>> Thanks and Regards,
>>> Harshana
>>>
>>>
>>> On Wed, Feb 23, 2011 at 3:31 PM, Harshana Martin wrote:
>>>


 On Wed, Feb 23, 2011 at 3:23 PM, Sameera Jayasoma wrote:

>
>
> On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle  wrote:
>
>> Can we move to Maven3?
>>
>
> Since we are doing major changes to Carbon trunk builds, It is better
> if we can start working on this migration too.
>

 +1

>
> Maven3 has improved the performance over Maven2. That is just a single
> features. For other improvements, refer [1].
>
> Maven3 seems be compatible with Maven2 projects. But here are some
> reported compatibility issues.
>

 Yes. I tried building Carbon with Maven 3 a little while back and found
 several incompatibilities. But AFAIU, they are manageable. Most of the
 problems I faced were related to Parent POM resolution.

 Thanks and Regards,
 Harshana

>
> Thanks
> Sameera
>
> [1]
> http://www.developer.com/java/article.php/3908561/Top-10-New-Features-in-Maven-3.htm
> [2] https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>
>>
>> Paul
>>
>> On 27 January 2011 11:19, Harshana Martin  wrote:
>>
>>> Hi All,
>>>
>>> On Wed, Dec 22, 2010 at 12:27 PM, Saminda Wijeratne <
>>> samin...@wso2.com> wrote:
>>>


 On Wed, Dec 22, 2010 at 12:18 PM, Harshana Martin <
 harsh...@wso2.com> wrote:

> Hi All,
>
> I came across Eclipse Tycho project[0]. It turned out that, it can
> build Eclipse plugins and OSGi bundles using Apache Maven.[1]. Thus 
> we can
> use it in Carbon Studio. Anyone tried this before?
>
> I am thinking of this as a solution for getting rid of Ant4Eclipse
> which we are currently using to build Carbon Studio. Planning to play 
> around
> a bit. will keep the list updated.
>

>>> I did some digging in to the Tycho and it turns out that it is
>>> capable of building p2 sites. But it requires Maven 3 to execute this.
>>> Therefore at least for the time being, we have to hang around 
>>> Ant4Eclipse.
>>>
>>> Thanks and Regards,
>>> Harshana
>>>
>>>
   +1

 Saminda

>
>
> [0]. http://www.eclipse.org/tycho/
> [1].
> http://mattiasholmqvist.se/2010/02/building-with-tycho-part-1-osgi-bundles/
>
> Thanks and Regards,
> Harshana
> --
> Harshana Martin
> Software Engineer
> WSO2 Inc.
> Web:http://wso2.com
>
> Mobile: +94 716062650
> Blog: http://harshana05.blogspot.com
> Profile: https://www.google.com/profiles/harshana05
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>

 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev


>>>
>>>
>>> --
>>> Harshana Martin
>>> Software Engineer
>>> WSO2 Inc.
>>> Web:http://wso2.com
>>>   http://wso2.org
>>>
>>> Mobile: +94 716062650
>>> Blog: http://harshana05.blogspot.com
>>> Profile: https://www.google.com/profiles/harshana05
>>> Twitter: http://twitter.com/harshana05
>>>
>>>
>>> ___
>>> Carbon-dev mailin

Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-05-18 Thread Harshana Martin
Hi Samisa,

On Wed, May 18, 2011 at 3:35 PM, Samisa Abeysinghe  wrote:

> But for CS case, we also need to sensitive to the fact what the client will
> be using in their dev environment.


+1. That's correct.

The version of Maven which we use to build CS will not affect the CS users
at all. But the main issue is having 2 Maven versions for platform and
tools, which is awkward.

>
> What is the % adaption of m3 vs m2?
>

I could not find solid statistical figures to support. But It seems multi
module projects which benefit from parallel builds are rapidly adopting
Maven 3.

The reason for this rapid adoption is, the minimum effort we have to put in
the migration process, compared to the benefits.

Thanks and Regards,
Harshana

>
>
> On Wed, May 18, 2011 at 3:15 PM, Harshana Martin wrote:
>
>> Hi All,
>>
>> Andreas,a committer from Axis2 has pointed out to me recently that Axis2
>> Jenkins Server now run Maven 3. So I don't think it will be a huge problem
>> for us to migrate too.
>>
>> Thanks and Regards,
>> Harshana
>>
>>
>> On Wed, Feb 23, 2011 at 3:31 PM, Harshana Martin wrote:
>>
>>>
>>>
>>> On Wed, Feb 23, 2011 at 3:23 PM, Sameera Jayasoma wrote:
>>>


 On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle  wrote:

> Can we move to Maven3?
>

 Since we are doing major changes to Carbon trunk builds, It is better if
 we can start working on this migration too.

>>>
>>> +1
>>>

 Maven3 has improved the performance over Maven2. That is just a single
 features. For other improvements, refer [1].

 Maven3 seems be compatible with Maven2 projects. But here are some
 reported compatibility issues.

>>>
>>> Yes. I tried building Carbon with Maven 3 a little while back and found
>>> several incompatibilities. But AFAIU, they are manageable. Most of the
>>> problems I faced were related to Parent POM resolution.
>>>
>>> Thanks and Regards,
>>> Harshana
>>>

 Thanks
 Sameera

 [1]
 http://www.developer.com/java/article.php/3908561/Top-10-New-Features-in-Maven-3.htm
 [2] https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html

>
> Paul
>
> On 27 January 2011 11:19, Harshana Martin  wrote:
>
>> Hi All,
>>
>> On Wed, Dec 22, 2010 at 12:27 PM, Saminda Wijeratne <
>> samin...@wso2.com> wrote:
>>
>>>
>>>
>>> On Wed, Dec 22, 2010 at 12:18 PM, Harshana Martin >> > wrote:
>>>
 Hi All,

 I came across Eclipse Tycho project[0]. It turned out that, it can
 build Eclipse plugins and OSGi bundles using Apache Maven.[1]. Thus we 
 can
 use it in Carbon Studio. Anyone tried this before?

 I am thinking of this as a solution for getting rid of Ant4Eclipse
 which we are currently using to build Carbon Studio. Planning to play 
 around
 a bit. will keep the list updated.

>>>
>> I did some digging in to the Tycho and it turns out that it is capable
>> of building p2 sites. But it requires Maven 3 to execute this. Therefore 
>> at
>> least for the time being, we have to hang around Ant4Eclipse.
>>
>> Thanks and Regards,
>> Harshana
>>
>>
>>>   +1
>>>
>>> Saminda
>>>


 [0]. http://www.eclipse.org/tycho/
 [1].
 http://mattiasholmqvist.se/2010/02/building-with-tycho-part-1-osgi-bundles/

 Thanks and Regards,
 Harshana
 --
 Harshana Martin
 Software Engineer
 WSO2 Inc.
 Web:http://wso2.com

 Mobile: +94 716062650
 Blog: http://harshana05.blogspot.com
 Profile: https://www.google.com/profiles/harshana05


 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev


>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Harshana Martin
>> Software Engineer
>> WSO2 Inc.
>> Web:http://wso2.com
>>   http://wso2.org
>>
>> Mobile: +94 716062650
>> Blog: http://harshana05.blogspot.com
>> Profile: https://www.google.com/profiles/harshana05
>> Twitter: http://twitter.com/harshana05
>>
>>
>> ___
>> Carbon-dev mailing list
>> carbon-...@lists.wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>
> Office: +44 844 484 8143
> Cell: +44 798 447 4618
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfre

Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-05-18 Thread Samisa Abeysinghe
But for CS case, we also need to sensitive to the fact what the client will
be using in their dev environment.

What is the % adaption of m3 vs m2?

On Wed, May 18, 2011 at 3:15 PM, Harshana Martin  wrote:

> Hi All,
>
> Andreas,a committer from Axis2 has pointed out to me recently that Axis2
> Jenkins Server now run Maven 3. So I don't think it will be a huge problem
> for us to migrate too.
>
> Thanks and Regards,
> Harshana
>
>
> On Wed, Feb 23, 2011 at 3:31 PM, Harshana Martin wrote:
>
>>
>>
>> On Wed, Feb 23, 2011 at 3:23 PM, Sameera Jayasoma wrote:
>>
>>>
>>>
>>> On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle  wrote:
>>>
 Can we move to Maven3?

>>>
>>> Since we are doing major changes to Carbon trunk builds, It is better if
>>> we can start working on this migration too.
>>>
>>
>> +1
>>
>>>
>>> Maven3 has improved the performance over Maven2. That is just a single
>>> features. For other improvements, refer [1].
>>>
>>> Maven3 seems be compatible with Maven2 projects. But here are some
>>> reported compatibility issues.
>>>
>>
>> Yes. I tried building Carbon with Maven 3 a little while back and found
>> several incompatibilities. But AFAIU, they are manageable. Most of the
>> problems I faced were related to Parent POM resolution.
>>
>> Thanks and Regards,
>> Harshana
>>
>>>
>>> Thanks
>>> Sameera
>>>
>>> [1]
>>> http://www.developer.com/java/article.php/3908561/Top-10-New-Features-in-Maven-3.htm
>>> [2] https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>>>

 Paul

 On 27 January 2011 11:19, Harshana Martin  wrote:

> Hi All,
>
> On Wed, Dec 22, 2010 at 12:27 PM, Saminda Wijeratne  > wrote:
>
>>
>>
>> On Wed, Dec 22, 2010 at 12:18 PM, Harshana Martin 
>> wrote:
>>
>>> Hi All,
>>>
>>> I came across Eclipse Tycho project[0]. It turned out that, it can
>>> build Eclipse plugins and OSGi bundles using Apache Maven.[1]. Thus we 
>>> can
>>> use it in Carbon Studio. Anyone tried this before?
>>>
>>> I am thinking of this as a solution for getting rid of Ant4Eclipse
>>> which we are currently using to build Carbon Studio. Planning to play 
>>> around
>>> a bit. will keep the list updated.
>>>
>>
> I did some digging in to the Tycho and it turns out that it is capable
> of building p2 sites. But it requires Maven 3 to execute this. Therefore 
> at
> least for the time being, we have to hang around Ant4Eclipse.
>
> Thanks and Regards,
> Harshana
>
>
>>   +1
>>
>> Saminda
>>
>>>
>>>
>>> [0]. http://www.eclipse.org/tycho/
>>> [1].
>>> http://mattiasholmqvist.se/2010/02/building-with-tycho-part-1-osgi-bundles/
>>>
>>> Thanks and Regards,
>>> Harshana
>>> --
>>> Harshana Martin
>>> Software Engineer
>>> WSO2 Inc.
>>> Web:http://wso2.com
>>>
>>> Mobile: +94 716062650
>>> Blog: http://harshana05.blogspot.com
>>> Profile: https://www.google.com/profiles/harshana05
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Harshana Martin
> Software Engineer
> WSO2 Inc.
> Web:http://wso2.com
>   http://wso2.org
>
> Mobile: +94 716062650
> Blog: http://harshana05.blogspot.com
> Profile: https://www.google.com/profiles/harshana05
> Twitter: http://twitter.com/harshana05
>
>
> ___
> Carbon-dev mailing list
> carbon-...@lists.wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


 --
 Paul Fremantle
 CTO and Co-Founder, WSO2
 OASIS WS-RX TC Co-chair, VP, Apache Synapse

 Office: +44 844 484 8143
 Cell: +44 798 447 4618

 blog: http://pzf.fremantle.org
 twitter.com/pzfreo
 p...@wso2.com

 wso2.com Lean Enterprise Middleware

 Disclaimer: This communication may contain privileged or other
 confidential information and is intended exclusively for the addressee/s. 
 If
 you are not the intended recipient/s, or believe that you may have received
 this communication in error, please reply to the sender indicating that 
 fact
 and delete the copy you received and in addition, you should not print,
 copy, retransmit, disseminate, or otherwise use the information contained 
 in
 this communication. Internet communications cannot be guaranteed to be
 timely, secure, error or virus-free. The sender does not accept liability
 for any errors or omissions.

 ___

Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-05-18 Thread Harshana Martin
Hi All,

Andreas,a committer from Axis2 has pointed out to me recently that Axis2
Jenkins Server now run Maven 3. So I don't think it will be a huge problem
for us to migrate too.

Thanks and Regards,
Harshana

On Wed, Feb 23, 2011 at 3:31 PM, Harshana Martin  wrote:

>
>
> On Wed, Feb 23, 2011 at 3:23 PM, Sameera Jayasoma wrote:
>
>>
>>
>> On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle  wrote:
>>
>>> Can we move to Maven3?
>>>
>>
>> Since we are doing major changes to Carbon trunk builds, It is better if
>> we can start working on this migration too.
>>
>
> +1
>
>>
>> Maven3 has improved the performance over Maven2. That is just a single
>> features. For other improvements, refer [1].
>>
>> Maven3 seems be compatible with Maven2 projects. But here are some
>> reported compatibility issues.
>>
>
> Yes. I tried building Carbon with Maven 3 a little while back and found
> several incompatibilities. But AFAIU, they are manageable. Most of the
> problems I faced were related to Parent POM resolution.
>
> Thanks and Regards,
> Harshana
>
>>
>> Thanks
>> Sameera
>>
>> [1]
>> http://www.developer.com/java/article.php/3908561/Top-10-New-Features-in-Maven-3.htm
>> [2] https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>>
>>>
>>> Paul
>>>
>>> On 27 January 2011 11:19, Harshana Martin  wrote:
>>>
 Hi All,

 On Wed, Dec 22, 2010 at 12:27 PM, Saminda Wijeratne 
 wrote:

>
>
> On Wed, Dec 22, 2010 at 12:18 PM, Harshana Martin 
> wrote:
>
>> Hi All,
>>
>> I came across Eclipse Tycho project[0]. It turned out that, it can
>> build Eclipse plugins and OSGi bundles using Apache Maven.[1]. Thus we 
>> can
>> use it in Carbon Studio. Anyone tried this before?
>>
>> I am thinking of this as a solution for getting rid of Ant4Eclipse
>> which we are currently using to build Carbon Studio. Planning to play 
>> around
>> a bit. will keep the list updated.
>>
>
 I did some digging in to the Tycho and it turns out that it is capable
 of building p2 sites. But it requires Maven 3 to execute this. Therefore at
 least for the time being, we have to hang around Ant4Eclipse.

 Thanks and Regards,
 Harshana


>   +1
>
> Saminda
>
>>
>>
>> [0]. http://www.eclipse.org/tycho/
>> [1].
>> http://mattiasholmqvist.se/2010/02/building-with-tycho-part-1-osgi-bundles/
>>
>> Thanks and Regards,
>> Harshana
>> --
>> Harshana Martin
>> Software Engineer
>> WSO2 Inc.
>> Web:http://wso2.com
>>
>> Mobile: +94 716062650
>> Blog: http://harshana05.blogspot.com
>> Profile: https://www.google.com/profiles/harshana05
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


 --
 Harshana Martin
 Software Engineer
 WSO2 Inc.
 Web:http://wso2.com
   http://wso2.org

 Mobile: +94 716062650
 Blog: http://harshana05.blogspot.com
 Profile: https://www.google.com/profiles/harshana05
 Twitter: http://twitter.com/harshana05


 ___
 Carbon-dev mailing list
 carbon-...@lists.wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/carbon-dev


>>>
>>>
>>> --
>>> Paul Fremantle
>>> CTO and Co-Founder, WSO2
>>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>>
>>> Office: +44 844 484 8143
>>> Cell: +44 798 447 4618
>>>
>>> blog: http://pzf.fremantle.org
>>> twitter.com/pzfreo
>>> p...@wso2.com
>>>
>>> wso2.com Lean Enterprise Middleware
>>>
>>> Disclaimer: This communication may contain privileged or other
>>> confidential information and is intended exclusively for the addressee/s. If
>>> you are not the intended recipient/s, or believe that you may have received
>>> this communication in error, please reply to the sender indicating that fact
>>> and delete the copy you received and in addition, you should not print,
>>> copy, retransmit, disseminate, or otherwise use the information contained in
>>> this communication. Internet communications cannot be guaranteed to be
>>> timely, secure, error or virus-free. The sender does not accept liability
>>> for any errors or omissions.
>>>
>>> ___
>>> Carbon-dev mailing list
>>> carbon-...@lists.wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Sameera Jayasoma
>> Technical Lead and Product Manager, WSO2 Carbon
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://tech.jayasoma.org
>>
>> Lean . Enterprise . Middleware
>>
>> __

Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-02-23 Thread Harshana Martin
On Wed, Feb 23, 2011 at 3:23 PM, Sameera Jayasoma  wrote:

>
>
> On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle  wrote:
>
>> Can we move to Maven3?
>>
>
> Since we are doing major changes to Carbon trunk builds, It is better if we
> can start working on this migration too.
>

+1

>
> Maven3 has improved the performance over Maven2. That is just a single
> features. For other improvements, refer [1].
>
> Maven3 seems be compatible with Maven2 projects. But here are some reported
> compatibility issues.
>

Yes. I tried building Carbon with Maven 3 a little while back and found
several incompatibilities. But AFAIU, they are manageable. Most of the
problems I faced were related to Parent POM resolution.

Thanks and Regards,
Harshana

>
> Thanks
> Sameera
>
> [1]
> http://www.developer.com/java/article.php/3908561/Top-10-New-Features-in-Maven-3.htm
> [2] https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>
>>
>> Paul
>>
>> On 27 January 2011 11:19, Harshana Martin  wrote:
>>
>>> Hi All,
>>>
>>> On Wed, Dec 22, 2010 at 12:27 PM, Saminda Wijeratne 
>>> wrote:
>>>


 On Wed, Dec 22, 2010 at 12:18 PM, Harshana Martin wrote:

> Hi All,
>
> I came across Eclipse Tycho project[0]. It turned out that, it can
> build Eclipse plugins and OSGi bundles using Apache Maven.[1]. Thus we can
> use it in Carbon Studio. Anyone tried this before?
>
> I am thinking of this as a solution for getting rid of Ant4Eclipse
> which we are currently using to build Carbon Studio. Planning to play 
> around
> a bit. will keep the list updated.
>

>>> I did some digging in to the Tycho and it turns out that it is capable of
>>> building p2 sites. But it requires Maven 3 to execute this. Therefore at
>>> least for the time being, we have to hang around Ant4Eclipse.
>>>
>>> Thanks and Regards,
>>> Harshana
>>>
>>>
   +1

 Saminda

>
>
> [0]. http://www.eclipse.org/tycho/
> [1].
> http://mattiasholmqvist.se/2010/02/building-with-tycho-part-1-osgi-bundles/
>
> Thanks and Regards,
> Harshana
> --
> Harshana Martin
> Software Engineer
> WSO2 Inc.
> Web:http://wso2.com
>
> Mobile: +94 716062650
> Blog: http://harshana05.blogspot.com
> Profile: https://www.google.com/profiles/harshana05
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>

 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev


>>>
>>>
>>> --
>>> Harshana Martin
>>> Software Engineer
>>> WSO2 Inc.
>>> Web:http://wso2.com
>>>   http://wso2.org
>>>
>>> Mobile: +94 716062650
>>> Blog: http://harshana05.blogspot.com
>>> Profile: https://www.google.com/profiles/harshana05
>>> Twitter: http://twitter.com/harshana05
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> carbon-...@lists.wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Paul Fremantle
>> CTO and Co-Founder, WSO2
>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>
>> Office: +44 844 484 8143
>> Cell: +44 798 447 4618
>>
>> blog: http://pzf.fremantle.org
>> twitter.com/pzfreo
>> p...@wso2.com
>>
>> wso2.com Lean Enterprise Middleware
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s. If
>> you are not the intended recipient/s, or believe that you may have received
>> this communication in error, please reply to the sender indicating that fact
>> and delete the copy you received and in addition, you should not print,
>> copy, retransmit, disseminate, or otherwise use the information contained in
>> this communication. Internet communications cannot be guaranteed to be
>> timely, secure, error or virus-free. The sender does not accept liability
>> for any errors or omissions.
>>
>> ___
>> Carbon-dev mailing list
>> carbon-...@lists.wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Sameera Jayasoma
> Technical Lead and Product Manager, WSO2 Carbon
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Harshana Martin
Software Engineer
WSO2 Inc.
Web:http://wso2.com
  http://wso2.org

Mobile: +94 716062650
Blog: http://harshana05.blogspot.com
Profile: https://www.google.com/profiles/harshana05
Twitter: http://twitter.com/harshana05
___
Carbon-dev mailing list
Carbon-dev@wso2.org

Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-02-23 Thread Sameera Jayasoma
On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle  wrote:

> Can we move to Maven3?
>

Since we are doing major changes to Carbon trunk builds, It is better if we
can start working on this migration too.

Maven3 has improved the performance over Maven2. That is just a single
features. For other improvements, refer [1].

Maven3 seems be compatible with Maven2 projects. But here are some reported
compatibility issues.

Thanks
Sameera

[1]
http://www.developer.com/java/article.php/3908561/Top-10-New-Features-in-Maven-3.htm
[2] https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html

>
> Paul
>
> On 27 January 2011 11:19, Harshana Martin  wrote:
>
>> Hi All,
>>
>> On Wed, Dec 22, 2010 at 12:27 PM, Saminda Wijeratne wrote:
>>
>>>
>>>
>>> On Wed, Dec 22, 2010 at 12:18 PM, Harshana Martin wrote:
>>>
 Hi All,

 I came across Eclipse Tycho project[0]. It turned out that, it can build
 Eclipse plugins and OSGi bundles using Apache Maven.[1]. Thus we can use it
 in Carbon Studio. Anyone tried this before?

 I am thinking of this as a solution for getting rid of Ant4Eclipse which
 we are currently using to build Carbon Studio. Planning to play around a
 bit. will keep the list updated.

>>>
>> I did some digging in to the Tycho and it turns out that it is capable of
>> building p2 sites. But it requires Maven 3 to execute this. Therefore at
>> least for the time being, we have to hang around Ant4Eclipse.
>>
>> Thanks and Regards,
>> Harshana
>>
>>
>>>   +1
>>>
>>> Saminda
>>>


 [0]. http://www.eclipse.org/tycho/
 [1].
 http://mattiasholmqvist.se/2010/02/building-with-tycho-part-1-osgi-bundles/

 Thanks and Regards,
 Harshana
 --
 Harshana Martin
 Software Engineer
 WSO2 Inc.
 Web:http://wso2.com

 Mobile: +94 716062650
 Blog: http://harshana05.blogspot.com
 Profile: https://www.google.com/profiles/harshana05


 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev


>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Harshana Martin
>> Software Engineer
>> WSO2 Inc.
>> Web:http://wso2.com
>>   http://wso2.org
>>
>> Mobile: +94 716062650
>> Blog: http://harshana05.blogspot.com
>> Profile: https://www.google.com/profiles/harshana05
>> Twitter: http://twitter.com/harshana05
>>
>>
>> ___
>> Carbon-dev mailing list
>> carbon-...@lists.wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>
> Office: +44 844 484 8143
> Cell: +44 798 447 4618
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> p...@wso2.com
>
> wso2.com Lean Enterprise Middleware
>
> Disclaimer: This communication may contain privileged or other confidential
> information and is intended exclusively for the addressee/s. If you are not
> the intended recipient/s, or believe that you may have received this
> communication in error, please reply to the sender indicating that fact and
> delete the copy you received and in addition, you should not print, copy,
> retransmit, disseminate, or otherwise use the information contained in this
> communication. Internet communications cannot be guaranteed to be timely,
> secure, error or virus-free. The sender does not accept liability for any
> errors or omissions.
>
> ___
> Carbon-dev mailing list
> carbon-...@lists.wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev


Re: [Carbon-dev] Using Tycho for building Carbon Studio

2011-01-27 Thread Danushka Menikkumbura
Even Maven2, only 2.1.0 (which is not the latest Maven2) works.

Danushka

On Thu, Jan 27, 2011 at 5:50 PM, Harshana Martin  wrote:

> Hi Paul,
>
> On Thu, Jan 27, 2011 at 5:28 PM, Paul Fremantle  wrote:
>
>> Can we move to Maven3?
>>
>
> I did try to build the tools trunk using Maven 3. I was able to build some
> of the plugins using Maven 3 without any issue, but some of them failed due
> to certain incompatibilities (mainly parent pom declaration issues) between
> Maven 2 pom model elements with Maven3. I will try to solve it. Meanwhile
> I'll give a try to build Carbon trunk with Maven 3 as well.
>
> Thanks and Regards,
> Harshana
>
>>
>> Paul
>>
>> On 27 January 2011 11:19, Harshana Martin  wrote:
>>
>>>  Hi All,
>>>
>>> On Wed, Dec 22, 2010 at 12:27 PM, Saminda Wijeratne 
>>> wrote:
>>>


 On Wed, Dec 22, 2010 at 12:18 PM, Harshana Martin wrote:

> Hi All,
>
> I came across Eclipse Tycho project[0]. It turned out that, it can
> build Eclipse plugins and OSGi bundles using Apache Maven.[1]. Thus we can
> use it in Carbon Studio. Anyone tried this before?
>
> I am thinking of this as a solution for getting rid of Ant4Eclipse
> which we are currently using to build Carbon Studio. Planning to play 
> around
> a bit. will keep the list updated.
>

>>> I did some digging in to the Tycho and it turns out that it is capable of
>>> building p2 sites. But it requires Maven 3 to execute this. Therefore at
>>> least for the time being, we have to hang around Ant4Eclipse.
>>>
>>> Thanks and Regards,
>>> Harshana
>>>
>>>
   +1

 Saminda

>
>
> [0]. http://www.eclipse.org/tycho/
> [1].
> http://mattiasholmqvist.se/2010/02/building-with-tycho-part-1-osgi-bundles/
>
> Thanks and Regards,
> Harshana
> --
> Harshana Martin
> Software Engineer
> WSO2 Inc.
> Web:http://wso2.com
>
> Mobile: +94 716062650
> Blog: http://harshana05.blogspot.com
> Profile: https://www.google.com/profiles/harshana05
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>

 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev


>>>
>>>
>>> --
>>> Harshana Martin
>>> Software Engineer
>>> WSO2 Inc.
>>> Web:http://wso2.com
>>>   http://wso2.org
>>>
>>> Mobile: +94 716062650
>>> Blog: http://harshana05.blogspot.com
>>> Profile: https://www.google.com/profiles/harshana05
>>> Twitter: http://twitter.com/harshana05
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> carbon-...@lists.wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Paul Fremantle
>> CTO and Co-Founder, WSO2
>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>
>> Office: +44 844 484 8143
>> Cell: +44 798 447 4618
>>
>> blog: http://pzf.fremantle.org
>> twitter.com/pzfreo
>> p...@wso2.com
>>
>> wso2.com Lean Enterprise Middleware
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s. If
>> you are not the intended recipient/s, or believe that you may have received
>> this communication in error, please reply to the sender indicating that fact
>> and delete the copy you received and in addition, you should not print,
>> copy, retransmit, disseminate, or otherwise use the information contained in
>> this communication. Internet communications cannot be guaranteed to be
>> timely, secure, error or virus-free. The sender does not accept liability
>> for any errors or omissions.
>>
>> ___
>> Carbon-dev mailing list
>> carbon-...@lists.wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Harshana Martin
> Software Engineer
> WSO2 Inc.
> Web:http://wso2.com
>   http://wso2.org
>
> Mobile: +94 716062650
> Blog: http://harshana05.blogspot.com
> Profile: https://www.google.com/profiles/harshana05
> Twitter: http://twitter.com/harshana05
>
>
> ___
> Carbon-dev mailing list
> carbon-...@lists.wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev


Re: [Carbon-dev] Using Tycho for building Carbon Studio

2010-12-21 Thread Saminda Wijeratne
On Wed, Dec 22, 2010 at 12:18 PM, Harshana Martin  wrote:

> Hi All,
>
> I came across Eclipse Tycho project[0]. It turned out that, it can build
> Eclipse plugins and OSGi bundles using Apache Maven.[1]. Thus we can use it
> in Carbon Studio. Anyone tried this before?
>
> I am thinking of this as a solution for getting rid of Ant4Eclipse which we
> are currently using to build Carbon Studio. Planning to play around a bit.
> will keep the list updated.
>
+1

Saminda

>
>
> [0]. http://www.eclipse.org/tycho/
> [1].
> http://mattiasholmqvist.se/2010/02/building-with-tycho-part-1-osgi-bundles/
>
> Thanks and Regards,
> Harshana
> --
> Harshana Martin
> Software Engineer
> WSO2 Inc.
> Web:http://wso2.com
>
> Mobile: +94 716062650
> Blog: http://harshana05.blogspot.com
> Profile: https://www.google.com/profiles/harshana05
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev