Closed GoogleCodeExporter closed 9 years ago
The default package is a great idea, but the renaming from HandlerExecutor to
MultiProperties is a little bit confusing because the class name should
represent the purpose of the class. On the other hand, it is just a small
command line tool, it would not be a big mistake.
Regarding the output directory and the single execution for each column. The
solution should let the user overwrite the "columnConfig", because usually he
needs to use different path (comparing to the Eclipse workspace paths), or
different option flags (in case of Properties handler). So I mean just the
outputDir parameter cannot be enough. I could imagine a "columnConfigPattern"
argument instead of "columnConfig", where for example the user could use the
column name as a variable. Like:
... -columnConfig "C:\temp\file_${columnName}.properties|true|true|true|false" ...
A kind of Ant style variable format.
Does the above detailed solutions satisfy your requirement?
Comment: you can also take a look into the
http://code.google.com/a/eclipselabs.org/p/multiproperties/wiki/CommandLineHandl
erExecutor wiki page. It is just recently created.
Original comment by ska...@gmail.com
on 17 Sep 2012 at 7:56
[deleted comment]
Thanks, didn't mean to suggest renaming HandlerExecutor but perhaps just
providing a an additional entry point for generating multiple property files at
once. Sure, if you don't mind supporting output file format that would
certainly satisfy my requirement. The wiki page looks great!
Original comment by kalle.o....@gmail.com
on 17 Sep 2012 at 11:45
A new "columnConfigPattern" argument has been introduced, where the
${columnName} marker can be used for differentiating the output generation
column by column.
The related wiki is already updated.
http://code.google.com/a/eclipselabs.org/p/multiproperties/wiki/CommandLineHandl
erExecutor
Will be delivered by 1.2.0 release in the next days.
Original comment by ska...@gmail.com
on 13 Nov 2012 at 8:13
Original comment by ska...@gmail.com
on 14 Nov 2012 at 8:24
Original issue reported on code.google.com by
kalle.o....@gmail.com
on 17 Sep 2012 at 2:26