Hey guys. I'm trying to compile AOSP for our device, but I keep running into problems. I try to add the local manifest but I keep getting an error. The error is:
HTML:
fatal: error parsing manifest /home/iacevedo/aosp/.repo/local_manifests/local_manifest.xml: duplicate attribute: line 7, column 61
My manifest his this:
HTML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github"
fetch="https://github.com/" />
<project path="Cyanogenmod/android_device_motorola_quark" path="devices/motorola/quark" remote="github" revision="cm-12.1"/>
<project path="Cyanogenmod/android_kernel_motorola_apq8084" path="kernel/motorola/quark" remote="github" revision="cm-12.1" />
<project path="bhb27/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="RR-12/12-LP" />
</manifest>
I have limited knowledge in compiling so if someone can help me it would be very appreciated.
Edit: Forgot error. Sorry. Also updated manifest to have github as remote and added proprietary files.
izzy001 said:
Hey guys. I'm trying to compile AOSP for our device, but I keep running into problems. I try to add the local manifest but I keep getting an error. The error is:
HTML:
fatal: error parsing manifest /home/iacevedo/aosp/.repo/local_manifests/local_manifest.xml: duplicate attribute: line 7, column 61
My manifest his this:
HTML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github"
fetch="https://github.com/" />
<project path="Cyanogenmod/android_device_motorola_quark" path="devices/motorola/quark" remote="github" revision="cm-12.1"/>
<project path="Cyanogenmod/android_kernel_motorola_apq8084" path="kernel/motorola/quark" remote="github" revision="cm-12.1" />
<project path="bhb27/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="RR-12/12-LP" />
</manifest>
I have limited knowledge in compiling so if someone can help me it would be very appreciated.
Edit: Forgot error. Sorry. Also updated manifest to have github as remote and added proprietary files.
Click to expand...
Click to collapse
what source is that?
your file is wrong, It should be...
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_kernel_motorola_apq8084" path="kernel/motorola/apq8084" remote="github" revision="cm-12.1" />
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-12.1" />
</manifest>
the vendor for Motorola device is TheMuppets that is the stable one, you can use my but I change too much and in some point in time I may let a nonfunctional tree on my git plus I may delete/change the name of that branch any day, but TheMuppets will never do that because that is the one used by CM server to build and is 100% stable.
you do not put device tree on the manifest that is personal, you must have your one make changes and publish that to your one github, some source is not compatible with CM that is way I ask the source...
If the source is not CM base it will require a lot of dev skills because you will need to change almost all the device tree to make it work, as the only device tree that exist today is CM.
baybutcher27 said:
what source is that?
your file is wrong, It should be...
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_kernel_motorola_apq8084" path="kernel/motorola/apq8084" remote="github" revision="cm-12.1" />
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-12.1" />
</manifest>
the vendor for Motorola device is TheMuppets that is the stable one, you can use my but I change too much and in some point in time I may let a nonfunctional tree on my git plus I may delete/change the name of that branch any day, but TheMuppets will never do that because that is the one used by CM server to build and is 100% stable.
you do not put device tree on the manifest that is personal, you must have your one make changes and publish that to your one github, some source is not compatible with CM that is way I ask the source...
If the source is not CM base it will require a lot of dev skills because you will need to change almost all the device tree to make it work, as the only device tree that exist today is CM.
Click to expand...
Click to collapse
Thanks, I don't get that error anymore! The sources were just some I had found from around the forum. I'm going to switch to a Ubuntu based distro because I'm having some errors with my Java. Any you recommend?
izzy001 said:
Thanks, I don't get that error anymore! The sources were just some I had found from around the forum. I'm going to switch to a Ubuntu based distro because I'm having some errors with my Java. Any you recommend?
Click to expand...
Click to collapse
I use google recommendation... Ubuntu 14.04 64bits.
http://source.android.com/source/initializing.html
if you need let me know I like to see more ROM for quark... :good:
Ok so I'm working on this on my free time, in between two jobs. On the manifest, I don't need the device tree? Or do I have to build that myself?
izzy001 said:
Ok so I'm working on this on my free time, in between two jobs. On the manifest, I don't need the device tree? Or do I have to build that myself?
Click to expand...
Click to collapse
you can but only if the source is 100% CM compatible and if you don't plan to make the ROM with your taste, CM is vary basic there is a lot to add or remove from it, plus most source are not 100% compatible they need changes to the device tree to make it work, to know if you need to change you can try and have a error or you look for other devices tree that use that source and look for the changes that they make to work almost all device tree start by forking CM tree.
so you fork CM tree, clone to your machine make the changes and publish it to your github account, just search github basic tings clone commit etc, you will find all the command and things related, XDA and google have it all just search.
Related
Hello, users.
I want to ask you if someone can explain me a step to build cm 11
well, I have prepared everything but i just have to know what means "Obtain the proprietary files"
so as a example in the guide i have "$ breakfast mako"
so instead of that i just say "breakfast trebon"?
Well and after that i have this step:
"Then create a file with the name local_manifest.xml in the local_manifests directory. To see this directory, you have to press Ctrl-H in your file manager.
Use this code:
Code:
$ gedit ~/cm11/.repo/local_manifests/local_manifest.xml" (this is a example for nexus)
i say all this because i think somewhere i have to use TheWhisp's sources, right? atleast that is what we did with 4.3 and pac man, carbon...
as yazidkucrit and TechKang are working on building cm 11 and i'm doing my best, maybe we could get it after all this waiting, right?
so don't say this device is lost and there is no further development for us
ShadowsDie said:
Hello, users.
I want to ask you if someone can explain me a step to build cm 11
well, I have prepared everything but i just have to know what means "Obtain the proprietary files"
so as a example in the guide i have "$ breakfast mako"
so instead of that i just say "breakfast trebon"?
Well and after that i have this step:
"Then create a file with the name local_manifest.xml in the local_manifests directory. To see this directory, you have to press Ctrl-H in your file manager.
Use this code:
Code:
$ gedit ~/cm11/.repo/local_manifests/local_manifest.xml" (this is a example for nexus)
i say all this because i think somewhere i have to use TheWhisp's sources, right? atleast that is what we did with 4.3 and pac man, carbon...
as yazidkucrit and TechKang are working on building cm 11 and i'm doing my best, maybe we could get it after all this waiting, right?
so don't say this device is lost and there is no further development for us
Click to expand...
Click to collapse
You guys didn't replied me at all but thanks anyway if you tried and thanks to @ptanmay143 for his help as well
but Snypercell, a very kind person from here, finnaly helped me with this step
This is the solution for the rest of developers that didn't knew this;
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CM replacements -->
<remove-project name="CyanogenMod/android_frameworks_native" />
<project path="frameworks/native" name="omnirom/android_frameworks_native" revision="android-4.4" />
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
<!-- FM Radio -->
<project path="hardware/qcom/fm" name="legaCyMod/android_hardware_qcom_fm" revision="cm-11.0" />
<project path="packages/apps/FM2" name="legaCyMod/android_packages_apps_FM2" revision="cm-11.0" />
</manifest>
Then: brunch trebon
Today i will try ubuntu LTS as 13.10 gives me kernel errors, hope it works with LTS
ShadowsDie said:
You guys didn't replied me at all but thanks anyway if you tried and thanks to @ptanmay143 for his help as well
but Snypercell, a very kind person from here, finnaly helped me with this step
This is the solution for the rest of developers that didn't knew this;
Then: brunch trebon
Today i will try ubuntu LTS as 13.10 gives me kernel errors, hope it works with LTS
Click to expand...
Click to collapse
Most of us are not dev sorry, you, yazid, Tech and The whisp is our only hope. Have you heard of vicky? We never seen him a couple of weeks, did he leave or developing or something for us?:what::what::beer:
ANDROID-000 said:
Most of us are not dev sorry, you, yazid, Tech and The whisp is our only hope. Have you heard of vicky? We never seen him a couple of weeks, did he leave or developing or something for us?:what::what::beer:
Click to expand...
Click to collapse
i wasn't trying to be rude sry
yazid and Tech are developing cm 11 and TheWhisp im pretty sure he will not help us in the near present.
I'm not a developer as well but i'm trying to learn how to as this is how i spend my free time and i do something useful
i actually don't know if i will accomplish something and i'm sure Tech or yazid will finish first
and i dont know nothing of vicky, its so bad if he left as he has a better acknoweledge in developing than me
ANDROID-000 said:
Most of us are not dev sorry, you, yazid, Tech and The whisp is our only hope. Have you heard of vicky? We never seen him a couple of weeks, did he leave or developing or something for us?:what::what::beer:
Click to expand...
Click to collapse
Absolute right
ShadowsDie said:
i wasn't trying to be rude sry
yazid and Tech are developing cm 11 and TheWhisp im pretty sure he will not help us in the near present.
I'm not a developer as well but i'm trying to learn how to as this is how i spend my free time and i do something useful
i actually don't know if i will accomplish something and i'm sure Tech or yazid will finish first
and i dont know nothing of vicky, its so bad if he left as he has a better acknoweledge in developing than me
Click to expand...
Click to collapse
Read The whisp github, i think our device is included in his kikat project:thumbup: hope it will.
Yeah, vicky had no update in his thread or even post a reply.
ANDROID-000 said:
Read The whisp github, i think our device is included in his kikat project:thumbup: hope it will.
Yeah, vicky had no update in his thread or even post a reply.
Click to expand...
Click to collapse
but the whisp isnt replying to any one using ace plus or posting questions about our device..techkang and yazid are the only hopes for now...
Happy new year developers..:good:
ShadowsDie said:
Hello, users.
I want to ask you if someone can explain me a step to build cm 11
well, I have prepared everything but i just have to know what means "Obtain the proprietary files"
so as a example in the guide i have "$ breakfast mako"
so instead of that i just say "breakfast trebon"?
Well and after that i have this step:
"Then create a file with the name local_manifest.xml in the local_manifests directory. To see this directory, you have to press Ctrl-H in your file manager.
Use this code:
Code:
$ gedit ~/cm11/.repo/local_manifests/local_manifest.xml" (this is a example for nexus)
i say all this because i think somewhere i have to use TheWhisp's sources, right? atleast that is what we did with 4.3 and pac man, carbon...
as yazidkucrit and TechKang are working on building cm 11 and i'm doing my best, maybe we could get it after all this waiting, right?
so don't say this device is lost and there is no further development for us
Click to expand...
Click to collapse
CM11 is already builded...
danyznd123 said:
CM11 is already builded...
Click to expand...
Click to collapse
not for ace plus...
ShadowsDie said:
not for ace plus...
Click to expand...
Click to collapse
All cm roms are not stable and i don't recommend to flash them...
If you want a good custom rom flash inspiration rom by kk9999gada that have no bugs...
danyznd123 said:
All cm roms are not stable and i don't recommend to flash them...
If you want a good custom rom flash inspiration rom by kk9999gada that have no bugs...
Click to expand...
Click to collapse
thanks for the very obvious advice
Hi everybody,
a week ago, I started to try to port Firefox OS on our device. I download everything, and I follow this guide. The problem is there. I use this manifest for falcon :
Code:
<?xml version="1.0" ?><manifest>
<include name="base-kk.xml"/>
<default remote="caf" revision="refs/tags/android-4.4.2_r1" sync-j="4"/>
<remote fetch="git://github.com/CyanogenMod/" name="cm"/>
<!-- Falcon specific things -->
<project name="android_device_qcom_common" path="device/qcom/common" remote="cm" revision="cm-11.0"/>
<project name="android_device_motorola_qcom-common" path="device/motorola/qcom-common" remote="cm" revision="cm-11.0"/>
<project name="android_device_motorola_falcon" path="device/motorola/falcon" remote="cm" revision="cm-11.0"/>
<project name="android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="cm" revision="cm-11.0"/>
<project name="android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="cm" revision="cm-11.0"/>
<project name="android_hardware_qcom_display-caf-new" path="hardware/qcom/display-caf-new" remote="cm" revision="cm-11.0"/>
<project name="android_hardware_qcom_media-caf-new" path="hardware/qcom/media-caf-new" remote="cm" revision="cm-11.0"/>
<project name="android_hardware_qcom_fm" path="hardware/qcom/fm" remote="cm" revision="cm-11.0"/>
<project name="platform_system_nfcd" path="system/nfcd" remote="b2g" revision="master"/>
</manifest>
Which is pretty strange. And the next parts failed ... I build boot.img ... Adapted config.sh BUT nothing works well !
The problem is the manifest .. so can anybody help my to build a new one ?
I thinking about using CyanogenMod's Github ! Nope ?
UPDATE :
Code:
<?xml version="1.0" ?><manifest>
<include name="base-kk.xml"/>
<default remote="caf" revision="refs/tags/android-4.4.2_r1" sync-j="4"/>
<remote fetch="git://github.com/CyanogenMod" name="cm"/>
<!-- Falcon specific things -->
<project name="android_device_motorola_falcon" path="device/motorola/falcon" remote="cm" revision="cm-11.0"/>
<project name="device/generic/armv7-a-neon" path="device/generic/armv7-a-neon"/>
<project name="android_kernel_motorola_msm8226" path="hardware/qcom/msm8226" remote="cm" revision="cm-11.0"/>
<project name="platform/external/libnfc-nci" path="external/libnfc-nci"/>
<project name="platform/external/wpa_supplicant_8" path="external/wpa_supplicant_8"/>
<project name="platform/hardware/broadcom/wlan" path="hardware/broadcom/wlan"/>
<project name="android_hardware_qcom_audio-caf" path="hardware/qcom/audio" remote="cm" revision="cm-11.0"/>
<project name="platform/hardware/qcom/camera" path="hardware/qcom/camera"/>
<project name="android_hardware_qcom_display-caf-new" path="hardware/qcom/display" remote="cm" revision="cm-11.0"/>
<project name="platform/hardware/qcom/keymaster" path="hardware/qcom/keymaster"/>
<project name="android_hardware_qcom_media-caf-new" path="hardware/qcom/media" remote="cm" revision="cm-11.0"/>
<project name="platform/hardware/qcom/power" path="hardware/qcom/power"/>
<project name="platform/hardware/qcom/sensors" path="hardware/qcom/sensors"/>
<project name="platform/hardware/qcom/wlan" path="hardware/qcom/wlan"/>
<project name="platform/hardware/ril" path="hardware/ril"/>
<project name="platform_system_nfcd" path="system/nfcd" remote="b2g" revision="master"/>
</manifest>
I made that, what do you thnk about it ?
Thanks you sooooooooooooooooo much !
PS : Sorry for my bad english
P-PS : If this project work great ... I would create A NIGHTLY BUILD of Firefox Os on Moto G (XT1032)
Building
I've never builded (but tried to),but i have some clues
i assume u followed this link to build
https://developer.mozilla.org/en-US/Firefox_OS/Porting
You can ask some questions here,maybe they will know
https://groups.google.com/forum/#!forum/mozilla.dev.b2g
This guide for manifest
http://forum.xda-developers.com/showpost.php?p=40003302&postcount=2
Anyway way to go and best of luck!
I've never builded (but tried to),but i have some clues
i assume u followed this link to build
https://developer.mozilla.org/en-US/Firefox_OS/Porting
You can ask some questions here,maybe they will know
https://groups.google.com/forum/#!forum/mozilla.dev.b2g
This guide for manifest
http://forum.xda-developers.com/show...02&postcount=2
Anyway way to go and best of luck!
Click to expand...
Click to collapse
I know those things but thank you very much guy
That learn me how to create a manifest, wich isn't a problem, the exact problem is : wich files go where, and wich files are useless ! I thinking about managing every Cynaogenmod code.
What do you think about it ?
xmattjus said:
Try to put those https://github.com/razrqcom-dev-team/android_local_razrqcom in the .repo/local_manifests folder. Particularly you need the vendor.xml file. For what I understood while building anything from sources you can't put all the repos you need in a single xml file.
I hope you understand what I mean.. xD
Click to expand...
Click to collapse
Look at this ! The manifest is very particular :/ I'm inspiratting by the Nexus 5's one.
There aren't like the razrqcom-dev-team's ones.
Thanks for you reply !
Hey guys!
I've been seaching now for some time in order to find a ready-to-build source tree for my GT-I8262. I found several entries on github but unfortunately I got compilation errors for all of them. The most promising one was the approach of ankur850 which he explained himself here.
In order to get rid of some of the errors, I changed the following points in the .repo/local_manifests/roomservice.xml:
Inserted remove-project in order to resolve the conflict with the existing repository by Cyanogenmod.
Changed the path kernel/samsung/arubaslim to kernel/samsung/msm7x27a
Removed the revision attribute for those repositories having a later branch (since I tried to build cm-11.0)
resulting in the following xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="ankur850/android_device_samsung_arubaslim" path="device/samsung/arubaslim" remote="github" />
<project name="ankur850/android_vendor_qcom_msm7x27a" path="vendor/qcom/msm7x27a" remote="github" revision="cm-10.2" />
<project name="ankur850/android_device_qcom_msm7x27a" path="device/qcom/msm7x27a" remote="github" revision="cm-10.2" />
<project name="ankur850/android_vendor_samsung_arubaslim" path="vendor/samsung/arubaslim" remote="github" revision="cm-10.2" />
<project name="ankur850/android_hardware_qcom_display-legacy" path="hardware/qcom/display-legacy" remote="github" revision="jellybean-mr2" />
<remove-project name="CyanogenMod/android_hardware_qcom_audio-caf" revision="cm-10.2" />
<project name="ankur850/android_hardware_qcom_audio-caf" path="hardware/qcom/audio-caf" remote="github" revision="cm-10.2" />
<project name="ankur850/android_kernel_samsung_msm7x27a" path="kernel/samsung/msm7x27a" remote="github" />
</manifest>
When compiling (brunch arubaslim), I get the following error - which seems to be related to the repository:
Code:
make: *** No rule to make target `frameworks/base/data/etc/com.stericsson.hardware.fm.receiver.xml', needed by `~/android/system/out/target/product/arubaslim/system/etc/permissions/com.stericsson.hardware.fm.receiver.xml'. Stop.
I would appreciate very much if someone could point a working CM11 (if possible CM12) source tree out to me (or even help me to build with this one).
@admin: If a forum moderator/admin happens to be reading this, I would appreciate very much if you could integrate an overview for source trees like you did for ROMs and kernels.
Many thanks!
There is no com.stericsson.hardware.fm.receiver.xml
In framework/base/data/etc as I recall. Check again if its not there than there is no rule to make it.
Y300-0100 said:
There is no com.stericsson.hardware.fm.receiver.xml
In framework/base/data/etc as I recall. Check again if its not there than there is no rule to make it.
Click to expand...
Click to collapse
Thanks for your quick reply!
I searched the whole android repository using grep -r com.stericsson.hardware.fm.receiver.xml device hardware kernel vendor and could only find an entry in device/samsung/arubaslim/device_arubaslim.mk. What should I do now? Should I just comment this line and try to run over it? Will this cause reduced functionality?
Inperpetuammemoriam said:
Thanks for your quick reply!
I searched the whole android repository using grep -r com.stericsson.hardware.fm.receiver.xml device hardware kernel vendor and could only find an entry in device/samsung/arubaslim/device_arubaslim.mk. What should I do now? Should I just comment this line and try to run over it? Will this cause reduced functionality?
Click to expand...
Click to collapse
https://github.com/Y300-0100/android_device_huawei_u8833/blob/caf/u8833.mk#L62
Maybe it's not needed at all or it's proprietary file from stock but I doubt that.
All you need is proper packages.
Y300-0100 said:
https://github.com/Y300-0100/android_device_huawei_u8833/blob/caf/u8833.mk#L62
Maybe it's not needed at all or it's proprietary file from stock but I doubt that.
All you need is proper packages.
Click to expand...
Click to collapse
You might be right. This section of the repository has been changed between cm-10.2 and cm-11.0, so that this file doesn't exist anymore. As grep -r com.stericsson.hardware.fm.receiver frameworks doesn't return any results, I suppose that this file has become obsolete. Because of that - I don't like to say this - I think the maintainer has abandoned his repository during the port to CM11.
Do you know if there is a more up-to-date repository for this device? I can't believe that the uploaded CM12 builds just pop out of nowhere...
I found no github repo for the amazon ariel so i started one
for the first i try to build a CWM recovery
Help me if you want:
https://github.com/etzisim/android_device_amazon_ariel
# android_device_amazon_ariel
Amazon FireHD 7 (4gen)
Local manifest for <build_env>/.repo/local_manifest/
local manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="etzisim/android_device_amazon_ariel" path="device/amazon/ariel" remote="github" />
<project name="etzisim/android_kernel_amazon_ariel" path="kernel/bn/encore" remote="github" />
</manifest>
CM12
great to hear but we do not want rather build CM12 of the new Fire OS 5?
sorry for bad english i am using Google Translate cus im from germany
way to go man keep up the work
etzisim said:
I found no github repo for the amazon ariel so i started one
for the first i try to build a CWM recovery
Help me if you want:
https://github.com/etzisim/android_device_amazon_ariel
Click to expand...
Click to collapse
There is a working TWRP version, so no need to replicate CWM !!!
Instead, what would add most value is if somebody managed to disable checking for signed bootloader/kernel. Basically, somebody would have to comb through TEE1/UBOOT binaries, and figure out how to disable signatures. There is no good way to debug it though, a tiny issue with the code may brick the device.
i have an idea build safestrap recovery for fire hd 7 to get cm 11 working not a cwm recovery
Edit: i cant try to build safestrap cuz there is no source code of it
Hey guys,
I'm somewhat new to building a custom ROM for Cyanogenmod, and I'm a bit lost right now...
Ok, so my problem is, I created a local_manifests.xml to pull in some repos for my device, which is not listed in the Cyanogenmod website, but I'm getting a "cannot fetch" error.
Since it's my first time working with the local_manifests.xml file, I thought it might be a problem in it. Maybe I did something wrong there.
This is what I came up with:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/sony/sonyxperiadev" name="sonyxperiadev/device-sony-seagull" remote="github"/>
<project path="vendor/sony/sonyxperiadev" name="sonyxperiadev/device-sony-common" remote="github"/>
<project path="kernel/sony/sonyxperiadev" name="sonyxperiadev/kernel" remote="github"/>
</manifest>
I got the repositories links from the FreeXperia Blog. (I can't post the link, or the repos link because I'm a new user, sorry!)
I'm trying to build a custom ROM for a Xperia T3 (D5106).
ANY help would be deeply appreciated.
Thanks!
Well... That's embarrassing. I just forgot to specify the revision on the xml file.