Hi folks,
many moons ago we discussed this issue ....
- Make the ParameterParser a POJO again. The implementation used is
configurable anyway (in the FactoryService). This really would be my
favourite.
that's the way to go
- Implement Lifestyles SingleThreaded and Poolable in YAAFI (Hi Siegfried!)
Arghh, container bloat
- Use a different Avalon Container (Fortress)
That is a bloated container - well, that was politically not correct
- Remove the getLogger() call that causes the NPE in
DefaultParameterParser.
that wold be option as well
Cheers,
Siegfried Goeschl
Thomas Vandahl wrote:
Andrey Larionov wrote:
Just checked out trunk. And there is 9 errors and lot of warnings.
Most of errors related to ValueParser or ParametersParser? Is trunk
compilable? Maybe i need another version of fulcrum-parser? Maven
download dev from ibiblio. Maybe i should download from your private
repo?
The trunks state is a bit untidy. The parser problem for example is a
known one. It is based on the fact that the ParameterParser is an
Avalon component but is not initialized as such from the
FactoryService. From my point of view the following solutions are
possible (in order of my preference):
- Make the ParameterParser a POJO again. The implementation used is
configurable anyway (in the FactoryService). This really would be my
favourite.
- Implement Lifestyles SingleThreaded and Poolable in YAAFI (Hi
Siegfried!)
- Use a different Avalon Container (Fortress)
- Remove the getLogger() call that causes the NPE in
DefaultParameterParser.
Opinions?
Bye, Thomas.
---------------------------------------------------------------------
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]
