What is the purpose of argLine down here
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<argLine>-Dspring.config.location=file://${user.home}/.l10n/config/webapp/
-Dspring.profiles.active=${user.name},test -Xmx1024m -XX:MaxPermSize=256m
</argLine>
</configuration>
</plugin>
</plugins>
</build>
@chreck I'm gonna have a look to see if we can support different source language properly. But else has it stands you should be able to use the tool regardless. If the file are in
res/values/strings.xml then the source string will be linked to "en" which is improper but won't prevent the rest to work fine
@gvamsikrishna9 it is used to activate spring profiles based on your user name and also configure the default location where you can add configuration files that will be use during the test
@aurambaj Thanks for looking into it. We will maybe using mojito in the near future for a new bigger project but not now. If you know a provider who is running mojito it would be interesting. I know there is a docker image but I think it takes a lot of knowledge to handle docker images correctly.
I want to use Mojito, but I don't have any experience with Java apps. I'm used to php scripts on regular webhosting services. Any basic how-to resources you guys could recommend?
@briantastico_twitter if you're familiar with Docker there is a docker compose file here: https://github.com/box/mojito/blob/master/docker/docker-compose.yml. The image it is pointing to is very old though. Else, the harder part is probably to setup the DB. On the Java side you only need Java 8 installed and it can all run as described here: http://www.mojito.global/docs/guides/install/#using-executable-jars
For hosting, you probably want to look for the usual springboot app hosting solution. I haven't tried any lately
@briantastico_twitter this will always get the latest release
Hello everyone, I have an issue with push command, Please give me your advise
I am using docker to build mojito
But cannot push the exists string.properties file
~/.linuxbrew/bin/mojito push -r MyRepo -s /input/
Push assets to repository: MyRepo
- Uploading: string.properties
Unexpected error, see logs for more information
Do you know where is the logs stored
@khanhhd Is /input/ the correct directory where you have read permission?
Hi @jeeyi @aurambaj , Thank for your help. I found the logs are located in
But I could not find a configuration to store the logs
My problem was MySQL encoding was not set to utf-8, it noticed in
/tmp/ directory after using find / -type f -name *mojito*But I could not find a configuration to store the logs
My problem was MySQL encoding was not set to utf-8, it noticed in
/tmp/spring.log java.sql.SQLException: Incorrect string value:
My issue is resolved, Thank you all again
I want to import existing translations as needing translation, but with content that is translated
I know about the option of setting status when translations are same as the source
But I want to have that when translations are passed
The reason is translations are wrong
Also found tm-import and tm-export, but want to use just import
Hey all, weareusing Mojito from ~1y, today when I try to push I received:
[..EDITED..]
Running, task id: 84384
Asset content has not changed (84384) Done
Unexpected error, see logs for more informationLooking into logs I see:
2019-03-18 22:17:26.014 ERROR 1 --- [_MisfireHandler] o.s.s.quartz.LocalDataSourceJobStore : MisfireHandler: Error handling misfires: Couldn't retrieve trigger: No record found for selection of Trigger with key: 'DYNAMIC.repositoryStatisticJob_15' and statement: SELECT * FROM QRTZ_SIMPLE_TRIGGERS WHERE SCHED_NAME = 'scheduler' AND TRIGGER_NAME = ? AND TRIGGER_GROUP = ?Anyone have can help me tobetter understand what's wrong?
@mavimo did you recently update? Do you have configuration for quartz like shown here: http://www.mojito.global/docs/guides/install/#mysql or still running without it? Also you may want to look for another error in the log because I don't think that error would lead to the push failing
I'm not familiar with Heroku but I would expect it to be relatively easy to do. I've been running it on AWS (ec2+rds). The server can be run as a standalone jar, passing config (especially credentials) in a clean way might be the part that takes a big more time. Else the most sensible part is to setup/manage the mysql server.
yes that's one way with spring boot. The doc is pretty extensive on the subject: https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-external-config.html
last I've done use
SPRING_APPLICATION_JSON to pass all the conf as a JSON object instead of having multiple environment parameters
Hey all, our team recently started to use mojito, and we want to import some translation memory files (.xliff format) from other applications into mojito. I am wondering what is the correct way to do so?
Suppose our TM files are in ~/Demo, and I have created one repo named "Demo", I have tried to run
Any advice what is the correct command to run?
Suppose our TM files are in ~/Demo, and I have created one repo named "Demo", I have tried to run
mojito import -r Demo ormojito tm-import -r Demo, but none of them worked.Any advice what is the correct command to run?
Hi @Victor515 . The import command is the best way to bootstrap repository from already localized files (https://www.mojito.global//docs/guides/import-localized-files/).
Assuming you have XLIFF like here: https://www.mojito.global//docs/refs/mojito-file-formats/#xliff-example, you can do:
mojito repo-create -n xliffImport -l es-ES
mojito push -r xliffImport
mojito import -r xliffImportThe tm-import is supposed to be used with files that are generated using tm-export command (mostly use to do project maintenance). There is little configuration that can be done and there isn't really an option to import standalone TMs.
yes, it pushes them to the server but the server process them only when they have changed or if the filter options are different. We added
--git-diff but ended up not using it so far and I'm thinking about removing it. The idea is indeed to not send the file to the server if there are no change. You can also ignore part of the diff. it is useful when working with files generated by an extractor like gettext. Even if the strings are the same, the file will be different because of the created timestamp that changes. What I don't like about --git-diff is that it is dependent on the SCM and thinking more about it there are probably better way to do that.
the original idea was to keep the CLI as simple as possible and let the server have the main logic. But if sending too many files to the server is a bottleneck the md5 check could be moved to the client, etc. That said it hasn't been an issue with our current usage