Error in built jar file

[shum...@gmx.de]

Hello,

I have no done the packaging for brailleUtils 1.2.3. I now want to test the
package and get the following error when trying to convert a text to PDEF
format:

% brailleutils text2pef -mode=de_de text out.pef
Starting text to pef application...
Exception in thread "main" java.lang.IllegalArgumentException: Unknown option "required-3"
at org.daisy.braille.facade.PEFConverterFacade.parseTextFile(PEFConverterFacade.java:285)
at org.daisy.braille.ui.TextParser.main(TextParser.java:80)
at org.daisy.braille.ui.BasicUI.run(BasicUI.java:114)
at org.daisy.braille.ui.BasicUI.main(BasicUI.java:143)

Is this a fault of the application or a fault of my compilation? Or even a fault
of usage?

Thanks
Sebastian
--
Web: http://www.crustulus.de | Blog: http://www.crustulus.de/cgi-bin/blog.cgi?de-0
Freies Latein-Deutsch-Wörterbuch: http://www.crustulus.de/freedict.de.html
FreeDict: Free multilingual dictionary databases - http://www.freedict.org

[Joel Håkansson]

Hi Sebastian,

You have to put the required arguments first, that's all.

Best,
Joel

-----Ursprungligt meddelande-----
Från: braill...@googlegroups.com [mailto:braill...@googlegroups.com] För shum...@gmx.de
Skickat: den 15 mars 2014 20:21
Till: braill...@googlegroups.com
Ämne: Error in built jar file

[shum...@gmx.de]

Hello Joel,

Joel Håkansson schrieb am 17.03.2014, 7:36 +0000:
>You have to put the required arguments first, that's all.

You are right. Seemed to me a bit counter-intiutive and therefore I overlooked
it in the help output. But anyway, the packaging works, thanks!

The user documentation states that this command line interface is mostly
targeted at developers and not at end users. On GNU/Linux however, there are
some users which are used to the command line, so with three enhancements, you
could increase the usability a lot:

+ there should be a general parameter to activate debugging facilities:
- if it is not set, the te whole stack trace is printed, but jost the
(important) message
- if set, the stack trace should be printed
+ please remove the message "starting .* application"
- you could optionally print it when the debug flag is set

Would that be possible?

Thank you!

[Joel Håkansson]

Hi Sebastian,

Thank you for your feedback. I am all for fixing problems in the CLI, but since I am not a Linux person myself, I need specific requests, like the ones below. The second one I have fixed now, the first one I added an issue for at google code.

http://code.google.com/p/brailleutils/issues/detail?id=50

Please feel free to submit additional requests directly in the issue tracker, if you want.

Best,
Joel

-----Ursprungligt meddelande-----
Från: braill...@googlegroups.com [mailto:braill...@googlegroups.com] För shum...@gmx.de

Skickat: den 17 mars 2014 11:00
Till: braill...@googlegroups.com
Ämne: Re: SV: Error in built jar file

[Sebastian Humenda]

Hello Joel,

Joel Håkansson schrieb am 17.03.2014, 13:30 +0000:
>Thank you for your feedback. I am all for fixing problems in the CLI, but since
>I am not a Linux person myself, I need specific requests, like the ones below.

Thanks on your side :).

>The second one I have fixed now, the first one I added an issue for at google
>code.
>
>http://code.google.com/p/brailleutils/issues/detail?id=50
>
>Please feel free to submit additional requests directly in the issue tracker, if you want.

Well, I have looked into it. Do you already have debugging facilities
implemented? I haven't found them, if existent.

I first imagined something like:

try {
everythingWhatIsMainCode();
catch(exception e)
if(!DEBUG)
System.out.println("Error: "+e.getMessage()); // possible more
else:
e.stackTrace(); // symbolic code
}
}

This is not easily possible, since every «subprogram» of brailleUtils is is an
application on its own with its own static main method. Therefore you would have
to do the above error handling in every subprogram.
Do you have a better idea how to implement it?

Thanks

[Joel Håkansson]

Hi Sebastian,

Well, if there is a debugging facility, it is Logger.getLogger(classname).fine("");

I guess I could send stack traces there. To enable it as it currently is, you'd have to provide a settings file for the logging. If you want a command line switch for it, I guess the log level could be set to fine from within the application.

E.g.

try {
everythingWhatIsMainCode();
catch(exception e) {
logger.severe(e.getMessage());
logger.log(Level.FINE, e.getMessage(), e);
}

What do you think about that?

/Joel

-----Ursprungligt meddelande-----
Från: braill...@googlegroups.com [mailto:braill...@googlegroups.com] För Sebastian Humenda
Skickat: den 22 mars 2014 19:43
Till: braill...@googlegroups.com
Ämne: Re: Error in built jar file

[Sebastian Humenda]

Hello Joel,

Joel Håkansson schrieb am 24.03.2014, 8:40 +0000:
>Well, if there is a debugging facility, it is Logger.getLogger(classname).fine("");
>
>I guess I could send stack traces there. To enable it as it currently is, you'd
>have to provide a settings file for the logging. If you want a command line
>switch for it, I guess the log level could be set to fine from within the
>application.
>
>E.g.
>
>try {
> everythingWhatIsMainCode();
>catch(exception e) {
> logger.severe(e.getMessage());
> logger.log(Level.FINE, e.getMessage(), e);
>}
>
>What do you think about that?

Looks great. Would you implement it? I could try it myself, but I guess you are
much quicker with it.

[Joel Håkansson]

Hi Sebastian,

I don't have time to do it at the moment, but I can have a look later this month.

Best,

Joel

-----Ursprungligt meddelande-----
Från: braill...@googlegroups.com [mailto:braill...@googlegroups.com] För Sebastian Humenda

Skickat: den 31 mars 2014 21:48
Till: braill...@googlegroups.com
Ämne: Re: SV: Error in built jar file