Re: [Carbon-dev] Maven3 migration in carbon-trunk

2011-10-25 Thread Afkham Azeez
Pradeep,
Did you ever try a mvn clean install from the
https://svn.wso2.org/repos/wso2/trunk/carbon level?

On Thu, Sep 1, 2011 at 5:39 PM, Pradeep Fernando prad...@wso2.com wrote:

 Hi,

 Small tip :

 if you get build failure while doing a build, you can continue the
 build from failed module by using the resume option.

 In the maven3 build failure description it gives the command to resume
 the build from the failed location. the command is

 mvn clean install -rf :module to resume from

 hth,
 --Pradeep
 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev




-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/**
email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
blog: **http://blog.afkham.org* http://blog.afkham.org*
twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev


Re: [Carbon-dev] Maven3 migration in carbon-trunk

2011-10-25 Thread Pradeep Fernando
hi,

right now , you cant do that. I would have fixed it, but i dont have the
knowledge of individual packaging of products. I fixed it for the products
that im most familiar with, which is Carbon and Appserver. Some of the
product teams fixed their product level things. But some did not. Cant blame
them since we were in release mode.

this is a kind of major change. But we needed it.

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


Re: [Carbon-dev] Maven3 migration in carbon-trunk

2011-10-25 Thread Pradeep Fernando
Hi,

Actually now i remember that I do fixed it to build it from the root pom in
kind of hacky way. In fact we had hudson build job that builds trunk with
maven3. The default build profile did not include product level. after the
root pom build you had to go inside the relevant product and build it.

hudson is down and i dont have an idea about the build state of the trunk
right now.

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


Re: [Carbon-dev] Maven3 migration in carbon-trunk

2011-09-01 Thread Pradeep Fernando
Hi devs,


Now the trunk is maven3 compatible up to features level. Please make
your product builds maven3 compatible. Refer to the wiki page given
above for more information. I have taken care of Carbon and AS.

Due to this migration carbon-trunk will not work with maven2 anymore
(99% of the time it is compatible, at least for now). Please make sure
that you build with maven3 before committing to the trunk (only if
there is a pom change)

please talk to me if you are having any problems. Willing to help you.

thanks,
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev


Re: [Carbon-dev] Maven3 migration in carbon-trunk

2011-09-01 Thread Pradeep Fernando
Hi,

Small tip :

if you get build failure while doing a build, you can continue the
build from failed module by using the resume option.

In the maven3 build failure description it gives the command to resume
the build from the failed location. the command is

mvn clean install -rf :module to resume from

hth,
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev


[Carbon-dev] Maven3 migration in carbon-trunk

2011-08-31 Thread Pradeep Fernando
Hi,

I started the $subject some time ago and now it is ready up to
features level. (infact Appserver is maven3 compatible). Withing next
day or two the trunk will be moved to maven3 completely.

After that you need to have both maven2 and maven3 installed if you
are working on bother carbon-branches and carbon-trunk
interchangeably. No changes when it comes to local maven repo. It will
be .m2 as usual.

I may need the help of individual product teams while migrating the
product level builds. Will let you know shortly.

thanks,
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev


Re: [Carbon-dev] Maven3 migration in carbon-trunk

2011-08-31 Thread Sameera Jayasoma
On Wed, Aug 31, 2011 at 1:35 PM, Pradeep Fernando prad...@wso2.com wrote:

 Hi,

 I started the $subject some time ago and now it is ready up to
 features level. (infact Appserver is maven3 compatible). Withing next
 day or two the trunk will be moved to maven3 completely.

 After that you need to have both maven2 and maven3 installed if you
 are working on bother carbon-branches and carbon-trunk
 interchangeably. No changes when it comes to local maven repo. It will
 be .m2 as usual.

 I may need the help of individual product teams while migrating the
 product level builds. Will let you know shortly.


+1. Pradeep, please send information on how to update product pom files for
Maven 3 migration. Once the all the information is available, product teams
can update their products.

Thanks,
Sameera.


 thanks,
 --Pradeep
 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 http://mail.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] Maven3 migration in carbon-trunk

2011-08-31 Thread Pradeep Fernando
Hi,

The main difference is in maven site plugin. Maven3 poms should not
contain reporting element. Instead they should be placed in the
reportPlugins element in the site plugin configuration. [1]

recommended versions for the plugins,

maven-site-plugin  : 3.0
maven-project-info-plugin : 2.4
maven-javadoc-plugin : 2.8

apart from that maven3 is strict on duplicated modules, parent
resolution (fixing these are trivial as the error messages are
descriptive)

[1] 
https://cwiki.apache.org/MAVEN/maven-3x-site-plugin-migration-from-maven-2x.html

thanks,
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev