Hi Supun,

On Sat, Jul 2, 2011 at 9:38 AM, Supun Malinga <[email protected]> wrote:

> Hi Amila,
>
> On Sat, Jul 2, 2011 at 9:29 AM, Amila Suriarachchi <[email protected]> wrote:
>
>>
>>
>> On Fri, Jul 1, 2011 at 9:38 AM, Supun Malinga <[email protected]> wrote:
>>
>>> Hi folks,
>>>
>>> Please make sure you have added relative paths in the
>>> components,features, etc.
>>> Otherwise you can't build 3.2.1 patch-release pom in a clean repo.
>>>
>>>
>>>    - How to do this,
>>>
>>> Lets take the system-statistics module. There packaging structure is as
>>> follows.
>>>
>>> components/system-statistics$ tree -L 3
>>>
>>> |-- org.wso2.carbon.statistics
>>>
>>> |   |-- 3.2.0
>>>
>>> |   |   |-- pom.xml
>>>
>>> |   |   |-- src
>>>
>>> |   |   `-- target
>>>
>>> |   `-- 3.2.1
>>>
>>> |       |-- pom.xml
>>>
>>> |       |-- src
>>>
>>> |       `-- target
>>>
>>> |-- org.wso2.carbon.statistics.ui
>>>
>>> |   `-- 3.2.0
>>>
>>> |       |-- pom.xml
>>>
>>> |       |-- src
>>>
>>> |       `-- target
>>>
>>> |-- pom.xml
>>>
>>>
>>>
>>> So in the *
>>> components/system-statistics/org.wso2.carbon.statistics/3.2.1/pom.xml*,
>>> you need to add the relative paths for the parent pom which is the, *
>>> components/system-statistics/pom.xml.*
>>> It would be like,
>>>
>>>   <parent>
>>>         <groupId>org.wso2.carbon</groupId>
>>>         <artifactId>system-statistics</artifactId>
>>>         <version>3.2.0</version>
>>>         <relativePath>../../pom.xml</relativePath>
>>>     </parent>
>>>
>>>
>>>
>>>
>>>    - How to test if this works
>>>
>>>
>>>    1. back up your existing .m2 repo (or clean the m2 repo) or
>>>    remove/move  components/system-statistics/pom.xml from the m2 repo.
>>>    2. goto *
>>>    components/system-statistics/org.wso2.carbon.statistics/3.2.1/* and
>>>    'mvn clean install'
>>>
>>>
>> shouldn't this suppose to work. since parent pom i.e 3.2.0 should have
>> been in the maven repos?
>>
>
> yes it does, but then we have to add the repositories to each of these
> poms, cos' we do not build from the top to bottom in the patch release poms.
> (What we do in the patch-release poms is, going into each module directory
> and build from there.)
>

With the new structure in the patch-release folder, it is similar to our
carbon folder struccture, right? In that case, adding the nexus repo to
patch-release root pom wont work?

AmilaM.

>
> thanks,
>
>>
>> thanks,
>> Amila.
>>
>>>
>>> *Please verify all your components that was added into 3.2.1 release.*
>>>
>>> thanks n regards,
>>> --
>>> Supun Malinga,
>>>
>>> Software Engineer,
>>> WSO2 Inc.
>>> http://wso2.com
>>> http://wso2.org
>>> email - [email protected] <[email protected]>
>>> mobile - 071 56 91 321
>>>
>>>
>>> _______________________________________________
>>> Carbon-dev mailing list
>>> [email protected]
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> [email protected]
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Supun Malinga,
>
> Software Engineer,
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
> email - [email protected] <[email protected]>
> mobile - 071 56 91 321
>
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to