Hello!
I think it is this Jenkins bug that causes this:
https://issues.jenkins-ci.org/browse/JENKINS-959
/Linus
2012/6/24 Linus Tolke Tigris <[email protected]>
> Hello again Laurent!
>
> It looks like we are both mistaken. For some reason, snapshots for the
> jars with the properties are deployed even though the tests are failing. I
> don't know the reason for this but it is clear from the logs of the
> i18n-projects that this is happening.
>
> /Linus
>
>
> 2012/6/23 Linus Tolke Tigris <[email protected]>
>
>> Hello again Laurent!
>>
>> The questions you are asking are very interesting. The first ones boils
>> down to "What is the purpose of the tests?" and you are right of course,
>> you can't do a maven package with failing tests.
>>
>> One purpose of the tests is to make sure that everything is correct.
>> Another purpose is to make sure that things that worked previously does not
>> suddenly get broken (regression). Both purposes are difficult to achieve in
>> this. My main purpose, in the short run, is to get something running to
>> allow us to get a gerrit/Jenkins to have something to work on. We are still
>> a little bit away from releasing with maven so I don't see that as a
>> problem.
>>
>> I have added an option for the specific internationalization to avoid
>> testing certain keys. That will allow developers of the
>> internationalization to specify what files that are not yet started while
>> files that are complete will get the complete coverage of the test.
>>
>> I am sure you are also right about the character encoding problems. I
>> didn't think of that aspect when implementing that test case. I have
>> removed that test now.
>>
>> I added a test that attempts to see that all format parameters are used
>> in the string. I hope you also think that this would be a good idea. I will
>> add the tests to all i18n projects.
>>
>> /Linus
>>
>>
>> 2012/6/23 Laurent BRAUD <[email protected]>
>>
>>> Hi,
>>> I have seen you make something and I will look.
>>>
>>> >"Since there aren't that many translation done in the argouml-sv
>>> project, there are a lot of errors found by these tests. Please let me know
>>> what you think if this approach."
>>>
>>> It was one of the goal of this post, by the question
>>> "If a test failed because a translation missing, can the jar been build
>>> ?".
>>>
>>> It's impossible to have a complete translation (Or we have to set all
>>> keys, and set the defaut message -so no idea of % of translation !- ).
>>>
>>> So, I think that it has to be built. But, when a properties is all
>>> translated (or for a commercial tool), I think that it could be a good
>>> thing. BUT the developper who choose a new keyword can't translate it in
>>> any language, so gerrit has to accepted it.
>>>
>>> I don't use a lot JUNIT/Maven/Jenkins, so I don't know what we can do
>>> with something like the "@ignore" in junit.
>>>
>>>
>>> >"I am not sure about the test of the contents in the strings"
>>> After my first post, I try to do a first JUNIT test. And as I used
>>> "Properties", it doesn't work (Always found é, even if it was the code in
>>> properties). I will try yours.
>>>
>>> ------------------------------------------------------
>>>
>>> http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2972762
>>>
>>> To unsubscribe from this discussion, e-mail: [
>>> [email protected]].
>>> To be allowed to post to the list contact the mailing list moderator,
>>> email: [[email protected]]
>>>
>>
>>
>
------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=3004619
To unsubscribe from this discussion, e-mail:
[[email protected]].
To be allowed to post to the list contact the mailing list moderator, email:
[[email protected]]
