I have tried working on that but it did not work in reading the feature.xml
file and copying the relevant jars.

it is doable though. It should be easier to read it from a text file and
copy the jars.

Regards
Awanthika

Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Mon, Feb 1, 2016 at 3:27 PM, Rajeeva Uthayasangar <raje...@wso2.com>
wrote:

>
>
> On Mon, Feb 1, 2016 at 3:15 PM, Susinda Perera <susi...@wso2.com> wrote:
>
>>
>>
>> On Mon, Feb 1, 2016 at 2:04 PM, Rajeeva Uthayasangar <raje...@wso2.com>
>> wrote:
>>
>>> Hi Nuwan,
>>>
>>> Please follow the steps:
>>>
>>> 1) Build the product with fix.
>>> 2) Navigate to below location in builder machine and create a folder
>>> called "feature-updater" inside the product where the fix should be applied.
>>> /home/developerstudio/wso2/developer-studio/
>>>
>>> for example:if the fix is for ESB , then navigate to
>>>  /home/developerstudio/wso2/developer-studio/esb and create the folder
>>> called "feature-updater" in it.
>>> 3) then create the two folders  as features and plugins inside
>>> feature-updater folder.
>>>
>> @ Rajeewa : I think we can automate these folder creation in the
>> publish.sh script
>>
>
> If we automate the folder creation, we need to automate the copying jars
> part as well. In that case, we need to point the location  and name of the
> jars. Those we can give a text file and read from there.
>
>>
>>
>>> 4) then add the feature jar to the features folder and the plugin jars
>>> related to the feature inside the plugins folder.
>>> 5) Extract a eclipse distribution and give it's path as eclipse_home in
>>> the publish.sh script
>>> 6) Execute the script
>>> 7) while it runs, it asks for the feature. Give the feature name without
>>> the version
>>>
>> But we have to make sure the version is correct in the script. (This will
>> work for 4.0.0 but if you use the same script without modifying for a new
>> version, this will not work)
>>
>>
>>> 8) Script will create a newP2 which will contain p2 of the fix
>>> 9) then navigate to the below location. Create a folder with patch
>>> number under updates. Please note, below location points to esb.
>>>
>>> /home/developerstudio/public_html/developer-studio-kernel/4.0.0/esb-tools/updates
>>> 10) Copy the p2 (which is created in step 8) inside the newly created
>>> patch folder
>>> 11)then update the compositeArtifacts.xml and compositeContent.xml to
>>> add the new patch folder
>>>
>>> thanks
>>> Rajeeva.
>>>
>>> On Mon, Feb 1, 2016 at 12:52 PM, Nuwan Pallewela <nuw...@wso2.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> What is the process for adding improvements done for a patch, to
>>>> Developer Studio update site?
>>>>
>>>> Thanks,
>>>> Nuwan
>>>>
>>>> --
>>>> ----------------------------------------------------------
>>>>
>>>> *Nuwan Chamara Pallewela*
>>>>
>>>>
>>>> *Software Engineer*
>>>>
>>>> *WSO2, Inc. *http://wso2.com
>>>> *lean . enterprise . middleware*
>>>>
>>>> Email   *nuw...@wso2.com <nuw...@wso2.com>*
>>>> Mobile  *+94719079739 <%2B94719079739>@*
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Rajeeva Uthayasangar*
>>> Software Engineer
>>> WSO2, Inc.:http://wso2.com
>>>
>>>
>>> Mobile: +94777298873
>>>
>>>
>>
>>
>> --
>> *Susinda Perera*
>> Software Engineer
>> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
>> Mobile:(+94)716049075
>> Blog: susinda.blogspot.com
>> WSO2 Inc. http://wso2.com/
>> Tel : 94 11 214 5345 Fax :94 11 2145300
>>
>>
>
>
> --
> *Rajeeva Uthayasangar*
> Software Engineer
> WSO2, Inc.:http://wso2.com
>
>
> Mobile: +94777298873
>
>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to