[17:55:31] alexsmirnov: balunasj: Yes, it is.
[17:55:50] ilya_shaikovsky| теперь известен как ilya_shaikovsky
[17:55:57] balunasj: nbelaevski: Hi nbelaevski
[17:56:04] ilya_shaikovsky: hllo All!
[17:56:09] ilya_shaikovsky: hello :)
[17:56:13] Alex_Kolonitsky (~akolonits@93.191.103.3) присоединился к #richfaces
[17:56:15] balunasj: alexsmirnov: I'm looking up that link not in the transcript - one mine
[17:57:02] nbelaevski: balunasj: it should be in meeting minutes
[17:57:06] balunasj: http://jira.codehaus.org/browse/MNG-3716
[17:58:14] balunasj: ok so this is showing fixed in 2.1.0, but as you say - only for interactive
[17:59:08] balunasj: Hi all - we'll get started in just a couple of minutes
[17:59:12] balunasj: here is the agenda http://community.jboss.org/wiki/RichFacesTeamMeetingAgenda5-18-2010
[17:59:50] balunasj: alexsmirnov: are planning on reviewing this?  or do we need to have someone else look?
[17:59:54] alexsmirnov: balunasj: That is another issue. I can find proper link later.
[18:01:08] alexsmirnov: Out of topic: I see warning on top of page "There are some system components which have reached, or are approaching, their license limit for page views, member seats, or has reached its software subscription expiration. For details, please contact your system administrator."
[18:01:35] prabhatjha (~prabhat@ip70-177-185-159.dc.dc.cox.net) покинул #richfaces [  ]
[18:01:35] alexsmirnov: Is it Jboss site problem or something wrong in my profile ?
[18:01:48] balunasj: alexsmirnov: yup - it should only be visable to space admins, and is being looked at
[18:03:18] balunasj: ok guys lets get started
[18:04:05] balunasj: here is the agenda
[18:04:06] balunasj: http://community.jboss.org/wiki/RichFacesTeamMeetingAgenda5-18-2010
[18:04:11] balunasj: for release planning
[18:04:33] balunasj: we are going to have a dev code freeze next Friday for Alpha2
[18:04:46] balunasj: this is based on the various status updates, and discussions
[18:05:10] balunasj: we have some minor talks left for amarkhel components, but that is later in the meeting
[18:05:48] balunasj: given that this is the first release with new structure, and we hope to automate as much as we can
[18:06:10] balunasj: I'm not confident that the build for QE will be ready by Monday, but it should be close
[18:06:53] balunasj: I was hoping to talk with prabhat about the plan for A2 testing
[18:07:02] balunasj: lfryc: he dropped off - do you know why?
[18:07:17] lfryc: balunasj: not sure
[18:07:35] balunasj: ok I may need to touch base with him later
[18:07:47] lfryc: balunasj: actually he is on PTO
[18:07:48] balunasj: lfryc: have you heard anything on the plan for testing A2?
[18:07:52] lightguard_jp (~lightguar@166-70-166-98.ip.xmission.com) присоединился к #richfaces
[18:08:24] ppitonak: balunasj:  we have only unit test
[18:08:39] ppitonak: balunasj: or is there anything we don't know about?
[18:09:04] lfryc: balunasj: nothing formal, but we go through some initial steps like configured environment for client-side and server-side performance testing
[18:09:05] balunasj: ppitonak: we have been covering all of the functionality in these meetings, or in forums
[18:09:31] lfryc: balunasj: and how Pavol said, the test-application are ready to filling by components + tests
[18:09:33] balunasj: obviously the unit tests are part of it, but I would like some manual testing of A2 as well.
[18:09:55] lfryc: balunasj: Prabhat also plans to do some new example application afaik
[18:10:28] balunasj: yup and I think that is great, but I'm talking more about pre-releaes test execution, than more test development right now
[18:11:11] balunasj: We'll touch base with prabhat, and discuss what he feels he can get done in a 1-1.5 weeks ( tops )
[18:11:17] balunasj: before we release.
[18:11:27] lfryc: yes
[18:11:34] balunasj: ok
[18:12:10] balunasj: Dev team - any changes in status, or questions besides the ones already listed out below in the agenda that we should add to the list?
[18:12:36] balunasj: nbelaevski: ilya_shaikovsky alexsmirnov Alex_Kolonitsky pyaschenko abelevich , etc....
[18:13:14] balunasj: Alex_Kolonitsky: btww - your latest commits seem to have broken the build for commons, and core - I have not reviewed them yet.
[18:13:37] nbelaevski: I'm going to do small redesign for partial updates
[18:13:50] nbelaevski: this is to make tables simpler
[18:14:09] nbelaevski: + have some ideas on how to improve resources handling
[18:14:46] balunasj: Alex_Kolonitsky: seems to be back now - perhaps just a timing issues - I'll still review your updates so we can talk
[18:14:51] nbelaevski: + I've reviewed queues server-side code and there are some changes to apply
[18:15:13] balunasj: nbelaevski: ok how much time do you think these will take?
[18:16:02] nbelaevski: I expect to complete mine tasks this week if I won't work on assembler or on the next weel if I will work on it
[18:16:40] alexsmirnov: nbelaevski: I hope that I will have time for assembler.
[18:17:11] nbelaevski: alexsmirnov: ok, good
[18:17:20] balunasj: alexsmirnov: the cdk one, or are you going to assist Alex_Kolonitsky with the project one?
[18:17:33] alexsmirnov: From my perspective, it would be easy combination of the two existing plugins.
[18:18:20] alexsmirnov: I meant library assembler to create single jar from component projects.
[18:18:46] balunasj: alexsmirnov: oh ok - you can see the cause of my confusion ;-)
[18:19:13] balunasj: nbelaevski: were you also talking about the library assembler, or help with the project assembler?
[18:19:23] nbelaevski: library assembler
[18:20:02] nbelaevski: balunasj: I think I'll be helping with testing project assembler
[18:20:34] balunasj: nbelaevski: ok, that is what I thought - wanted to make sure we are on same page.
[18:20:44] nbelaevski: balunasj: ok
[18:20:58] balunasj: all:  any other items we need to discuss ( except for the ones already listing in the agenda )?
[18:22:10] balunasj: ok then - lets jump on to the listing the agenda
[18:22:28] balunasj: amarkhel: you had some open estimate questions in the status thread
[18:22:39] balunasj: amarkhel: can you explain?
[18:22:57] amarkhel: yes, one minute
[18:23:17] alexsmirnov: balunasj: what do you mean about project assembler ?
[18:23:31] amarkhel: balunasj: I have to implement 3 components(poll, messages and param) poll is started, other two not
[18:23:35] balunasj: alexsmirnov: http://community.jboss.org/message/543625
[18:23:55] balunasj: and the work that Alex_Kolonitsky is doing around that structure.
[18:23:56] amarkhel: balunasj: but I have look on 3.3.x branch and specification for this components
[18:24:52] amarkhel: balunasj:so my estimates 2 day to implement param and 3 -for messages, but I heard that alexSmirnov will be work on validators
[18:24:58] clerum (~clerum@208.85.63.62) вышел из IRC [ Read error: Connection reset by peer ]
[18:25:17] amarkhel: balunasj: so, maybe some questions arised in messages comp too
[18:25:45] balunasj: amarkhel: have you and alexsmirnov been able to discuss this
[18:25:46] balunasj: ?
[18:25:57] clerum (~clerum@208.85.63.62) присоединился к #richfaces
[18:27:11] amarkhel: balunasj: 2 day to complete poll, 2 to param, maybe alex finish his work earlier, so I think discussion isn't needed now
[18:28:05] balunasj: alexsmirnov: when do you think you will know more about the validation changes that might effect msgs?
[18:28:11] alexsmirnov: amarkhel: validators at the architecture stage only, but they definitely have to be connected to messages.
[18:29:26] balunasj: alexsmirnov: do you think that connection will impact msgs dev time for A2?
[18:29:45] amarkhel: alexsmirnov: ok, but we have discuss this right before I start implement messages
[18:30:04] amarkhel: alexsmirnov: have = can
[18:30:11] alexsmirnov: In the 3.3., rich:messages stores information about its content, so single component can update its own messages without erasing ones from other components.
[18:31:26] shadowlr (~shadowl@189.100.167.82) присоединился к #richfaces
[18:31:35] alexsmirnov: rich:messade has no explicit code for validators.
[18:31:47] OndejZizka (~ondra@nat/redhat/x-eqenlgosikzivsro) вышел из IRC [ Ping timeout: 246 seconds ]
[18:32:26] balunasj: amarkhel: so for A2 it sounds like there might not be much impact
[18:32:48] balunasj: alexsmirnov: please coordinate with amarkhel if you feel there is something needed in A2 while you are working on validators.
[18:32:59] amarkhel: balunasj: agree
[18:33:11] shadowl (~shadowl@200-158-219-147.dsl.telesp.net.br) вышел из IRC [ Ping timeout: 246 seconds ]
[18:33:12] shadowlr теперь известен как shadowl
[18:33:12] balunasj: amarkhel: with that when do you estimate you will be completed with A2 dev work?
[18:34:40] amarkhel: balunasj: 7d for components and 2 other issues one day each, maybe next Friday...
[18:35:02] balunasj: amarkhel: next friday is our code freeze
[18:35:28] balunasj: amarkhel: so please get it done by then
[18:35:47] balunasj: nbelaevski: you covered a4j:apply in your comments
[18:35:55] amarkhel: balunasj: ok
[18:36:07] amarkhel: balunasj: I think it is possible
[18:36:25] balunasj: amarkhel: sorry - what about rich:* functions?  Is that just not up to date in jira?
[18:37:06] balunasj: RF-7642
[18:37:10] amarkhel: balunasj: rich* function is one of two tasks, 1 day needed
[18:37:21] balunasj: amarkhel: ok good thanks
[18:37:30]  (~kvirc@93.191.103.3) присоединился к #richfaces
[18:37:33] ilya_shaikovsky: Nick will reconnect now.. his client hanged
[18:37:38] 40FAAY0LP (~kvirc@93.191.103.3) присоединился к #richfaces
[18:37:39] 40FAAY0LP: sorry, I've dropped off
[18:37:40] 40FAAY0LP (~kvirc@93.191.103.3) вышел из IRC [ Client Quit ]
[18:37:45] : not a client, server
[18:37:57] nbelaevski (~kvirc@93.191.103.3) вышел из IRC [ Quit: When two people dream the same dream, it ceases to be an illusion. KVIrc 3.4.2 Shiny http://www.kvirc.net ]
[18:38:01] balunasj: alexsmirnov: I noticed you took a4j:actionListener
[18:38:02] : anyway, I'm back
[18:38:21] balunasj: that is good :-)
[18:38:36] balunasj: alexsmirnov: ilya_shaikovsky : are there any open items from forum thread for meeting?
[18:38:48] balunasj: I have been too busy this morning to read through latest
[18:39:52] ilya_shaikovsky: no.. lets continue that offline
[18:40:05] balunasj: ok good
[18:40:17] balunasj: next item is release artifact sforum thread
[18:40:28] balunasj: http://community.jboss.org/message/543625
[18:40:39] balunasj: alexsmirnov: have you had a chance to review?
[18:41:12] balunasj: alexsmirnov: I would like to make this into an article, but would like to have a section on your CDK artifact structure.
[18:42:46] balunasj: nick - could you change your nickname to what is usually is?
[18:43:13] balunasj: There is also the question of how to package the source for the project in the project release artifact
[18:43:36] alexsmirnov: Yes, I see that. I'm not sure that CDK needs distribution package at all, because it can work for maven builds only ( while it's easy to append ANT task or APT module ).
[18:43:37] balunasj: nick - have you had a change to see my reply to you on this?
[18:44:27]  теперь известен как nbelaevski
[18:44:32] balunasj: alexsmirnov: I thought we talked about that before.  That is would be good to have a cdk distribution to push, and highlight it as more than just a tool that richfaces uses
[18:44:42] balunasj: nbelaevski: aaahhh - much better :-)
[18:44:43] nbelaevski: balunasj: yes , I saw your reply
[18:44:55] nbelaevski: balunasj: great :)
[18:45:26] nbelaevski: balunasj: ok, so sources will include pom.xml and other necessary stuff
[18:45:42] nbelaevski: balunasj: like we already did for examples
[18:45:50] alexsmirnov: balunasj: I meant that there is no jar's that can be included to distribution, because all of them are maven - related.
[18:46:07] alexsmirnov: But there should be documentation and examples.
[18:46:28] balunasj: yup - basically - I would like to make sure a user could go into a /src direct and mvn clean install ( and rebuild from their local src ).
[18:46:31] balunasj: nbelaevski: ^
[18:47:08] balunasj: alexsmirnov: I think those examples, docs, archetyples, scripts, whatever could be good in its own release artifact.
[18:47:33] balunasj: alexsmirnov: keeping a separation of cdk and richfaces ui project
[18:47:36] nbelaevski: balunasj: rebuild core & ui, right?
[18:47:54] nbelaevski: balunasj: does user need to rebuild distribution?
[18:48:01] OndejZizka (~ondra@nat/redhat/x-bqfahgpwrunqiofa) присоединился к #richfaces
[18:48:02] balunasj: nbelaevski: no
[18:48:09] balunasj: nbelaevski: sorry - yes to the first
[18:48:14] balunasj: nbelaevski: no to the second
[18:48:22] nbelaevski: balunasj: ok, we are on the same page
[18:48:56] balunasj: nbelaevski: I would like to have instructions that we can give users on how to import with m2elclipse and
[18:49:13] balunasj: nbelaevski: get started changing source
[18:49:26] balunasj: nbelaevski: Then if the users are really intetested they can start looking at svn.
[18:49:54] balunasj: alexsmirnov: do you think a release artifact like that is possible?
[18:50:11] nbelaevski: balunasj: ok, got that
[18:50:29] balunasj: Alex_Kolonitsky: have you taken a look at the http://community.jboss.org/message/543625
[18:50:48] balunasj: Alex_Kolonitsky: you will be the one implementing most of this - I want ot make sure you are comfortable with it.
[18:51:02] alexsmirnov: balunasj:  Sure. I only meant that there no binary distribution that user can download and run.
[18:51:33] balunasj: alexsmirnov: ok sure - so a /lib directory would make no sense :-)
[18:52:12] balunasj: alexsmirnov: for main project dist we are requiring maven to build source - I don't have a problem with cdk requiring it either.
[18:54:06] balunasj: Alex_Kolonitsky: ping?
[18:55:15] alexsmirnov: balunasj: lib would make late, because it possible to append CDK as APT module to any javac build ( Eclipse lets to define such tool ).
[18:56:06] balunasj: alexsmirnov: "lib would make late" ? - you mean supporting that would make it late for release?
[18:56:41] Alex_Kolonitsky: yes
[18:56:49] Alex_Kolonitsky: I am looking
[18:56:57] alexsmirnov: would make sense :-). I haven't tested CDK in that mode yet.
[18:57:46] balunasj: alexsmirnov: I'm fine without having this support in A2 - we have a lot to get done in the next 2 weeks :-)
[18:58:20] balunasj: alexsmirnov: Although I would like at least a basic release artifact structure in place
[18:58:39] balunasj: Alex_Kolonitsky: ok please comment on the forums for any comments
[18:58:57] Alex_Kolonitsky: ok
[18:59:10] balunasj: alexsmirnov: will that be possible in A2 timeframe?
[18:59:45] alexsmirnov: I'm not sure, but it seems possible.
[19:00:25] balunasj: alexsmirnov: ok lets revist this part next week.
[19:00:46] balunasj: Next I want to finalize the module structure.
[19:00:58] balunasj: there has been some discussions internally about it.
[19:01:07] balunasj: Alex_Kolonitsky: did you see the last reply from me?
[19:01:28] balunasj: alexsmirnov: nbelaevski : have you guys had a change to look at it?
[19:02:32] nbelaevski: balunasj: yes, I'm following this discussion
[19:02:45] ppitonak (~ppitonak@paliboy.sks3.muni.cz) вышел из IRC [ Ping timeout: 258 seconds ]
[19:02:48] Alex_Kolonitsky: yes
[19:02:50] nbelaevski: balunasj: I prefer your variant more and we discussed this with Alex today
[19:03:20] nbelaevski: balunasj: Alex_Kolonitsky: I mean the one where aggregator is aggregator-only
[19:03:43] balunasj: nbelaevski: I just want to make sure we are talking about the same things
[19:03:54] Alex_Kolonitsky: yes, I understand
[19:04:10] balunasj: my comment "The aggregator does two things - manages modules, and assembly." is that the one that you agree with?
[19:04:34] balunasj: and <module>-parent would not manage any modules directly
[19:04:50] nbelaevski: "The aggregator should be managing the modules, not the parent." - this
[19:05:20] nbelaevski: balunasj: looking at assembly part - there's not much assembly information there
[19:05:20] paliboy (~ppitonak@paliboy.sks3.muni.cz) присоединился к #richfaces
[19:05:28] paliboy теперь известен как ppitonak
[19:05:46] balunasj: nbelaevski: ok and that goes along with my next comment and image below that in the email.
[19:05:56] nbelaevski: Alex_Kolonitsky: do you agree?
[19:06:22] nbelaevski: balunasj: sorry, I'm confused by the images - ThunderBird does not show tiff files
[19:06:34] nbelaevski: which one is that - 01 or 02?
[19:07:04] abelevich (~belevich_@93.191.103.3) покинул #richfaces [  ]
[19:07:20] balunasj: PastedGrapfic-1 is what exists now and what I think should stay
[19:07:38] Alex_Kolonitsky: yes, I am agree
[19:07:38] nbelaevski: yes, that's it
[19:07:40] balunasj: Aggregator handles modules, and any basic assembly work.
[19:07:51] Alex_Kolonitsky: I'll correct other modules
[19:08:03] nbelaevski: the only thing to improve is removing dependency to richfaces-parent from aggregator
[19:08:11] balunasj: for more complex assembly we have the /dist ( the ones with intermodule artifacts ).
[19:08:28] nbelaevski: I dislike these parallel lines of inheritance
[19:08:50] balunasj: nbelaevski: but then what will be the parent of aggregator?
[19:09:18] nbelaevski: balunasj: it can be without parent
[19:09:32] balunasj: nbelaevski: I think this was something that Alex_Kolonitsky brought up earlier in the emails - looking...
[19:11:01] balunasj: It may still have plugins and other items that should be controlled by richfaces-parent.
[19:11:07] balunasj: is there a reason to remove it?
[19:11:27] balunasj: i.e. - is it currently or future causing a problem?
[19:12:03] alexsmirnov: nbelaevski: If richfaces-parent has only meta-information and no build related code at all, aggregator can safely inherit it.
[19:12:22] nbelaevski: alexsmirnov: agree
[19:12:29] nbelaevski: balunasj: no problems I think
[19:12:40] balunasj: ok good - so I think that we are all on teh same page with that again :-)
[19:12:41] nbelaevski: balunasj: just to keep it simpler
[19:13:20] balunasj: Alex_Kolonitsky: you are going to update the module structure - where you already changed to other way correct?
[19:13:32] Alex_Kolonitsky: yes
[19:14:24] balunasj: lets move on to the next point
[19:14:26] nbelaevski: alexsmirnov: balunasj: Alex_Kolonitsky: richfaces-parent contains build-related code (e.g. checkstyle plugin configuration), but it should be ok inheriting  anyway
[19:14:45] balunasj: nbelaevski: those should be in pluginmanagement
[19:14:49] balunasj: looking...
[19:15:21] nbelaevski: unrelated plugins will ignore pom packaging project and it will work
[19:15:49] balunasj: the only thing outside of pluginmanagement is the release plugin for release the parent itself so I think it would be ok.
[19:17:03] balunasj: So next up is the /ui modules and getting component back into the /ui from /ui-sandbox
[19:17:15] balunasj: following the structure outlined above.
[19:17:29] balunasj above meaning in the structure wiki page
[19:17:56] balunasj: Alex_Kolonitsky: you have already moved over /ui/core correct?
[19:18:00] balunasj: Alex_Kolonitsky: is that complete?
[19:18:07] alexsmirnov: balunasj: release plugin in root should be marked <inherited>false for safety.
[19:18:22] balunasj: alexsmirnov: oh - good point
[19:18:45] balunasj: alexsmirnov: thanks
[19:20:14] balunasj: nbelaevski: while we wait for Alex_Kolonitsky to reply.  What do you think is the best way to get the components moved over.
[19:21:00] balunasj: nbelaevski: I know I have the migration process task still in place, but we can't wait for that I fear if we are going to make A2 timing.
[19:21:23] balunasj: nbelaevski: if needed we can update the components based on that process post A2.
[19:22:07] nbelaevski: balunasj: we can stop development and move code  to ui
[19:22:32] nbelaevski: balunasj: without formal review this time
[19:22:47] balunasj: nbelaevski: yeah - I think that is going to be needed for A2
[19:23:00] nbelaevski: balunasj: then when we get the process, QA team or dev. team will do formal review
[19:23:05] balunasj: we'll start that requirement for M1.
[19:23:13] balunasj: nbelaevski: exactly
[19:23:23] nbelaevski: balunasj: ok, we are on the same
[19:23:28] balunasj: nbelaevski: yup :-)
[19:23:35] balunasj: nbelaevski: so the question is who is the best for this
[19:23:47] nbelaevski: I'll do, it's easy
[19:24:03] nbelaevski: and I' most active coder in this module now :)
[19:24:05] wojtask9 (~d94a4402@gateway/web/freenode/x-wvwqvjvgnezkusss) присоединился к #richfaces
[19:24:25] balunasj: nbelaevski: easy - even with the structure in the wiki page?
[19:24:52] balunasj: nbelaevski: Seam has a archytype for new modules - I wonder if we should create the same
[19:25:04] balunasj: nbelaevski: perhaps not now
[19:25:21] balunasj: but would setup base bom, parent, agg, and structure.
[19:25:37] nbelaevski: balunasj: modules in sandbox should be already updated for new structure, so ideally I just rename groupId, commit and write e-mail on that change
[19:26:00] nbelaevski: balunasj: we have archetype for A1, but need to update it for A2
[19:26:55] alexsmirnov: I guess that Jay told about artefact for our own structure ( bom/parent/dist/etc... )
[19:27:21] alexsmirnov: s/arterfact/archetype/
[19:27:26] balunasj: nbelaevski: the difference is going to be the ones like /input that will contain several maven sub-modules
[19:28:29] balunasj: nbelaevski: broken up by type like in the left menu on live demo - http://livedemo.exadel.com/richfaces-demo/richfaces/editor.jsf
[19:28:51] balunasj: nbelaevski: again - just wanted to make sure we are on the same page
[19:29:00] shadowlr (~shadowl@189.100.167.82) присоединился к #richfaces
[19:29:03] Alex_Kolonitsky (~akolonits@93.191.103.3) покинул #richfaces [  ]
[19:30:16] balunasj: the next topic is on release process and release plugin
[19:30:21] nbelaevski: balunasj: ok, let's take this offline
[19:30:34] balunasj: alexsmirnov: and I already talked about this some, I think we are on the right track and I'll update
[19:30:36] nbelaevski: balunasj: I'm not sure I have the right vision now
[19:30:37] balunasj: nbelaevski: ok
[19:30:46] balunasj: nbelaevski: np
[19:31:08] balunasj: nbelaevski: alexsmirnov : do either of you have a problem if I release richfaces-parent, and richfaces-checkstyle
[19:31:24] nbelaevski: balunasj: no
[19:31:25] balunasj: These artifacts are the ones without 4.0.0-SNAPSHOT versions
[19:31:37] balunasj: it will help when we actually release the 4.0.0
[19:32:02] balunasj: nbelaevski: ok good
[19:32:13] alexsmirnov: balunasj: no problem
[19:32:27] shadowl (~shadowl@189.100.167.82) вышел из IRC [ Ping timeout: 276 seconds ]
[19:32:27] shadowlr теперь известен как shadowl
[19:32:33] balunasj: alexsmirnov: just to wrap up - did you see my comment on cdk module naming?
[19:32:48] alexsmirnov: balunasj: Where is it ?
[19:32:57] balunasj: bottom of the agenda - in comments
[19:33:08] balunasj: right now they are called bom, parent, etc...
[19:33:26] balunasj: in IDE it is very hard to differentiate them
[19:33:41] balunasj: same problem the other modules had before we discussed and I update
[19:33:44] balunasj: updated
[19:34:45] alexsmirnov: balunasj: I can see that, the comment about richfaces-cdk-* preffix ?
[19:34:52] balunasj: yup
[19:35:45] alexsmirnov: That could be my own taste of things, but I hate names like org.richfaces.cdk:richfaces-cdk-...
[19:36:40] balunasj: alexsmirnov: I understand, but I thought you were one of the ones that thought I should update my modules when I had the same thing ;-)
[19:36:52] alexsmirnov: richfaces.cdk already definer in groupId. These project are not supposed to import into IDE so I prefer to keep short names.
[19:37:37] balunasj: alexsmirnov: hmm - let me think about it - I'm not sure.
[19:38:17] alexsmirnov: balunasj: I only told about java modules, that would be propagated into IDE project and jar file names.
[19:38:24] balunasj: alexsmirnov: the other modules it makes it easy to differenciate in IDE - but this is really only going to effect people who are updating bom, parent, etc...
[19:38:32] balunasj: alexsmirnov: ah :-)
[19:38:40] balunasj: ok
[19:38:42] balunasj: alexsmirnov: also you plan to update cdk to have richfaces-parent as its parent right?
[19:39:05] balunasj: other than that I think I can touch base on the other topics offline
[19:39:16] alexsmirnov: Yes, I'll do that today.
[19:39:34] balunasj: alexsmirnov: ok cool
[19:39:49] balunasj: also last thing - I have my own local version of hudson runnign :-)
[19:39:52] nbelaevski: balunasj: ok, I'd like to discuss logging shortly
[19:40:13] balunasj: nbelaevski: shortly today, or shorting in 15min?
[19:40:38] nbelaevski: balunasj: any time today is fine for me
[19:41:19] balunasj: nbelaevski: ok - I've got to get some lunch so we can talk about logging, and ui structure a little later
[19:41:27] balunasj: nbelaevski: if that works for you.
[19:41:38] nbelaevski: balunasj: sure, np
[19:41:56] balunasj: nbelaevski: great
[19:41:57] alexsmirnov: nbelaevski: balunasj:  Just to information - I already suggested to use our own ligging interfaces that we can easely swich to any implementation.
[19:42:13] nbelaevski: alexsmirnov: yes - I remember that
[19:42:25] alexsmirnov: CDK uses such approach to integrate with Maven logging.
[19:42:34] balunasj: alexsmirnov: I agree - I think we may need that flexiblity - seam did the same thing to be honest
[19:42:49] nbelaevski: alexsmirnov: balunasj: I'm not great fan of slf4j after I worked some time with it
[19:42:50] alexsmirnov: So all code already in the project.
[19:43:13] balunasj: nbelaevski: I've also heard not good things
[19:43:58] balunasj: alexsmirnov: public interface Logger { right?
[19:44:15] alexsmirnov: Yes, there it is.
[19:44:31] balunasj: ok - I'll review
[19:44:43] balunasj: perhaps we should all be together for logging - and even UI
[19:44:59] balunasj: a little later today and we'll see if we are all online
[19:45:58] balunasj: ok guys - I need a bio break and stretch my legs - good meeting, and we'll talk later
[19:46:01] alexsmirnov: I'm going to office now and will be back online in 40-50 minutes
[19:46:10] balunasj: alexsmirnov: sounds good
[19:46:15] balunasj теперь известен как balunasj_away
[19:50:50] ppitonak (~ppitonak@paliboy.sks3.muni.cz) вышел из IRC [ Remote host closed the connection ]
[19:53:04] alexsmirnov (~alexsmirn@adsl-71-132-205-85.dsl.pltn13.pacbell.net) вышел из IRC [ Read error: Operation timed out ]