We're finalising the rename from Flies to Zanata in 1.3, which we plan
to deploy on https://translate.jboss.org/ this week (probably Thursday).
Unfortunately, there a few small changes needed to your config files.
Sorry! When we deploy Zanata on translate.jboss.org, the Maven Flies
client will stop working, so you will need to make these changes then:

Steps to take:

1. Rename ~/.config/flies.ini to ~/.config/zanata.ini (or create a
symlink...)

NB: If your flies.ini has an entry for
https://translate.jboss.org/flies/, please change it to
https://translate.jboss.org/

2. For each of your projects on translate.jboss.org,
rename flies.xml to zanata.xml, and change xmlns to
http://zanata.org/namespace/config/, ie
<config xmlns="http://zanata.org/namespace/config/">

Please check that you are using the URL https://translate.jboss.org/ not
the old URL https://translate.jboss.org/flies/.

3. If you use the Maven client, edit your pom.xml and any helper scripts:
plugin group: org.zanata
plugin artifact: zanata-maven-plugin
version: 1.3

eg
<plugin>
<groupId>org.zanata</groupId>
<artifactId>zanata-maven-plugin</artifactId>
<version>1.3</version>
</plugin>

Any scripts will need to use the zanata: prefix instead of flies:.
Also, properties such as flies.srcDir have been renamed to
zanata.srcDir. For instance
mvn flies:publican-push -Dflies.srcDir=.
should become
mvn zanata:publican-push -Dzanata.srcDir=.

I have already made the required Weld changes, so I will be
submitting a pull request on github. But it would probably be best not
to merge it in until translate.jboss.org has been upgraded to Zanata,
because the Zanata client won't work with the old Flies server.

Also if you have a Hudson job which executes the flies_* scripts, it
will need to use zanata_* instead. (Or I can rename them back to
flies_* if you prefer.)

Again, I do apologise for the inconvenience, and let me know if I can
help with anything.