On 15/08/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> For the latter, I use:
>
> function propcheck() {
> for i in `find $1 -type f -name '*.properties'`
> do
> for j in `cat $i | sed 's/=.*//'`
This does not allow for comment or continuation lines ...
> do
> grep -R --exclude='*properties*' --exclude='*svn*' $j $1 >
> /dev/null
Might be safer to include only *.java files. Can properties be used
in other files?
Otherwise certainly need to exclude *.metaprop files (used by at least
one I18n editor).
Would also be safer to match "$j", as the property name has to be
quoted when used. Otherwise it can match property names that are a
substring of other names.
It can still match property names that are not being used as properties.
This may or may not be a big problem, depending on the naming
convention (if any) used, and particularly the length of the property
names - shorter ones are more likely to trigger false matches.
> if [ $? -ne 0 ]
> then
> echo "Property $j is missing."
> else
> echo "Property $j is good."
> fi
> done
> done
> }
> On 8/15/07, sebb <[EMAIL PROTECTED]> wrote:
> > On 15/08/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> > > (DNS issues, trying again)
> > >
> > > ---------- Forwarded message ----------
> > > From: Henri Yandell <[EMAIL PROTECTED]>
> > > Date: Aug 15, 2007 6:56 AM
> > > Subject: [CLI] Getting moving with 2.0
> > > To: Jakarta Commons Developers List <dev@commons.apache.org>, Andrew
> > > Shirley <[EMAIL PROTECTED]>
> > >
> > >
> > > Two different angles I guess.
> > >
> > > Firstly we've got 17 issues open, and secondly we have opinions on
> > > directions to take the library. It's easiest to get started on the
> > > issues I think, so here are the ones that look like our obvious
> > > targets:
> > >
> > > * https://issues.apache.org/jira/browse/CLI-61
> > >
> > > Andrew Shirley reported this and supplied a patch. Need someone to
> > > look at this and then we can apply it (Andrew, are you still around?).
> > >
> > > * https://issues.apache.org/jira/browse/CLI-6
> > >
> > > This has a patch from Brian Hanson. Looks like Rob thought there were
> > > decisions to make, so this is a good one to get started on thinking of
> > > the big picture with. Anyone have any views on this one?
> > >
> > > * https://issues.apache.org/jira/browse/CLI-122
> > >
> > > A note from me that we need a test for CLI-51 in CLI 2.0. Brian added
> > > a unit test to CLI1 to fix CLI-51, any thoughts on doing the same for
> > > CLI 2.0 Brian?
> > >
> > > * https://issues.apache.org/jira/browse/CLI-118
> > >
> > > Spanish bundle for CLI. I suspect this would be quite educational to
> > > dig into - we need to make sure that we also clean up the .properties
> > > as in my experience they tend to accumulate unused properties.
> >
> > JMeter has some test code to check that there aren't any extra
> > properties in "foreign" bundles compared with the "native" bundle. I
> > could dig that out if required. Checking for spurious entries in the
> > "native" bundle is rather harder ...
> >
> > > * https://issues.apache.org/jira/browse/CLI-99
> > >
> > > Can someone confirm that this is not an issue in CLI2?
> > >
> > >
> > > Hen
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
