Re: Maven 3 and site generation

2011-01-24 Thread Stefan Seelmann
On Tue, Jan 25, 2011 at 12:36 AM, Felix Knecht wrote: > On 01/24/2011 11:09 PM, Alex Karasulu wrote: >> >> On Mon, Jan 24, 2011 at 11:40 PM, Stefan Seelmann >>  wrote: >>> >>> Hi devs, >>> >>> our projects build well will Maven 3. An exception is the site >>> generation which doesn't work with Mav

[Codec] Refactoring status

2011-01-24 Thread Alex Karasulu
Although I was going to apply the encoding decorator pattern last (STEP 5 in previous status) I started discussing the approach with Emmanuel last night and that kicked off the step ahead of the others. And it's not so bad to do this first. Now I have a few issues. First I am running out of time,

[Codec] Decorator not that simple

2011-01-24 Thread Alex Karasulu
Seems we have many more package friendly methods that the encoder is using in all the Message implementation classes. Like for AddRequestImpl we have the following: /** * Stores the encoded length for the AddRequest * @param addRequestLength The encoded length */ /* No quali

Re: Maven 3 and site generation

2011-01-24 Thread Jesse McConnell
yes hudson supports m3 we use it in hudson @ eclipse jesse -- jesse mcconnell jesse.mcconn...@gmail.com On Mon, Jan 24, 2011 at 17:36, Felix Knecht wrote: > On 01/24/2011 11:09 PM, Alex Karasulu wrote: >> >> On Mon, Jan 24, 2011 at 11:40 PM, Stefan Seelmann >>  wrote: >>> >>> Hi devs, >>> >>

Re: Maven 3 and site generation

2011-01-24 Thread Felix Knecht
On 01/24/2011 11:09 PM, Alex Karasulu wrote: On Mon, Jan 24, 2011 at 11:40 PM, Stefan Seelmann wrote: Hi devs, our projects build well will Maven 3. An exception is the site generation which doesn't work with Maven 3 because support for was removed. Instead a new version of the maven-site-pl

Re: Maven 3 and site generation

2011-01-24 Thread Emmanuel Lecharny
On 1/24/11 11:09 PM, Alex Karasulu wrote: On Mon, Jan 24, 2011 at 11:40 PM, Stefan Seelmann wrote: Hi devs, our projects build well will Maven 3. An exception is the site generation which doesn't work with Maven 3 because support for was removed. Instead a new version of the maven-site-plugi

Re: Maven 3 and site generation

2011-01-24 Thread Alex Karasulu
On Mon, Jan 24, 2011 at 11:40 PM, Stefan Seelmann wrote: > Hi devs, > > our projects build well will Maven 3. An exception is the site > generation which doesn't work with Maven 3 because support for > was removed. Instead a new version of the > maven-site-plugin must be used, [1] shows the migra

Maven 3 and site generation

2011-01-24 Thread Stefan Seelmann
Hi devs, our projects build well will Maven 3. An exception is the site generation which doesn't work with Maven 3 because support for was removed. Instead a new version of the maven-site-plugin must be used, [1] shows the migration path. I'd like to add support for Maven 3 site generation by ad

Re: [Shared] Refactoring update: next steps

2011-01-24 Thread Emmanuel Lécharny
On 1/24/11 6:45 PM, Alex Karasulu wrote: On Monday, January 24, 2011, Emmanuel Lecharny wrote: On 1/24/11 4:20 PM, Alex Karasulu wrote: I've moved all the classes that compose the model into a model sub package while removing codec dependencies. Next steps: (5) Apply Decorator to ldap-codec.

Re: [Shared] Refactoring update: next steps

2011-01-24 Thread Alex Karasulu
On Monday, January 24, 2011, Emmanuel Lecharny wrote: > On 1/24/11 4:20 PM, Alex Karasulu wrote: > > I've moved all the classes that compose the model into a model sub > package while removing codec dependencies. Next steps: > > (5) Apply Decorator to ldap-codec. > > I can handle this. > Thanks b

Re: [Shared] Refactoring update: next steps

2011-01-24 Thread Emmanuel Lecharny
On 1/24/11 4:20 PM, Alex Karasulu wrote: I've moved all the classes that compose the model into a model sub package while removing codec dependencies. Next steps: (5) Apply Decorator to ldap-codec. I can handle this. -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com

Re: Do Lucene developers use FindBugs?

2011-01-24 Thread Felix Knecht
Hi Cesar I am a PhD student at UFMG, Brazil and as part of my research I am making a study about the relevance of the warnings reported by the FindBugs bug finding tool. Since I am planning to use Directory as a subject system in my research, I would like to know if Directory's developers usua

Do Lucene developers use FindBugs?

2011-01-24 Thread César Couto
Dear developers, I am a PhD student at UFMG, Brazil and as part of my research I am making a study about the relevance of the warnings reported by the FindBugs bug finding tool. Since I am planning to use Directory as a subject system in my research, I would like to know if Directory's developer

[Shared] Refactoring update: next steps

2011-01-24 Thread Alex Karasulu
I've moved all the classes that compose the model into a model sub package while removing codec dependencies. Next steps: (1) There's still some more cleanup that I will do here. (2) Then I can move this whole package base over to ldap-model (3) Rename ldap to ldap-codec, have the codec depend on

About community, and how it works

2011-01-24 Thread Emmanuel Lecharny
Hi guys, I'm writing this as I'm currently unhappy about how this project operates I want to recall some elements about the way we work at The Apache Software Foundation, not that you don't know about those rules, but I'd like us to stick to the spirit of those rules, something I think we hav

Re: Shared refactoring : what's going on, some feedback

2011-01-24 Thread Pierre-Arnaud Marcelot
On 23 janv. 2011, at 14:47, Alex Karasulu wrote: > On Sun, Jan 23, 2011 at 12:06 PM, Emmanuel Lecharny > wrote: >> Hi guys, >> >> as you noticed, some heavy code refactoring is going on in shared. Let me >> give you some feedback about what is being done, and the reasons for those >> refactori

Re: Shared refactoring : what's going on, some feedback

2011-01-24 Thread Pierre-Arnaud Marcelot
Hi guys, On 23 janv. 2011, at 11:06, Emmanuel Lecharny wrote: > Hi guys, > > as you noticed, some heavy code refactoring is going on in shared. Let me > give you some feedback about what is being done, and the reasons for those > refactoring. > > First of all, the idea is to release a shared/