You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@empire-db.apache.org by Francis De Brabandere <fr...@gmail.com> on 2010/12/12 21:43:09 UTC
2.0.7-incubating release completed, what's next?
Please check the website for missing stuff.
So do we want this next release before the end of the year?
Do we want to fix all these before? Something else to add?
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310820&fixfor=12315015
Cheers,
Francis
--
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.
Re: moving to slf4j
Posted by Francis De Brabandere <fr...@gmail.com>.
On Mon, Dec 13, 2010 at 1:54 PM, Rainer Döbele <do...@esteam.de> wrote:
>
> I once stated an attempt to use slf4j but I had a problem with the configuration.
> Our class org.apache.empire.xml.XMLConfiguration uses the log4j DOMConfigurator (org.apache.log4j.xml.DOMConfigurator) to initialize Logging from the config file.
>
> How do we replace this so that logging configuration from the config file is still possible?
>
We don't replace it by something else. We move that part out of the
empire-db main package. As this is logger implementation specific.
Slf4j is mainly an api containing interfaces. Then for each logging
implementation there are extensions. So for using log4j you would
still set up log4j as before and add slf4j-log4j to the classpath. The
difference is that the code will not call commons-logging but slf4j
instead.
If you want I can set up a branch where we try the switch.
Cheers,
Francis
> Regards
> Rainer
>
>
> Francis De Brabandere wrote:
>> from: Francis De Brabandere [mailto:francisdb@gmail.com]
>> to: empire-db-dev@incubator.apache.org
>> re: Re: 2.0.7-incubating release completed, what's next?
>>
>> Hi Andreas,
>>
>> On Mon, Dec 13, 2010 at 11:39 AM, Andreas Fink <an...@andreasfink.com>
>> wrote:
>> > Hi Francis, Rainer.
>> >
>> >>> Besides the prepared statement fixes we should reconsider the slf4j
>> logging (already tried but the problem seems to be the configuration)
>> and the exception handling - and maybe a few more things.
>> >>
>> >> I'm a fan of slf4j, and so dumping commons-logging. But the main
>> >> problem is that we have a hard dependency on log4j. We should at
>> least
>> >> make that optional.
>> >
>> > Why don't you have a look at Logback (+slf4j):
>> http://logback.qos.ch/documentation.html
>> > It is API compatible with slf4j, works with any logging impl out there
>> (jdk, commons, ...) and even writes to stdout if no impl is available
>> (handy for unit tests).
>>
>> I also think that as tool provider that we should not enforce any
>> logging framework implementation. We should stick to the best api
>> which at the moment is slf4j. Slf4j can use any other framework out
>> there as input (api) or output (implementation).
>>
>> > Moreover it gives you the possibility to keep the old calls to log4j
>> in the source, if this is really necessary: http://slf4j.org/legacy.html
>>
>> Since we move to a new minor version I think we should switch to slf4j
>> completely.
>>
>> I don't care too much what implementation we use in the examples /
>> unit tests: slf4j-log4j, slf4j-simple, slf4j-jdk14 or logback
>>
>> Cheers,
>> Fracnis
>>
>> >
>> > Cheers,
>> > Andi.
>> >
>> > --
>> > web: http://andreasfink.com/
>> > mail: af@andreasfink.com
>> > mobil: +34 65 1728443
>> > tel: +34 93 2082949
>> >
>> >
>>
>>
>>
>> --
>> http://www.somatik.be
>> Microsoft gives you windows, Linux gives you the whole house.
>
--
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.
moving to slf4j
Posted by Rainer Döbele <do...@esteam.de>.
I once stated an attempt to use slf4j but I had a problem with the configuration.
Our class org.apache.empire.xml.XMLConfiguration uses the log4j DOMConfigurator (org.apache.log4j.xml.DOMConfigurator) to initialize Logging from the config file.
How do we replace this so that logging configuration from the config file is still possible?
Regards
Rainer
Francis De Brabandere wrote:
> from: Francis De Brabandere [mailto:francisdb@gmail.com]
> to: empire-db-dev@incubator.apache.org
> re: Re: 2.0.7-incubating release completed, what's next?
>
> Hi Andreas,
>
> On Mon, Dec 13, 2010 at 11:39 AM, Andreas Fink <an...@andreasfink.com>
> wrote:
> > Hi Francis, Rainer.
> >
> >>> Besides the prepared statement fixes we should reconsider the slf4j
> logging (already tried but the problem seems to be the configuration)
> and the exception handling - and maybe a few more things.
> >>
> >> I'm a fan of slf4j, and so dumping commons-logging. But the main
> >> problem is that we have a hard dependency on log4j. We should at
> least
> >> make that optional.
> >
> > Why don't you have a look at Logback (+slf4j):
> http://logback.qos.ch/documentation.html
> > It is API compatible with slf4j, works with any logging impl out there
> (jdk, commons, ...) and even writes to stdout if no impl is available
> (handy for unit tests).
>
> I also think that as tool provider that we should not enforce any
> logging framework implementation. We should stick to the best api
> which at the moment is slf4j. Slf4j can use any other framework out
> there as input (api) or output (implementation).
>
> > Moreover it gives you the possibility to keep the old calls to log4j
> in the source, if this is really necessary: http://slf4j.org/legacy.html
>
> Since we move to a new minor version I think we should switch to slf4j
> completely.
>
> I don't care too much what implementation we use in the examples /
> unit tests: slf4j-log4j, slf4j-simple, slf4j-jdk14 or logback
>
> Cheers,
> Fracnis
>
> >
> > Cheers,
> > Andi.
> >
> > --
> > web: http://andreasfink.com/
> > mail: af@andreasfink.com
> > mobil: +34 65 1728443
> > tel: +34 93 2082949
> >
> >
>
>
>
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.
Re: 2.0.7-incubating release completed, what's next?
Posted by Francis De Brabandere <fr...@gmail.com>.
Hi Andreas,
On Mon, Dec 13, 2010 at 11:39 AM, Andreas Fink <an...@andreasfink.com> wrote:
> Hi Francis, Rainer.
>
>>> Besides the prepared statement fixes we should reconsider the slf4j logging (already tried but the problem seems to be the configuration) and the exception handling - and maybe a few more things.
>>
>> I'm a fan of slf4j, and so dumping commons-logging. But the main
>> problem is that we have a hard dependency on log4j. We should at least
>> make that optional.
>
> Why don't you have a look at Logback (+slf4j): http://logback.qos.ch/documentation.html
> It is API compatible with slf4j, works with any logging impl out there (jdk, commons, ...) and even writes to stdout if no impl is available (handy for unit tests).
I also think that as tool provider that we should not enforce any
logging framework implementation. We should stick to the best api
which at the moment is slf4j. Slf4j can use any other framework out
there as input (api) or output (implementation).
> Moreover it gives you the possibility to keep the old calls to log4j in the source, if this is really necessary: http://slf4j.org/legacy.html
Since we move to a new minor version I think we should switch to slf4j
completely.
I don't care too much what implementation we use in the examples /
unit tests: slf4j-log4j, slf4j-simple, slf4j-jdk14 or logback
Cheers,
Fracnis
>
> Cheers,
> Andi.
>
> --
> web: http://andreasfink.com/
> mail: af@andreasfink.com
> mobil: +34 65 1728443
> tel: +34 93 2082949
>
>
--
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.
Re: 2.0.7-incubating release completed, what's next?
Posted by Andreas Fink <an...@andreasfink.com>.
Hi Francis, Rainer.
>> Besides the prepared statement fixes we should reconsider the slf4j logging (already tried but the problem seems to be the configuration) and the exception handling - and maybe a few more things.
>
> I'm a fan of slf4j, and so dumping commons-logging. But the main
> problem is that we have a hard dependency on log4j. We should at least
> make that optional.
Why don't you have a look at Logback (+slf4j): http://logback.qos.ch/documentation.html
It is API compatible with slf4j, works with any logging impl out there (jdk, commons, ...) and even writes to stdout if no impl is available (handy for unit tests).
Moreover it gives you the possibility to keep the old calls to log4j in the source, if this is really necessary: http://slf4j.org/legacy.html
Cheers,
Andi.
--
web: http://andreasfink.com/
mail: af@andreasfink.com
mobil: +34 65 1728443
tel: +34 93 2082949
re: 2.0.7-incubating release completed, what's next?
Posted by Rainer Döbele <do...@esteam.de>.
Hi Franics,
thanks for the info and great that you already updated the website.
I missed some of the conversation especially on general.
I will try to catch up with reading.
Regards
Rainer
Francis De Brabandere wrote:
> from: Francis De Brabandere [mailto:francisdb@gmail.com]
> to: empire-db-dev@incubator.apache.org
> re: Re: 2.0.7-incubating release completed, what's next?
>
> Hi all,
>
> reply inline
>
> On Mon, Dec 13, 2010 at 10:43 AM, Rainer Döbele <do...@esteam.de>
> wrote:
> > Hi Franics,
> >
> > first I want to thank you again for managing this whole release
> process.
> > Unthinkable what we would do without you.
>
> It's quite straightforward, just takes some time, it's important to
> follow the wiki on making releases.
>
> >
> > Please apologize that I have been too busy and thus been very quiet.
>
> No need for that!
>
> > I will try to check and update the website today or tomorrow.
>
> That has been taken care of, at least for news, download links and
> javadoc
>
> > Also I will review your prepared statement check code.
> >
> > About what is next: Technically we should consider a new release 2.1.
> soon.
>
> Version has been updated to 2.1.0-incubating-SNAPSHOT in the
> repository, would we rather have 2.1-incubating-SNAPSHOT?
>
> > Besides the prepared statement fixes we should reconsider the slf4j
> logging (already tried but the problem seems to be the configuration)
> and the exception handling - and maybe a few more things.
>
> I'm a fan of slf4j, and so dumping commons-logging. But the main
> problem is that we have a hard dependency on log4j. We should at least
> make that optional.
>
> > Organizationally we must find out how we can move forward regarding
> our graduation.
> > Do you think we should ask the board whether they think we're ready?
>
> We just got a new mentor, which is great news. And about incubation...
> I fear we're not doing well enough at building up an active community.
>
> Cheers,
> Francis
>
> >
> > Regards
> > Rainer
> >
> >
> > Francis De Brabandere wrote:
> >> from: Francis De Brabandere [mailto:francisdb@gmail.com]
> >> to: empire-db-dev@incubator.apache.org
> >> re: 2.0.7-incubating release completed, what's next?
> >>
> >> Please check the website for missing stuff.
> >>
> >> So do we want this next release before the end of the year?
> >>
> >> Do we want to fix all these before? Something else to add?
> >>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mod
> >> e=hide&sorter/order=DESC&sorter/field=priority&resolution=-
> >> 1&pid=12310820&fixfor=12315015
> >>
> >> Cheers,
> >> Francis
> >>
> >> --
> >> http://www.somatik.be
> >> Microsoft gives you windows, Linux gives you the whole house.
> >
>
>
>
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.
Re: 2.0.7-incubating release completed, what's next?
Posted by Francis De Brabandere <fr...@gmail.com>.
Hi all,
reply inline
On Mon, Dec 13, 2010 at 10:43 AM, Rainer Döbele <do...@esteam.de> wrote:
> Hi Franics,
>
> first I want to thank you again for managing this whole release process.
> Unthinkable what we would do without you.
It's quite straightforward, just takes some time, it's important to
follow the wiki on making releases.
>
> Please apologize that I have been too busy and thus been very quiet.
No need for that!
> I will try to check and update the website today or tomorrow.
That has been taken care of, at least for news, download links and javadoc
> Also I will review your prepared statement check code.
>
> About what is next: Technically we should consider a new release 2.1. soon.
Version has been updated to 2.1.0-incubating-SNAPSHOT in the
repository, would we rather have 2.1-incubating-SNAPSHOT?
> Besides the prepared statement fixes we should reconsider the slf4j logging (already tried but the problem seems to be the configuration) and the exception handling - and maybe a few more things.
I'm a fan of slf4j, and so dumping commons-logging. But the main
problem is that we have a hard dependency on log4j. We should at least
make that optional.
> Organizationally we must find out how we can move forward regarding our graduation.
> Do you think we should ask the board whether they think we're ready?
We just got a new mentor, which is great news. And about incubation...
I fear we're not doing well enough at building up an active community.
Cheers,
Francis
>
> Regards
> Rainer
>
>
> Francis De Brabandere wrote:
>> from: Francis De Brabandere [mailto:francisdb@gmail.com]
>> to: empire-db-dev@incubator.apache.org
>> re: 2.0.7-incubating release completed, what's next?
>>
>> Please check the website for missing stuff.
>>
>> So do we want this next release before the end of the year?
>>
>> Do we want to fix all these before? Something else to add?
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mod
>> e=hide&sorter/order=DESC&sorter/field=priority&resolution=-
>> 1&pid=12310820&fixfor=12315015
>>
>> Cheers,
>> Francis
>>
>> --
>> http://www.somatik.be
>> Microsoft gives you windows, Linux gives you the whole house.
>
--
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.
re: 2.0.7-incubating release completed, what's next?
Posted by Rainer Döbele <do...@esteam.de>.
Hi Franics,
first I want to thank you again for managing this whole release process.
Unthinkable what we would do without you.
Please apologize that I have been too busy and thus been very quiet.
I will try to check and update the website today or tomorrow.
Also I will review your prepared statement check code.
About what is next: Technically we should consider a new release 2.1. soon.
Besides the prepared statement fixes we should reconsider the slf4j logging (already tried but the problem seems to be the configuration) and the exception handling - and maybe a few more things.
Organizationally we must find out how we can move forward regarding our graduation.
Do you think we should ask the board whether they think we're ready?
Regards
Rainer
Francis De Brabandere wrote:
> from: Francis De Brabandere [mailto:francisdb@gmail.com]
> to: empire-db-dev@incubator.apache.org
> re: 2.0.7-incubating release completed, what's next?
>
> Please check the website for missing stuff.
>
> So do we want this next release before the end of the year?
>
> Do we want to fix all these before? Something else to add?
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mod
> e=hide&sorter/order=DESC&sorter/field=priority&resolution=-
> 1&pid=12310820&fixfor=12315015
>
> Cheers,
> Francis
>
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.