The i18n sandbox project seems to be quite similar to Commons Resources.
What is the relationship between the two? Will they continue to co-exist?
i18n is appealing to me because it allows for multiple properties (such as
title and details) under a common key. We solve very similar problems in
At 2005-04-18 10:33, Daniel Florey wrote:
> i18n is appealing to me because it allows for multiple properties (such as
> title and details) under a common key. We solve very similar problems in
> our project, but I would like to use a generic API reusable among several
> projects. Although I see so
At 2005-04-18 11:11, Daniel Florey wrote:
> My though was to re-use the basename or id used when "installing"
> ResourceBundle or XML providers. For example, after issuing
>ResourceBundleMessageProvider.install("errorMessages");
> I would like to be able to qualify the newly installed messages
Will Ant be abandoned in favor of Maven or should I update the Ant script
to include the unit tests? (I have no experience with Maven)
What indentation do you use for XML? I find both tabs and 2 spaces, even in
the same file. (There is also a tab on line 80 in LocalizedBundle.java)
I have set up
Is there an Apache standard for unit test code coverage?
It seems some projects use Clover and others jcoverage. Personally I have
experience with Emma (http://emma.sourceforge.net/).
If I want to add code coverage to a Commons project, is either of these
preferrable?
Mattias Jiderhamn
---
At 2005-04-19 10:35, Daniel Florey wrote:
We should keep both (ant/maven) working. There is a maven task that will
automatically generate an ant script, but I've never used it.
Maven is a great tool as it can also handle website generation, test
reports, changelog etc. So it's worth to have a loo
What I currently need is better unit tests in
ResourceBundleMessageProviderTest.java and XMLMessageProviderTest.java.
After those are set up, I will begin some refactoring. If you would like to
help out on those unit tests it would be great.
Please inform me if you get your hands at it, and whi
At 2005-04-19 15:22, you wrote:
Please, sorry by my ignorance but, what is "unit test code coverage"?? This
is different than the traditional unit test?
Those are not separate tests, but tools that help you see how much of your
code that is actually tested by your unit tests. Testing is pretty use
week, I will continue work and
then mail you what I've got.
Mattias Jiderhamn
At 2005-04-19 15:22, Mattias J wrote:
What I currently need is better unit tests in
ResourceBundleMessageProviderTest.java and XMLMessageProviderTest.java.
After those are set up, I will begin some refactorin
At 2005-04-20 09:23, you wrote:
> Seems like i18n is reinventing the wheel over and over. I see we are
using
> of Sax, when Digester is the most viable choice, given the typical clients
> of this framework. I see where ResourceBundle is used, yet a much more
> robust solution is already provided
At 2005-04-20 12:06, you wrote:
> Shall we add an i18n-contrib.jar that contains all the
> optional extensions? I'd like to keep the core i18n.jar as
> small as possible...
Then you'll need some definition for this. IMHO MBeanInfoDescriptionBundle
is as light as the rest without any deps and this
At 2005-04-20 09:47, Mattias J wrote:
B.t.w James: Thought I'd run your new Maven config to see the coverage of
the tests I've added. Though I have not checked out
.../commons-build/sandbox-project.xml and currently I cannot access the
SVN server.
Sorry if this is because I'
At 2005-04-20 21:49, you wrote:
Seems like i18n is reinventing the wheel over and over. I see we are using
of Sax, when Digester is the most viable choice, given the typical clients
of this framework. I see where ResourceBundle is used, yet a much more
robust solution is already provided through
add Emma to Ant),
but I would prefer to spend my time on the code rather than the setup.
Mattias Jiderhamn
At 2005-04-20 09:47, Mattias J wrote:
B.t.w James: Thought I'd run your new Maven config to see the coverage
of the tests I've added. Though I have not checked out
.../com
-20 09:47, Mattias J wrote:
B.t.w James: Thought I'd run your new Maven config to see the coverage
of the tests I've added. Though I have not checked out
.../commons-build/sandbox-project.xml and currently I cannot access the
SVN server.
Sorry if this is because I'm a newbie with
It seems that the ResourceBundleMessageProvider and the XMLMessageProvider
behaves differently when an entry does not exist in a non-default language.
With ResourceBundles, if I have an entry, say
helloWorld.notTranslated=This entry is not translated to any other languages
that only exists in t
ting these important issues!
Daniel
BTW: I'm back home. If you want me to add your testcases just mail the zip
file to me.
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Im Auftrag von Mattias J
> Gesendet: Donnerstag, 21. Apri
At 2005-04-28 13:53, you wrote:
Simply because different regions of the world use different date layouts.
There isn't any date format that is a reasonable built-in default.
I don't agree. -mm-dd is the ISO (8601) standard.
http://www.iso.org/iso/en/prods-services/popstds/datesandtime.html
It i
Daniel, have you had time to study the unit tests and refactoring proposal
I sent you?
From what I can tell, nothing has been checked in. Do you want me to make
modifications?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addi
Thanks for checking in the unit tests.
Although, you checked in the tests running against the refactored code,
without checking in the refactoring. The test cases does not compile
against the code in the repository. Please commit also the following patch
(which I will also try to attach):
Inde
or of
java.util.ResourceBundle and providing our own implementation would not
only cost a lot of time, but feel just "wrong".
(B.t.w. I have started working on naming/qualifying provider and will post
a diff when I'm done)
/Mattias J
Elliotte Harold wrote:
Is there any chance or interest in splitting this mailing list up into
multiple mailing lists, one per subproject?
+1
+ 1 common mailing list (commons-common :-) ) - for mails like this.
Mario Ivankovits wrote:
I do have an easy overlook whats new in other projects, the traf
nough to wade through all the projects
they don't care about. Having separate lists might help the smaller
communities to grow a bit.
That is a point. The volume of the dev-list might actually make people
reluctant to subscribing to it at all.
Mario Ivankovits wrote:
Mattias J wrote:
The
SimonKitching wrote:
+ Any Jakarta committer (not just commons committers) has the right ask
for karma (commit access) and have it granted. The right place to ask is
on the commons-dev mailing list.
+ Commit access to the sandbox is unfortunately '''not''' available to
people who are not existi
I think I agree with this. I believe it is better to remove the entire
sandbox directory, so that people notice it has moved (the website says
where) and can change the SVN repository in use (that can be done; can't it?).
At 2005-05-13 10:10, you wrote:
I disagree, README is just clutter and sho
rule object sets
returned by Commands as pre-conditions and post-conditions, so that a Chain
would be responsible of making sure the different Commands are compatible
when added using addCommand()...?
Does anyone else have any thoughts about this?
/Mattias J
--
At 2005-05-14 00:51, Simon Kitching wrote:
On Thu, 2005-05-12 at 09:44 +0200, Mattias J wrote:
> And if I am not currently a Jakarta commiter, but would like sandbox
commit
> access for existing sandbox projects?
If you're not an ASF committer, then I think the current policy is t
I have made some changes to the i18n sandbox project and tried to create a
patch for it to submit, although I noticed the patch did not contain
everything I expected. At first I thought I had done something wrong, but
after several tries I realized the i18n package has dissapeared from the
test
xdocs/index.xml
Incorporated changes proposed by Mattias J
--
Martin Cooper
On 5/14/05, Mattias J <[EMAIL PROTECTED]> wrote:
> I have made some changes to the i18n sandbox project and tried to create a
> patch
I have previously discussed with Daniel Florey a change that allows the user to
qualify the provider (or source or namespace) to be used for a given text
entry. My main motivation for this is to allow the same entry key in several
different text sources, but this also provides better performance
[was "Re: [i18n PATCH] Adding provider qualifying"]
At 2005-05-19 16:41, you wrote:
But, to be honest, I'm a bit disappointed at how this project is being
developed. I feel that i18n would benefit tremendously by reusing instead
of reinventing.
Since Commons Resources and i18n seems to basically
Here is a list of what I think needs to be done before i18n is moved to
proper/released as 1.0:
* If the id ("parent") exists, but the entry ("child") does not, the
ResourceBundleMessageProvider throws an exception (erroneously claiming "No
message entries found for bundle with key ..."), whil
At 2005-05-23 19:52, you wrote:
All users of v2.1 should upgrade to v2.1...
This should read 2.1.1 shouldn't it?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
At 2005-05-24 17:11, Simon Kitching wrote:
There is also the question of how large the generic collections
community will be. There aren't yet a whole lot of projects coding to
1.5 as far as I know.
Assuming this statement is true (which I am not too sure about), the fact
that many Open Source
In summary, I don't think the number of people interested in 1.5 features
will increase while Commons Collections developers just sit around waiting...
Thats not fair.
We do what we can and mostly in our free time. And its also your
(contributor) job to push a project forward - for sure what y
[A few entries have been removed and a comment has beedn added to the list
of remaining issues previously posted]
Here is a list of what I think needs to be done before i18n is moved to
proper/released as 1.0:
* If the id ("parent") exists, but the entry ("child") does not, the
ResourceBundl
36 matches
Mail list logo
