October 5, 2011 
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31
October 5, 2011 [00:04:23] <lightguard_jp> Drat [00:08:53] <sbryzak> morning all [00:09:04] <clerum> morning [00:09:57] <sbryzak> lightguard_jp: is it true that the mail module is dependent on seam reports? [00:10:15] <clerum> it isn't at this point [00:10:31] <sbryzak> clerum: ah, thanks [00:10:42] <sbryzak> are there plans to make it like that? [00:10:43] <clerum> I know we have talked about it [00:10:50] <clerum> but never moved forward on that [00:11:15] <lightguard_jp> sbryzak: It went out for the Beta with it though [00:11:33] <sbryzak> so is it or isn't it dependent? [00:11:44] <lightguard_jp> It's optional for the beta [00:11:56] <clerum> really? I must have missed it in the pom [00:11:58] <sbryzak> ah, an optional dependency [00:12:08] <lightguard_jp> The Seam Render portion is marked with @Requires [00:12:09] <sbryzak> how optional is it exactly? [00:12:13] <lightguard_jp> So it's not dependent on it at runtime [00:12:18] <clerum> oh wait [00:12:22] <clerum> Seam Render == Reports? [00:12:23] <lightguard_jp> The dep is set as provided [00:12:35] <lightguard_jp> sbryzak: wait, reports? [00:12:45] <lightguard_jp> No, it's never depended on reports [00:12:51] <sbryzak> yes, that's what rodney is asking [00:12:55] <sbryzak> i wonder if he means render [00:13:10] <clerum> it did dep on render but I'm pulling that out [00:13:13] <clerum> pulled that out [00:13:13] <sbryzak> so it has a dependency on render? [00:13:21] <clerum> in beta3 it does [00:13:25] <clerum> going forward it's gone [00:13:34] <sbryzak> so for cr1 in two weeks it will be gone? [00:13:40] <clerum> correct [00:13:44] <sbryzak> ok, thanks [00:14:05] <clerum> render was just causing issues due to it's neglect [00:14:36] <lightguard_jp> sbryzak: Yes [00:14:42] <lightguard_jp> We're actually thinking of doing a Beta4 [00:14:56] <lightguard_jp> I missed the solder dep, so it went out depending on Solder Beta2 [00:16:39] <sbryzak> i wouldn't do a beta4 just for that [00:16:54] <sbryzak> if we find a whole bunch of issues though, we can consider it [00:18:38] <clerum> sbryzak: I don't know how usable it is since it pulls in beta 2 [00:18:52] <clerum> and the logging and what not in mail points to the old packages names [00:19:01] <clerum> beta2 solder that is [00:19:43] <clerum> and since solder beta2 and beta3 are so much different than just version [00:19:47] <clerum> artifact, group, etc [00:19:58] <sbryzak> how is it pulling in beta2 for solder if the bom version was updated? [00:20:47] <clerum> https://github.com/seam/mail/blob/3.1.0.Beta3/impl/pom.xml#L40 [00:21:13] <clerum> https://github.com/seam/mail/blob/3.1.0.Beta3/pom.xml#L17 [00:21:34] <clerum> it was still using the beta 2 bom [00:23:43] <sbryzak> ah, that sucks [00:23:54] <sbryzak> hmm, i hope that isn't going to mess up the bundled distribution [00:24:54] <sbryzak> maybe not.. it seems ok [00:25:03] <sbryzak> are the docs going to be ready for cr1? [00:25:18] <clerum> yes [00:25:28] <sbryzak> great [00:25:35] <clerum> lightguard_jp: is just getting the test suite up and going [00:25:52] <clerum> but I have it working in my project in 3.1.0 snapshot with the solder fixes [00:26:06] <clerum> so I can work though the docs as a get it all working with my app this week [00:26:46] <hannelita> sbryzak: Ping [00:26:55] <sbryzak> clerum: cool, thanks [00:26:58] <sbryzak> hannelita: pong [00:27:11] <hannelita> sbryzak: Hi! is validation module ok for beta3? [00:27:36] <sbryzak> hannelita: yes, i got it released last night [00:28:50] <sbryzak> lightguard_jp: would you be able to build the module distributions and upload to sourceforge/docs.jboss.org ? [00:30:07] <lightguard_jp> sbryzak: If I remember how to upload to sourceforge :) [00:30:41] <sbryzak> if you like, i can do that bit and you can just do the docs and update jira? [00:30:44] <sbryzak> up to you :) [00:31:14] <sbryzak> i'm still struggling to get the bundled distribution fixed [00:31:25] <sbryzak> for some reason it's excluding the sources from the assembly [00:31:31] <sbryzak> and i still have no idea why [00:34:24] *** kevinpollet has quit IRC [00:37:07] <lightguard_jp> Ouch [00:39:40] *** iphands_ has joined #seam-dev [00:40:17] *** rmartinelli_ has joined #seam-dev [00:40:17] *** tsurdilo2 has quit IRC [00:40:32] *** tsurdilo has joined #seam-dev [00:42:14] *** sgilda has joined #seam-dev [00:42:21] *** alazarot has joined #seam-dev [00:42:21] *** mbg has quit IRC [00:42:22] *** iphands has quit IRC [00:42:31] *** iphands__ has joined #seam-dev [00:42:50] *** mbg has joined #seam-dev [00:42:50] *** ChanServ sets mode: +v mbg [00:43:23] *** rmartinelli has quit IRC [00:43:53] *** alazarot has quit IRC [00:46:01] *** iphands_ has quit IRC [00:46:14] *** lazarotti has quit IRC [00:46:18] *** rmartinelli_ has quit IRC [00:47:59] <hannelita> lightguard_jp: Ping [00:51:21] <hannelita> sbryzak: Thanks!! Everything working here for beta3!!! Thanks a lot!!!! [00:51:37] <sbryzak> awesome, good news [00:52:22] <lightguard_jp> hannelita: pong [00:52:40] <hannelita> lightguard_jp: confbuzz with beta3 support [00:52:46] <lightguard_jp> excellent [00:52:50] <hannelita> lightguard_jp: can i pull request? [00:53:00] <lightguard_jp> of course [00:53:30] <hannelita> lightguard_jp: Hope I dont get format problems this time :( [00:54:05] <lightguard_jp> I'll clean them up if you do. [00:54:17] <lightguard_jp> clerum: Tests build and run. They fail, but I'm getting closer [00:54:45] <clerum> asserts fail or is it a test setup issue? [00:55:22] <lightguard_jp> Pulling in a dep. I'll have to rework it use shrinkwrap resolver stuff [00:55:31] <clerum> ah gottcha [00:55:48] <clerum> yeah thats the part I was worried about. I think it's way behind [00:56:03] <lightguard_jp> No problem [00:57:59] <sbryzak> yay, source code is back in the distribution [00:58:19] <hannelita> lightguard_jp: Did yu receive the pull request?? [00:58:40] <jbossbot> git [dist] push master 6c8a38d.. Shane Bryzak fix source code inclusions [00:58:40] <jbossbot> git [dist] push master URL: http://github.com/seam/dist/compare/e992acf...6c8a38d [00:58:40] <sbryzak> i *think* we're ready to release the bundle now [00:59:26] <lightguard_jp> Yeah, I have it [01:00:26] <sbryzak> lightguard_jp: did we have something lined up for the next seam hack night? [01:00:54] *** lazarotti has joined #seam-dev [01:01:41] <lightguard_jp> hannelita: Why did you change the settings.xml? [01:01:55] <lightguard_jp> Helping people get setup [01:02:01] <lightguard_jp> essentially a live QA [01:02:05] <lightguard_jp> Q&A [01:02:15] <lightguard_jp> Hopefully those at J1 remember to announce it [01:02:17] <hannelita> wtf, I didnt open this [01:02:29] <hannelita> hmmmmm [01:02:30] <hannelita> wait [01:02:32] <sbryzak> hmm, can we possibly change it to a bug fixing night for CR1? [01:02:40] <hannelita> let me check at whatchanged -p [01:02:48] <sbryzak> and postpone the Q&A for post 3.1? [01:03:00] <lightguard_jp> hannelita: Looking good [01:03:07] <lightguard_jp> sbryzak: Sure [01:03:24] <sbryzak> that would be great.. we were planning to do it next week? [01:04:21] <hannelita> lightguard_jp: Where is this archive? :o [01:04:45] <lightguard_jp> sbryzak: Yes [01:04:57] <lightguard_jp> sbryzak: We should add the shrinkwrap resolver stuff to the parent pom [01:05:38] <lightguard_jp> hannelita: Oh, I might have removed it, you had a to a rebase or some other non FF merge, didn't you? [01:06:04] <hannelita> let me try again [01:06:06] <hannelita> just a sec [01:06:30] <sbryzak> lightguard_jp: sure, make a note of it or raise a jira for us to add it in CR1 [01:06:38] <lightguard_jp> hannelita: Merged [01:07:18] <hannelita> lightguard_jp: Thats weird, because this file doesnt even exist in my fork [01:07:29] <lightguard_jp> hannelita: Have you signed a CLA? [01:07:32] <hannelita> lightguard_jp: besides this, is everything k? [01:07:39] <lightguard_jp> hannelita: Yep [01:07:45] <lightguard_jp> It merged straight from github [01:07:47] <hannelita> lightguard_jp: Ok, good, thanks [01:08:33] <sbryzak> lightguard_jp: CLA not required for apache 2 licensed projects [01:08:35] <hannelita> lightguard_jp: Now I need to fix import and annotation stuff from another branch that contains security stuff [01:09:36] <lightguard_jp> sbryzak: I keep hearing mixed messages about that [01:09:46] <sbryzak> i followed it up with legal [01:09:59] *** mbg has quit IRC [01:10:45] <sbryzak> bundled distribution is done! https://sourceforge.net/projects/jboss/files/Seam/3/3.1.0.Beta3/? [01:12:04] <sbryzak> wow, over 16k downloads for the 3.0.0 bundle [01:12:10] <sbryzak> that's a lot of users not using maven [01:12:28] <lightguard_jp> Yep [01:12:38] <lightguard_jp> sbryzak: Okay, if that was Legal's final word [01:13:08] <sbryzak> lightguard_jp: so are you ok to upload docs/module distributions while i update jira and write up the announcement? [01:13:26] <lightguard_jp> Yeah, I can do that [01:13:35] <lightguard_jp> Validation as well? [01:13:45] <sbryzak> yep, validation too [01:13:49] <sbryzak> thanks [01:14:07] <sbryzak> lightguard_jp: is the hack night planned for next week? [01:16:48] <lightguard_jp> Second thursday of the month [01:17:04] <lightguard_jp> Yes, should be on the 13th [01:20:38] <sbryzak> great, that timing works out well [01:20:49] <sbryzak> when i'm going through jira i'll build a list of all outstanding issues [01:24:57] <lightguard_jp> great [01:40:42] <hannelita> hey all [01:41:05] <hannelita> some ppl here at the placae I work are doing a research related to code quality [01:41:33] <hannelita> I showed them some code existing in some of seam modules, and they suggested some refactors [01:42:04] <hannelita> can I pull request it? [01:42:14] <sbryzak> hannelita: sure [01:42:18] <sbryzak> which module/s? [01:42:31] <hannelita> i showed the some classes at security module [01:42:35] <hannelita> and persistence module [01:43:08] <sbryzak> no problem, let me know when it's sent and i can apply [01:45:23] <hannelita> sbryzak: Thanks! [01:53:43] <sbryzak> i love the new jira interface [01:53:52] <sbryzak> drag and drop version ordering, very nice [01:56:23] <clerum> any jsf guru's around? [01:59:10] <clerum> bleathem: i figured out what is happening and how to work around it. but need help understanding if it is a seam-faces issue or a mojarra issue [02:01:53] <lightguard_jp> clerum: If Brian isn't here, I may be able to help [02:02:10] *** alesj has joined #seam-dev [02:03:18] <clerum> so using the uiinputcontainer from seam faces [02:03:21] <clerum> https://gist.github.com/f2b7781f2773bd6e97bc [02:03:44] <clerum> and then using it on a page like so [02:03:44] <clerum> https://gist.github.com/1e0c7b334b473b09665d [02:04:00] <clerum> if I want to set an id on it and then rerender it [02:04:14] <clerum> set an id on it for the purposes of render="" [02:05:08] <clerum> the problem is that when it's gets rendered out to the page the id gets slapped on twice [02:05:24] <clerum> id="j_idt51:j_idt52:accountManagerDecorate:accountManager" [02:05:43] <clerum> id gets assiged to the composite I guess and then also to the panelgroup inside [02:06:34] <clerum> which may be correct I'm just wondering the best way to handle this [02:06:40] <clerum> as it's going to be common [02:06:57] <lightguard_jp> can you post more of the page? [02:08:30] <lightguard_jp> clerum: Add an id to the h:form and tell me what you get please [02:08:44] <clerum> yep [02:09:22] <lightguard_jp> Or if you can screenshot the component tree from a ui:debug [02:09:32] <clerum> id="fooForm:j_idt52:accountManagerDecorate:accountManagerDecorate" [02:09:53] <lightguard_jp> Okay, so that unassigned id is from the decorateContainer it appears [02:10:11] <lightguard_jp> sorry decoratePanel [02:10:28] <clerum> yep [02:10:31] <clerum> thats my guess [02:10:58] <clerum> but I think the issue is that I want to set an id on the composite compoent for the purposes of rerendering it [02:11:01] <lightguard_jp> Add an id, or check via ui:debug [02:11:24] <lightguard_jp> Hm... composite components are not my strong suite [02:11:38] *** msmigielski has joined #seam-dev [02:11:47] <clerum> so if I use the value "id" it gets assiged to the composite and to the h:panelgrid via #{cc.attrs.id} [02:11:51] <lightguard_jp> couldn't you using @parent ? [02:11:51] <clerum> gottcha [02:12:01] <clerum> for rerender? [02:12:04] <lightguard_jp> Yeah [02:12:13] <lightguard_jp> If you're rendering from within it [02:12:37] <clerum> not farmiliar with @parent [02:12:53] <clerum> sure that one is real? [02:15:02] <lightguard_jp> double checking [02:15:11] <clerum> you may have dreamed that one up :-) [02:15:14] <clerum> would be very nice though [02:16:03] <lightguard_jp> http://docs.jboss.org/richfaces/latest_4_0_X/Developer_Guide/en-US/html/chap-Developer_Guide-Basic_concepts.html [02:16:06] <lightguard_jp> I think it's JSF2 [02:16:15] <bleathem> hey [02:16:30] <bleathem> was afk for a bit [02:16:33] <clerum> not in my jsf 2 complete ref [02:16:37] <bleathem> you guys getting it all figured out? [02:16:50] <clerum> bleathem so what is happening [02:17:15] <clerum> is I want to have an id on my composite component so that I can use it as a render="" target [02:17:22] <lightguard_jp> Guess not [02:17:52] <clerum> if define the param id and then use that to set the id on a panel group in the composite https://gist.github.com/f2b7781f2773bd6e97bc [02:18:04] <lightguard_jp> clerum: I think a better approach, which would also help with perf down the road would be to use regions and only process / send events from the region [02:18:08] <clerum> then that id gets appended twice [02:18:24] <lightguard_jp> clerum: You should also be able to rerender the region id [02:18:37] <bleathem> <h:panelGroup id="#{cc.attrs.id}" [02:18:41] <bleathem> that is problematic [02:18:53] <bleathem> you are assigning the id of the composite component itself [02:19:08] <clerum> yep thats what I was afraid of [02:19:17] <clerum> so would it be better to rename the param to divId [02:19:22] <bleathem> right [02:19:31] <clerum> <h:panelGroup id="#{cc.attrs.divId}" [02:19:40] <bleathem> that'd work [02:19:41] *** alesj has quit IRC [02:20:11] <clerum> or...would it be better to not assign the "id" to the composite...and let it be auto assigned? [02:20:16] <clerum> or is that even possible [02:20:43] <clerum> I'm thinking that this is going to be a common user pattern using https://github.com/seam/faces/blob/3.1.0.Beta3/api/src/main/java/org/jboss/seam/faces/component/UIInputContainer.java [02:20:51] <lightguard_jp> clerum: the autogenerated id will be problematic for testing [02:21:08] <clerum> true [02:21:23] <clerum> unfortuantly the id of the composite is not a valid target for render="" [02:21:38] <clerum> using it as divId should work [02:28:56] *** tkimura has joined #seam-dev [02:30:01] <clerum> yep that works perfect [02:30:08] *** pmuir has joined #seam-dev [02:30:25] <clerum> so may want to tweak the suggested composite [02:33:53] <clerum> @parent for render though [02:34:03] <clerum> that would be awesome...has the EG considered that? [02:38:03] *** hannelita has quit IRC [02:46:49] <sbryzak> lightguard_jp: how are the distribution releases going? [02:47:14] <sbryzak> lightguard_jp: we also need to update sfwk.org [02:47:35] <lightguard_jp> sbryzak: Stuck trying to get mail testsuite setup. [02:47:41] <lightguard_jp> May need to table it for now [02:49:32] <lightguard_jp> sbryzak: I'll do them later tonight, probably after all the kids are bed at this point. [02:49:40] <sbryzak> yeah don't worry about the testsuite right now, it's released anyway ;) [02:49:54] <sbryzak> and we can ask the qa guys to help with it later today [02:50:35] <lightguard_jp> Thought it would be one of those 30 minute kind of things [02:50:45] <jbossbot> git [mail] push testsuite 1f4285e.. LightGuard Adding testsuite [02:50:45] <jbossbot> git [mail] push testsuite 55947a9.. LightGuard Trying to get tests working [02:50:45] <jbossbot> git [mail] push testsuite URL: http://github.com/seam/mail/compare/0000000...55947a9 [02:50:57] <lightguard_jp> Well, there's the work in progress :) [02:50:59] *** pmuir has quit IRC [02:51:51] <sbryzak> i'll get the announcement written up by the end of today [02:51:57] <sbryzak> it's going to take quite a bit of work i think [02:52:13] <sbryzak> so much has changed [02:54:43] <lightguard_jp> Indeed [03:03:18] *** pmuir has joined #seam-dev [03:05:56] *** akazakov has quit IRC [03:10:12] *** pmuir has quit IRC [03:10:47] *** amitev has quit IRC [03:11:22] *** amitev has joined #seam-dev [03:29:46] *** amitev has quit IRC [03:29:59] *** amitev has joined #seam-dev [03:30:18] *** lightguard_jp has quit IRC [03:33:50] *** amitev has quit IRC [03:34:25] *** amitev has joined #seam-dev [04:09:30] *** amitev has quit IRC [04:09:41] *** amitev has joined #seam-dev [04:15:04] *** amitev has quit IRC [04:15:18] *** amitev has joined #seam-dev [04:16:36] <jbossbot> git [mail] push testsuite fde7f04.. Cody Lerum more fixes to get closer to running tests [04:16:36] <jbossbot> git [mail] push testsuite URL: http://github.com/seam/mail/compare/55947a9...fde7f04 [04:18:09] *** amitev has quit IRC [04:18:20] *** amitev has joined #seam-dev [04:27:54] *** amitev has quit IRC [04:28:29] *** amitev has joined #seam-dev [04:39:52] *** amitev has quit IRC [04:40:12] *** amitev has joined #seam-dev [04:41:33] *** amitev has quit IRC [04:42:08] *** amitev has joined #seam-dev [04:43:33] *** hannelita has joined #seam-dev [04:46:14] <sbryzak> geez 2 downloads of the release already and i haven't even announced it yet [04:47:58] *** msmigielski has quit IRC [05:08:52] *** rruss has joined #seam-dev [05:22:36] <sbryzak> lightguard_jp: ping [05:22:53] <sbryzak> oh, he's offline [05:58:31] *** maxandersen1 has joined #seam-dev [05:59:04] *** hannelita has quit IRC [06:01:17] *** maxandersen has quit IRC [06:14:13] *** clerum has quit IRC [06:20:49] *** tsurdilo has quit IRC [06:21:11] *** lightguard_jp has joined #seam-dev [06:21:11] *** ChanServ sets mode: +o lightguard_jp [06:35:48] <lightguard_jp> sbryzak: Uploading docs [06:41:31] <sbryzak> lightguard_jp: thanks [06:41:37] <sbryzak> i've done the bundled docs already btw [06:54:23] <lightguard_jp> Okay, perfect. [06:54:37] <lightguard_jp> I copied all the stuff for sshfs in a script, makes it a little easier [06:55:38] <lightguard_jp> We should create scripts for all this stuff if we can't get jenkins up and running quickly [06:56:55] <lightguard_jp> What were the refactorings Hanneli had for you? [07:06:11] <lightguard_jp> cd jms && git pull origin && git checkout 3.1.0.Beta3 && mvn clean verify -Drelease -pl api,docs && ../build/upload_docs.sh jms 3.1.0.Beta3 -- thing of beauty [07:06:33] <lightguard_jp> Could be a little easier, but I'll take what I can get right now [07:24:27] *** daniel_hinojosa has quit IRC [07:32:43] *** bleathem has quit IRC [07:36:57] <lightguard_jp> sbryzak: ping [07:46:52] *** bdlink has joined #seam-dev [07:49:01] *** bdlink has quit IRC [07:54:07] *** tremes has joined #seam-dev [07:56:30] *** sbryzak has quit IRC [07:57:25] *** sbryzak has joined #seam-dev [07:57:25] *** sbryzak has quit IRC [07:57:25] *** sbryzak has joined #seam-dev [07:57:25] *** ChanServ sets mode: +o sbryzak [07:57:36] <sbryzak> lightguard_jp: sorry, computer died [07:57:55] <lightguard_jp> sbryzak: Can you do rest, I can't get it to build from the tag [07:58:05] <sbryzak> sure [07:59:39] <lightguard_jp> validation and wicket left. [07:59:46] <lightguard_jp> Then to do the bundle updates to sourceforge [08:02:30] *** rruss has quit IRC [08:05:44] *** bleathem has joined #seam-dev [08:05:44] *** ChanServ sets mode: +v bleathem [08:14:22] *** bleathem has quit IRC [08:16:25] *** mbg has joined #seam-dev [08:16:25] *** ChanServ sets mode: +v mbg [08:16:34] <sbryzak> lightguard_jp: rest distribution has been uploaded to sourceforge, and the docs are almost uploaded too [08:17:38] <sbryzak> lightguard_jp: and just sent you mail [08:30:23] *** koentsje has joined #seam-dev [08:31:25] <lightguard_jp> sbryzak: responded [08:31:39] <lightguard_jp> sbryzak: How are you uploading to sourceforge? [08:31:45] <sbryzak> lightguard_jp: thanks [08:31:46] <lightguard_jp> sftp, rsync, web? [08:31:51] <sbryzak> just through the web interface [08:33:23] <sbryzak> lightguard_jp: validation was in 3.0.0 [08:34:19] <sbryzak> lightguard_jp: so how does the templating work in mail right now? [08:34:35] <sbryzak> does it have support for velocity and freemarker in this release? [08:39:45] <lightguard_jp> Yes [08:49:51] *** rruss has joined #seam-dev [08:51:06] *** msmigielski has joined #seam-dev [08:53:03] *** oskutka has joined #seam-dev [08:55:06] *** msmigielski has quit IRC [08:57:03] *** maxandersen1 has quit IRC [08:58:11] *** msmigielski has joined #seam-dev [09:01:06] *** maschmid has joined #seam-dev [09:03:18] *** kevinpollet has joined #seam-dev [09:04:06] *** mathieuancelin has joined #seam-dev [09:04:06] <lightguard_jp> sbryzak: Can you upload security to sourceforge? [09:04:33] <lightguard_jp> It's looking for a seam-security-reference-guide.war [09:10:18] *** kpiwko has joined #seam-dev [09:12:45] <lightguard_jp> sbryzak: It looks like I also messed up on the dist for mail (too many things to check :( ). It's still called seam-mail-impl [09:13:02] <lightguard_jp> That should be in the release blog [09:13:13] <lightguard_jp> It'll get fixed as soon as I'm done uploading the other stuff [09:18:45] *** pchowaniec has joined #seam-dev [09:18:58] *** pchowaniec has left #seam-dev [09:21:20] *** jharting has joined #seam-dev [09:21:24] <lightguard_jp> sbryzak: Got security [09:21:27] <lightguard_jp> they're all done now [09:24:20] *** kpiwko has quit IRC [09:26:17] *** kpiwko has joined #seam-dev [09:30:58] *** msmigielski has quit IRC [09:37:23] <jbossbot> git [security] push develop 806c941.. LightGuard fixing dist contents from the impl rename [09:37:24] <jbossbot> git [security] push develop URL: http://github.com/seam/security/compare/d7deb83...806c941 [09:44:42] *** maxandersen has joined #seam-dev [09:47:13] *** lazarotti has quit IRC [09:48:00] *** msmigielski has joined #seam-dev [09:50:38] <jbossbot> git [mail] push develop a67b4f4.. LightGuard Fixing the dist [09:50:38] <jbossbot> git [mail] push develop URL: http://github.com/seam/mail/compare/918ea6e...a67b4f4 [09:51:31] <jbossbot> git [mail] push testsuite a67b4f4.. LightGuard Fixing the dist [09:51:31] <jbossbot> git [mail] push testsuite 5698863.. LightGuard Adding testsuite [09:51:31] <jbossbot> git [mail] push testsuite 6350b72.. LightGuard Trying to get tests working [09:51:31] <jbossbot> git [mail] push testsuite 6d995a6.. Cody Lerum more fixes to get closer to running tests [09:51:32] <jbossbot> git [mail] push testsuite 4cd1ca3.. LightGuard Merge remote-tracking branch 'origin/feature/testsuite' into feature/testsuite [09:51:33] <jbossbot> git [mail] push testsuite URL: http://github.com/seam/mail/compare/fde7f04...4cd1ca3 [09:55:52] <jbossbot> git [jms] push develop 47b40ad.. LightGuard Fixing the dist [09:55:52] <jbossbot> git [jms] push develop 03e6b60.. LightGuard Enabling the testsuite again [09:55:52] <jbossbot> git [jms] push develop URL: http://github.com/seam/jms/compare/8c41425...03e6b60 [09:58:04] <jbossbot> git [faces] push develop 51e3749.. LightGuard Fixing dist [09:58:04] <jbossbot> git [faces] push develop URL: http://github.com/seam/faces/compare/10ed88a...51e3749 [10:00:53] <lightguard_jp> sbryzak: Solder also doesn't follow the naming convention, it's solder-impl as well [10:07:21] *** kevinpollet has quit IRC [10:08:33] *** jharting has quit IRC [10:09:34] <lightguard_jp> nickarls: If you're using any of the same modules, care to take a stab at http://seamframework.org/Community/ThereIsATranscationExceptionSometime ? [10:09:41] *** deneme has joined #seam-dev [10:09:52] <deneme> Hi, can I ask a question please? [10:10:08] <deneme> I use wicket for my view tier. [10:10:16] <deneme> With seam. [10:10:26] <deneme> Namely, not JSF, or RichFaces. [10:10:46] <deneme> For security, I try to use PicketLink [10:11:30] <deneme> Can I use UserAction, and GroupAction programatically [10:11:39] <deneme> for wicket submits like this? [10:11:41] <deneme> @Inject UserAction userAction; [10:11:41] <deneme> @Override [10:11:41] <deneme> public final void onSubmit() [10:11:41] <deneme> { [10:11:41] <deneme> try { [10:11:41] <deneme> ValueMap values = getModelObject(); [10:11:41] <deneme> String deneme=values.getString("denemeText"); [10:11:42] <deneme> userAction.setFirstname("firstname"); [10:11:42] <deneme> userAction.setLastname("lastname"); [10:11:43] <deneme> userAction.setUsername(deneme); [10:11:43] <deneme> userAction.save(); [10:11:44] <deneme> } catch (Exception e) { [10:13:02] <deneme> sbryzak [10:13:45] <lightguard_jp> deneme: You should be able to [10:17:45] *** kevinpollet has joined #seam-dev [10:20:17] <deneme> lightguard_jp thanks for reply [10:20:28] <deneme> i ask because i get this errors [10:20:30] <deneme> https://docs.google.com/document/d/1V-xpFNoRld-CLZJObwxjQ9yau8WNLNPNh4dg15xoq_I/edit?hl=tr# [10:20:36] *** rruss has quit IRC [10:20:41] <deneme> when i try to use [10:21:04] <deneme> UserAction programatically [10:21:09] <lightguard_jp> deneme: http://pastie.org/ [10:21:57] <lightguard_jp> deneme: Here's your error: Error creating IdentitySession - no PicketLink IdentityStore repositories have been configured. [10:22:40] <lightguard_jp> deneme: You'll need to follow the docs on setting up the JPAIdentityStore, or some other identity store for your application [10:22:55] <deneme> http://pastie.org/2642555 [10:24:07] <lightguard_jp> deneme: Yep: 11:08:45,471 ERROR [stderr] (http--127.0.0.1-8080-4) Caused by: org.picketlink.idm.common.exception.IdentityException: Error creating IdentitySession - no PicketLink IdentityStore repositories have been configured. [10:27:15] <deneme> Yes, I use seam-bean.xml like this:http://pastie.org/2642560 [10:27:35] <deneme> In the picketlink code: [10:27:37] <deneme> IdentityStoreRepository repo = bootstrappedRepositories.get(metaData.getIdentityRepositoryIdRef()); [10:27:45] <deneme> repo is null [10:28:09] <deneme> so in the same method [10:28:12] <deneme> IdentitySessionConfigurationContext sessionConfigCtx = [10:28:12] <deneme> new IdentitySessionConfigurationContext(realmName, configMD, repo, mapper, provider, configurationContext, metaData.getOptions()); [10:28:22] <deneme> the repo parameter is null. [10:28:28] <deneme> What is repo man :) [10:28:59] <deneme> I read document, maybe i am stupid or something else, can not understand how i can configure repo. [10:29:11] <lightguard_jp> deneme: Can you paste your IdentityObject and IdentityCredential? [10:29:33] <deneme> IdentityObject.java? [10:29:50] <lightguard_jp> You can think of it as picketlink's abstraction over the identity data store (db, ldap, etc) [10:29:52] <lightguard_jp> yes [10:30:05] <lightguard_jp> Add those two classes to a pastie [10:30:15] <lightguard_jp> or pastbin, or whichever you prefer [10:30:28] <deneme> oke [10:30:42] <deneme> IdentityObject:http://pastie.org/2642585 [10:31:51] <deneme> IdentityObjectCredential:http://pastie.org/2642589 [10:32:06] <deneme> This javas are copy-paste from document as you see [10:32:07] <deneme> :) [10:37:31] <lightguard_jp> IdentityObjectCredential line 51 change TYPE to CREDENTIAL [10:37:38] <lightguard_jp> See if that works for you [10:38:28] <deneme> Ah, oke [10:41:56] <lightguard_jp> Any luck? [10:43:11] <deneme> nope [10:43:13] <deneme> <deneme> IdentitySessionConfigurationContext sessionConfigCtx = [10:43:13] <deneme> <deneme> new IdentitySessionConfigurationContext(realmName, configMD, repo, mapper, provider, configurationContext, metaData.getOptions()); [10:43:25] <deneme> in this method, repo and provider is null yet [10:45:10] *** jharting has joined #seam-dev [10:46:57] <lightguard_jp> deneme: Hm, you're missing something, if you debug the JpaIdentityStore class, method bootstrap I'm sure you'll get something. [10:47:10] *** jharting has quit IRC [10:47:12] <deneme> Oke, I will try to decug [10:47:17] <lightguard_jp> I'm sure you're missing something in your setup, just not sure what it is. [10:47:18] <deneme> thanks for your help [10:47:21] <lightguard_jp> I'm probably missing something small [10:47:33] <lightguard_jp> It's almost 3:00 AM here, I'm getting tired :) [10:47:41] <deneme> I see :) [10:47:46] *** mgoldmann has joined #seam-dev [10:47:51] <lightguard_jp> deneme: Best of luck [10:47:52] *** mgoldmann has quit IRC [10:47:52] *** mgoldmann has joined #seam-dev [10:48:13] *** jharting has joined #seam-dev [10:48:14] <deneme> Thanks for your help, i will be right back to send feedback. [10:48:19] <deneme> thanks [10:49:42] *** deneme has quit IRC [10:56:48] *** tkimura has quit IRC [10:58:16] <maschmid> deneme: Since 3.1.0.Beta3 you can now configure IdentityEntities with annotations (e.g. @IdentityEntity(IDENTITY_OBJECT), instead of configuring JpaIdentityStoreConfiguration see https://github.com/seam/security/blob/develop/examples/idmconsole/src/main/java/org/jboss/seam/security/examples/idmconsole/model/IdentityObject.java [11:19:16] *** sannegrinovero has quit IRC [11:19:30] *** lightguard_jp has quit IRC [11:21:53] *** tremes is now known as tremes_afk [11:24:57] *** deneme has joined #seam-dev [11:31:41] *** deneme has quit IRC [11:44:50] *** tsurdilo has joined #seam-dev [11:52:15] *** tsurdilo has quit IRC [11:53:10] *** tsurdilo has joined #seam-dev [12:08:39] *** sannegrinovero has joined #seam-dev [12:19:38] <jbossbot> git [rest] push develop 5eece12.. Jozef Hartinger a lot of minor fixes [12:19:38] <jbossbot> git [rest] push develop 9de25c3.. Jozef Hartinger Adapt to recent changes in solder [12:19:38] <jbossbot> git [rest] push develop URL: http://github.com/seam/rest/compare/16d7764...9de25c3 [12:25:26] *** mgoldmann has quit IRC [12:25:45] *** mgoldmann has joined #seam-dev [12:46:18] *** msmigielski has quit IRC [12:46:59] *** mgoldmann has quit IRC [13:05:14] *** deneme has joined #seam-dev [13:05:19] * deneme re. [13:06:43] <maschmid> deneme: Since 3.1.0.Beta3 you now configure IdentityEntities with annotations (e.g. @IdentityEntity(IDENTITY_OBJECT), instead of configuring JpaIdentityStoreConfiguration in seam-beans.xml see https://github.com/seam/security/blob/develop/examples/idmconsole/src/main/java/org/jboss/seam/security/examples/idmconsole/model/IdentityObject.java [13:07:18] <deneme> it is good news ;) [13:07:31] <deneme> Thanks for help. I will try and send feedback [13:08:20] <deneme> Oke. It means, that if I set annotations [13:08:29] <deneme> I dont need seam-beans.xml [13:08:31] <deneme> right [13:08:33] <deneme> ? [13:09:42] <maschmid> deneme: depends, if there is anything else besides the configuration of JpaIdentityStoreConfiguration [13:10:05] <deneme> Can I ask another quest [13:10:21] <deneme> what is the diffrence between beans.xml and seam-beans.xml [13:14:10] <maschmid> deneme: behavior of beans.xml is defined by standard (CDI), the ability to configure beans in XML is an extension provided by Solder... some CDI implementations does not allow such extensions to read from beans.xml, therefore solder reads it also from seam-beans.xml [13:20:37] <deneme> maschmid, thanks for the explanation. [13:22:51] <deneme> maschmid, now the repo is not null. I tried to follow your advise [13:23:19] <deneme> but, I get a nullpointer exception about entityManager [13:23:20] <deneme> I tried your advise [13:23:23] <deneme> pardon [13:23:35] <deneme> http://www.pastie.org/2643195 [13:26:02] *** mkouba has joined #seam-dev [13:39:43] *** mgoldmann has joined #seam-dev [13:43:34] *** mgoldmann has quit IRC [13:59:17] *** mgoldmann has joined #seam-dev [14:03:07] *** rmartinelli has joined #seam-dev [14:09:58] *** kenfinnigan has joined #seam-dev [14:09:59] *** ChanServ sets mode: +v kenfinnigan [14:11:24] *** jose_freitas has joined #seam-dev [14:12:09] <deneme> It is about this code [14:12:12] * deneme if (!entityManagerInstance.isUnsatisfied() && !entityManagerInstance.isAmbiguous()) { [14:12:13] <deneme> sessionOptions.put(SESSION_OPTION_ENTITY_MANAGER, entityManagerInstance.get()); [14:12:13] <deneme> sessionOptions.put(SESSION_OPTION_IDENTITY_OBJECT_CREATED_EVENT, identityObjectCreatedEvent); [14:12:13] <deneme> } [14:13:10] <deneme> sessionOptions will be empty, because entityManagerInstance.isUnsatisfied(), entityManagerInstance.isAmbiguous() are true [14:13:45] <deneme> So entityManager will be null because sessionOption is null [14:17:28] *** mgoldmann has quit IRC [14:24:50] <maschmid> deneme: Do you have an @Produces @ExtensionManaged @ConversationScoped @PersistenceUnit EntityManagerFactory anywhere? It doesn't seem to be documented, which is a bug, but seam security depends on seam persistence and it does appear that it depends on a configured @ExtensionManaged EntityManager. [14:26:30] *** alesj has joined #seam-dev [14:27:34] <deneme> I dont have but, I see something like this in your example [14:27:51] <deneme> EntityManagerProducer.java [14:27:58] <deneme> I can copy-paste [14:28:13] <deneme> but what invoces it? [14:28:23] <deneme> @Produces ? [14:29:23] <deneme> maschmid [14:29:26] <maschmid> deneme: there is some (a bit not up to date) documentation about it in http://docs.jboss.org/seam/3/persistence/3.1.0.Beta3/reference/en-US/html/persistence.html#persistence.seam-managed-persistence-contexts [14:30:38] <deneme> Oke, I will look over [14:32:29] <deneme> maschmid, thanks it is figured out by EntityManagerProducer.java [14:32:40] <deneme> now, em is not null [14:51:57] *** alesj has quit IRC [14:57:47] *** Diablo-D3 has quit IRC [15:04:29] *** maxandersen has quit IRC [15:25:06] <deneme> wicket-picketlink, works fine together :=) Thanks for help, maschmid, sbryzak. [15:25:18] * deneme away. [15:25:35] *** deneme has quit IRC [15:26:56] *** bleathem has joined #seam-dev [15:26:56] *** ChanServ sets mode: +v bleathem [15:28:14] *** oranheim has quit IRC [15:30:31] *** mathieuancelin has quit IRC [15:31:40] *** mathieuancelin has joined #seam-dev [15:54:37] *** rruss has joined #seam-dev [16:06:48] *** lazarotti has joined #seam-dev [16:07:24] *** hannelita has joined #seam-dev [16:18:53] *** emmanuel has joined #seam-dev [16:43:53] *** jganoff has joined #seam-dev [16:43:53] *** ChanServ sets mode: +v jganoff [16:48:18] *** mbg_ has joined #seam-dev [16:48:18] *** ChanServ sets mode: +v mbg_ [16:50:39] *** tremes_afk is now known as tremes [16:55:37] *** pmuir has joined #seam-dev [16:57:50] *** clerum has joined #seam-dev [16:57:56] *** ChanServ sets mode: +v clerum [16:58:18] *** pmuir has quit IRC [17:03:13] *** kpiwko has quit IRC [17:04:02] *** tsurdilo has quit IRC [17:04:49] *** tsurdilo has joined #seam-dev [17:06:35] *** emmanuel has quit IRC [17:12:18] *** mbg_ has quit IRC [17:26:39] *** kpiwko has joined #seam-dev [17:30:27] *** kpiwko has quit IRC [17:39:03] *** mkouba has quit IRC [17:46:45] *** tremes has quit IRC [17:47:02] *** maschmid has quit IRC [17:53:26] *** jharting has quit IRC [17:58:25] *** mathieuancelin has left #seam-dev [17:59:10] *** oskutka has quit IRC [17:59:59] *** kevinpollet has quit IRC [18:23:51] *** akazakov has joined #seam-dev [18:48:25] *** sannegrinovero has quit IRC [18:55:15] *** epbernard has joined #seam-dev [18:55:15] *** epbernard is now known as emmanuel [18:56:30] *** arbi has joined #seam-dev [19:19:41] *** daniel_hinojosa has joined #seam-dev [19:27:24] *** arbi has quit IRC [19:33:47] *** alesj has joined #seam-dev [19:37:34] *** lightguard_jp has joined #seam-dev [19:37:34] *** ChanServ sets mode: +o lightguard_jp [19:42:46] *** mgoldmann has joined #seam-dev [19:42:56] *** mgoldmann has quit IRC [19:42:56] *** mgoldmann has joined #seam-dev [19:52:27] *** emmanuel has quit IRC [19:53:12] *** rruss has quit IRC [19:56:17] *** lightguard_jp has quit IRC [19:56:43] *** lightguard_jp has joined #seam-dev [19:56:43] *** ChanServ sets mode: +o lightguard_jp [19:57:11] <lightguard_jp> bleathem: http://seamframework.org/Community/LoginRedirectionTransformsToInQueryParameters [19:57:18] <lightguard_jp> May be a question for lincoln as well. [19:57:22] <lightguard_jp> kenfinnigan: How's it going? [19:57:48] <kenfinnigan> lightguard_jp: not bad yourself? [19:57:52] <kenfinnigan> enjoying JavaOne? [19:58:00] <lightguard_jp> Doing well [19:58:03] <kenfinnigan> seems like a lot of cool stuff from all the tweets [19:58:04] <lightguard_jp> I'm not at J1 [19:58:08] <lightguard_jp> Yes it does [19:58:17] <kenfinnigan> no? oh, thought you were from some tweets I saw [19:58:20] <bleathem> https://issues.jboss.org/browse/RF/fixforversion/12317054 [19:59:14] <lightguard_jp> kenfinnigan: Nope, none of my talks were accepted [19:59:19] <kenfinnigan> bummer [19:59:21] <lightguard_jp> Yeah [19:59:33] <kenfinnigan> is that the only way to get to a conference, do a talk? [19:59:40] <kenfinnigan> can you not go as an attendee at all? [20:00:04] <kenfinnigan> or its just harder to get budget approval when you're not giving a talk? [20:02:24] <jbossbot> git [core] push master e61c95f.. Paul Bakker Added support to add an 'extensions' element which some plugins use to add packaging types to Maven for example. Required to use the Bundle Plugin [20:02:24] <jbossbot> git [core] push master 2a76c27.. Lincoln Baxter, III Merge pull request #58 from paulbakker/maven-plugin-api... [20:02:24] <jbossbot> git [core] push master URL: http://github.com/forge/core/compare/2d122e3...2a76c27 [20:05:07] *** epbernard has joined #seam-dev [20:05:07] *** epbernard is now known as emmanuel [20:08:34] *** jganoff has quit IRC [20:08:51] <lightguard_jp> kenfinnigan: basically [20:09:35] <lightguard_jp> It's harder to get the approval to go as an attendee. [20:10:02] <lightguard_jp> If you present, you get in for free, and travel / lodging is also sometimes taken care of by the conference [20:11:14] <kenfinnigan> ah ok [20:12:00] <kenfinnigan> lightguard_jp: can you remember from the previous DWG what Shane thought were good API parameters for Solder method to log error for a module? [20:12:17] <kenfinnigan> I was thinking, something to indicate the module, the error code, and then message [20:12:21] <kenfinnigan> do we need more? [20:12:37] <lightguard_jp> For logging exceptions, probably not [20:12:39] <kenfinnigan> ah, and possibly level of message (info, error, etc) [20:12:50] <kenfinnigan> unless that's done by method [20:12:53] <lightguard_jp> You could add the exception, but that's not as easy to localize [20:12:56] <kenfinnigan> haven't figured out the best way yet [20:13:11] <lightguard_jp> I'd say let the method handle the level [20:13:28] <lightguard_jp> We'll give it the module, code and message, should be good enough [20:13:37] <lightguard_jp> kenfinnigan: When's the trip to Raleigh? [20:13:46] <kenfinnigan> don't think I'm getting one [20:14:00] <lightguard_jp> Because you're already part of Red Hat? [20:14:00] <kenfinnigan> as I'm technically RH already, I don't believe one is being organized [20:14:12] <lightguard_jp> Makes sense. [20:14:14] <lightguard_jp> brb [20:14:15] *** lightguard_jp has quit IRC [20:14:35] *** lightguard_jp has joined #seam-dev [20:14:35] *** ChanServ sets mode: +o lightguard_jp [20:14:40] <kenfinnigan> which unfortunately means I don't get the swanky red fedora! [20:14:55] <lightguard_jp> weechat w/ tmux isn't behaving properly it seems, oh well. [20:15:09] <lightguard_jp> :( that sucks [20:15:12] <kenfinnigan> yep [20:15:14] <lightguard_jp> Maybe you can expense it [20:15:20] <kenfinnigan> possibly [20:16:19] *** maschmid has joined #seam-dev [20:17:10] <lightguard_jp> kenfinnigan: Who's the tdm? [20:17:15] *** jharting has joined #seam-dev [20:18:54] <kenfinnigan> Thomas Heute [20:20:09] <kenfinnigan> lightguard_jp: at least I think that's the tdm [20:20:20] <kenfinnigan> I know he'll be my manager, so presume that makes him the tdm [20:20:27] <lightguard_jp> Probably [20:20:30] <lightguard_jp> You start the 17th? [20:20:35] <kenfinnigan> yep [20:21:04] <kenfinnigan> really looking forward to it [20:22:20] <lightguard_jp> Cool. [20:23:04] *** lazarotti has quit IRC [20:23:25] *** lazarotti has joined #seam-dev [20:24:21] *** emmanuel has quit IRC [20:25:16] *** jharting has quit IRC [20:25:42] <lightguard_jp> kenfinnigan: I guess you're just tying things up for the next week? [20:26:02] <kenfinnigan> actually still on a client project until next Friday! [20:26:14] <kenfinnigan> getting their last bit of consulting income from me ;-) [20:26:23] <lightguard_jp> wow, all the way to the end [20:26:44] <kenfinnigan> yep [20:27:05] <kenfinnigan> in the 10 1/2 mths I will have been with amentra when I leave [20:27:18] <kenfinnigan> I think I will have been on the bench for all of 1 wk, maybe 2 at most [20:29:09] *** sannegrinovero has joined #seam-dev [20:33:28] <lightguard_jp> clerum: Thanks for that post on ir2 [20:33:54] <clerum> lightguard_jp: np. the longer stuff like that sits the better change it has of snowballing [20:34:09] <lightguard_jp> kenfinnigan: You were only with Amentra for less than a year? I thought it had been much longer [20:34:36] <lightguard_jp> Yeah, I was going to post something, then saw your post :) [20:34:37] <kenfinnigan> yeah, only migrated to Boston at end of October [20:34:49] <kenfinnigan> then started with Amentra beginning of December last year [20:35:07] <lightguard_jp> kenfinnigan: Did you get FC15 or Ubuntu installed? [20:35:13] <kenfinnigan> ubuntu [20:35:28] <kenfinnigan> seems to be working fine at moment [20:35:45] <kenfinnigan> but not coding on it yet, still setting everything up in free moments [20:36:58] <clerum> kenfinnigan: what are you going to be working on? [20:37:08] <kenfinnigan> portlet bridge and portal [20:37:15] <lightguard_jp> clerum: I have to say, I see the JSF rendering stuff less of priority, especially if we could give them an XSLT or something to migrate that xhtml page to a jasper report or something else. [20:37:16] <clerum> ah [20:37:41] <lightguard_jp> kenfinnigan: ready to get more familiar with JSF? [20:37:45] <clerum> lightguard_jp: if the JSF rendering falls into our lap cool. otherwise I can't see working on it [20:37:56] <kenfinnigan> it's been a couple of years since I've had to code with it regularly [20:38:07] <kenfinnigan> need to get up to speed with the latest in JSF 2 [20:38:25] <lightguard_jp> clerum: I think realistically if we want to keep the vocal members of our community we'll have to have something [20:38:33] <lightguard_jp> We've put it off for a long time [20:39:23] <clerum> until it's more natvily supported in JSf I think anything we do would be pretty hacky [20:39:24] <lightguard_jp> We've done an absolutely awesome job at screwing our community for the last few years [20:39:26] <clerum> and brittle [20:39:40] <lightguard_jp> clerum: Yep, just like it is with Seam 2 [20:39:49] <clerum> lightguard_jp: agreeed [20:40:13] <clerum> after 3.1 we really need to focus on real world complex examples [20:40:24] <clerum> that people can look at [20:40:41] <clerum> I think that seamCRM one I did could be expanded and moved to open shift [20:41:43] <clerum> and more resources need to go into making seam2 jsf compatable [20:42:29] <clerum> that storm isn't going away and with browser development moving much faster than it used to people are not going to take kindly to being left on RF3 [20:43:30] <clerum> need to be able to get Seam 2 working with RF4 and Primefaces 3 via JSF2. That would give people an option to hang on seam 2 for a bit until EE6 is a viable option for them [20:45:00] <clerum> what really hurt I think is that anyone really involved in the day to day development of Seam 2 was not in that capacity in Seam 3....other than maybe shane? [20:45:20] <lightguard_jp> Yeah, pretty much. [20:45:31] <lightguard_jp> I'm really not sure what's left to do to release 2.3 [20:45:47] <clerum> me either. it's been in waiting for a long time now [20:46:01] <lightguard_jp> Yeah, and the communication has been nearly non-existent, again. [20:46:14] *** jganoff has joined #seam-dev [20:46:14] *** ChanServ sets mode: +v jganoff [20:46:25] <lightguard_jp> I'm really confused how we do this all the time at Red Hat and don't change community communication. [20:46:57] <lightguard_jp> A bunch of the projects I've worked with have had little community interaction unless you as a community member go and seek it. [20:47:02] <lightguard_jp> We're not proactive about it. [20:47:14] *** mgoldmann has quit IRC [20:47:27] <lightguard_jp> We've tried to do more of that with Seam 3 and I think it's helped and shown what you can really get back for the efforts. [20:48:03] <clerum> keeping people updated should be one guys job 15 hrs a week [20:48:34] <clerum> maybe more...and devs should troll the forums 5 hrs a week [20:48:48] <clerum> just so they have a feel on what the community wants and is having issues with [20:49:03] <lightguard_jp> an hour a day is all it takes on the forums [20:49:22] <clerum> right [20:49:28] <lightguard_jp> Another hour writing blogs or twitter or something would be good too. [20:49:37] <lightguard_jp> The torquebox guys have it figured out I think. [20:49:51] <clerum> but it has to be someones responsibility [20:50:07] <lightguard_jp> A large part of our problem is that we're still so disorganized and everyone has 30 things they're trying to do. [20:50:18] <clerum> right [20:50:22] <clerum> but after 3.1 [20:50:29] <clerum> things need to reset [20:50:36] <lightguard_jp> Yeah [20:50:53] <clerum> then we are at a much more stable point [20:51:01] <clerum> I hope [20:51:08] <lightguard_jp> That's something I need to talk to Shane, Dan and Lincoln about [20:51:23] <lightguard_jp> We need to sit down as a team via Google Hangout or something and hammer this all out. [20:52:16] <lightguard_jp> I have a feeling it may not happen until January though, but we'll see [20:52:37] <kenfinnigan> is that due to all the conferences people are going to? [20:53:13] <lightguard_jp> Conferences and holidays [20:53:31] <lightguard_jp> End of the year is a terrible time to try and coordinate things [20:53:42] <clerum> the fact that we don't have something running like the old seam 2 booking is amazing [20:54:38] <clerum> means we don't have anything that we are having to maintain release to release and are probably missing lots of real world concerns [20:54:55] *** mgoldmann has joined #seam-dev [20:54:59] <kenfinnigan> there is a Seam 3 booking [20:55:08] <clerum> is it running live somewhere? [20:55:10] <kenfinnigan> but not sure it's being updated as new features in the modules are added [20:55:18] <clerum> exactly [20:55:19] <kenfinnigan> not that I'm aware of [20:55:28] <clerum> thats what I'm concerned about [21:00:16] <lightguard_jp> I'm trying to keep Confbuzz up to date, but it's not a fully fleshed out example. [21:02:23] <clerum> yep. I'd like to take an hour and get crm updated to as7 [21:03:18] <clerum> now that my primary project is on as7 it should be easy [21:03:28] <clerum> and the hibernate search bugs I had are fixed [21:05:14] <lightguard_jp> Sweet [21:07:30] *** gastaldi has joined #seam-dev [21:07:31] *** ChanServ sets mode: +v gastaldi [21:08:32] <gastaldi> Buonasera [21:08:36] <gastaldi> :) [21:08:43] <gastaldi> I love Rome [21:10:51] *** gastaldi has left #seam-dev [21:10:54] *** gastaldi has joined #seam-dev [21:10:54] *** ChanServ sets mode: +v gastaldi [21:11:16] *** gastaldi has quit IRC [21:12:15] *** mgoldmann has quit IRC [21:12:20] *** rruss has joined #seam-dev [21:33:03] *** maschmid has quit IRC [21:35:04] *** oskutka has joined #seam-dev [21:38:22] *** oskutka has quit IRC [21:47:11] <clerum> we have completely abandoned the idea of a seam2->seam3 bridge module right? [21:51:47] *** alesj has quit IRC [21:52:40] *** alesj has joined #seam-dev [21:55:01] <lightguard_jp> I believe so [21:55:05] <lightguard_jp> It really can't be done [21:55:12] <lightguard_jp> We have naming conflicts [21:55:44] *** alesj has quit IRC [21:59:27] <clerum> well really the only part you could is the DI [21:59:34] <clerum> and that is the easiest part to swap out [21:59:52] <clerum> the jsf2/rf part is far far worse [22:00:33] <amitev> i really miss pages.xml :) [22:01:35] <clerum> I did at first [22:01:45] *** dabloem_ has joined #seam-dev [22:01:53] <clerum> not I'm really liking just doing the navigation from my action methods [22:02:04] <clerum> I only have 1 or two rules in my faces-config [22:02:19] <clerum> and my pages.xml was 3k lines in seam 2 [22:02:38] <clerum> really what we need to provide is a Seam 2 -> EE6/CDI toolkit [22:02:48] <dabloem_> hi, just update seam to 3.1.0.Beta3 [22:02:59] <dabloem_> on glassfish 3.1.1 [22:03:00] <clerum> which has copy paste composite component replacement for s:div, s:decorate [22:03:02] <clerum> etc.. [22:03:27] <clerum> and a good explaination on how to convert your s:link s:button to h:link h:button [22:03:57] <dabloem_> noticed that you have to add seam-international and jboss-logging explicitly [22:04:04] <clerum> yes [22:04:17] <clerum> err jboss-logging? [22:04:35] <clerum> seam-international for sure [22:05:41] <clerum> yeah probably jboss-logging too [22:06:00] *** maschmid has joined #seam-dev [22:06:14] <dabloem_> yes, the app did deploy without errors, but as soon as the first application-scoped bean was constructed [22:06:14] <clerum> It's pulled in for me via hibernate search but if you aren't using that you will need add it to your pom [22:06:37] <dabloem_> I got an exception about missing a jboss-logging class [22:06:38] <clerum> in the earlier releases I think faces pulled in international [22:06:53] <clerum> org.jboss.logging [22:06:54] <clerum> jboss-logging [22:06:58] <clerum> 3.0.0.GA [22:07:23] <clerum> but now you need to define internationl yourself [22:07:40] <jbossbot> git [mail] push testsuite 7798a19.. LightGuard Using same arquillian.xml from other modules [22:07:40] <jbossbot> git [mail] push testsuite URL: http://github.com/seam/mail/compare/4cd1ca3...7798a19 [22:07:44] <dabloem_> clerum, yes infact i used 3.0.0.Beta5 [22:08:42] <clerum> lightguard_jp: does mail-impl need to rename to just mail [22:09:09] <clerum> looks like everyone else dropped the impl [22:09:28] <lightguard_jp> clerum: I think I got that last night [22:09:56] <clerum> cool [22:12:00] <clerum> dabloem_: did you get that figured out? [22:12:08] <clerum> if not jump over to #seam [22:13:13] <kenfinnigan> dabloem_: you shouldn't need jboss-logging artifact [22:13:13] <dabloem_> it works now, but I thought let you guys know that also jboss-logging is required if you use solder on glassfish [22:13:41] <dabloem_> ah, i see now [22:13:41] <kenfinnigan> we import jboss-logging into solder-logging [22:14:01] <dabloem_> I think it's me fault, I use infinispan [22:14:14] <dabloem_> and jboss-logging wasn't included [22:14:34] <kenfinnigan> ok, infinispan may rely on jboss-logging, not sure [22:15:22] <clerum> kenfinnigan: that makes sense as mine is being pulled in via hibernate search [22:15:37] <dabloem_> yes it does, strang that it wasn't complaining before [22:16:07] <clerum> one of the other modules may have been pulling it in for you before [22:16:14] <clerum> and that stopped after the move to Beta3 [22:16:29] <clerum> you'd have to inspect your old pom to be sure [22:19:05] <dabloem_> ok [22:40:48] *** tsurdilo has quit IRC [22:44:00] *** rmartinelli has quit IRC [22:46:53] *** alazarot has joined #seam-dev [22:50:41] *** lazarotti has quit IRC [22:53:55] *** tsurdilo has joined #seam-dev [23:00:23] <kenfinnigan> hey all [23:00:27] <kenfinnigan> meeting starting soon? [23:00:50] <sbryzak> morning ken [23:00:53] <sbryzak> i believe so [23:01:44] <kenfinnigan> cool [23:01:48] <kenfinnigan> morning shane [23:02:50] <kenfinnigan> sbryzak: planning to upgrade jboss-logging and jboss-logging-tools in solder over the next couple of days [23:03:03] <kenfinnigan> or would you prefer I wait until after 3.1.Final? [23:03:22] <lightguard_jp> Hi all [23:03:24] <lightguard_jp> #startmeeting [23:03:25] <jbott> Meeting started Wed Oct 5 21:00:32 2011 UTC. The chair is lightguard_jp. Information about MeetBot at http://wiki.debian.org/MeetBot. [23:03:25] <jbott> Useful Commands: #action #agreed #help #info #idea #link #topic. [23:03:27] <lightguard_jp> chair sbryzak [23:03:34] <sbryzak> kenfinnigan: that should be fine, as long as it doesn't break anything ;) [23:03:41] <lightguard_jp> I hope it's been a good week for everyone [23:03:41] <kenfinnigan> don't think it will [23:03:51] <kenfinnigan> if it does I won't submit a pull request yet ;-) [23:04:08] <sbryzak> clerum: thanks for responding on the release announcement about the mail templating [23:04:14] <clerum> np [23:04:22] <clerum> figured I would get out in front of it [23:05:00] <clerum> if we can't do that one right I don't think we should at all [23:05:34] <lightguard_jp> #chair sbryzak [23:05:34] <jbott> Current chairs: lightguard_jp sbryzak [23:06:11] <lightguard_jp> We don't have many topics today, so the meeting may be a little short [23:06:14] <lightguard_jp> First up [23:06:22] <lightguard_jp> #topic Seam 3.1.0.Beta3 release [23:06:22] *** jbott changes topic to "Seam 3.1.0.Beta3 release" [23:06:38] <lightguard_jp> I think most people are familiar with the blog Shane put up earlier today / yesterday [23:06:48] <lightguard_jp> #info We've released Seam 3.1.0.Beta3! [23:07:17] <lightguard_jp> http://in.relation.to/Bloggers/JBossSeam310Beta3Released if you haven't read it yet [23:07:19] <sbryzak> yes, thank you everyone for the hard work [23:07:25] <lightguard_jp> Thank you for everyone that's helped with this release. [23:07:30] <sbryzak> it's great to see the number of modules growing [23:07:52] <lightguard_jp> I think we also released this one in record time as well. We're getting faster :) [23:08:11] <sbryzak> i still have nightmares about maven while i sleep [23:08:27] <lightguard_jp> Not surprised [23:08:51] <lightguard_jp> We're continuing to improve, that's the best part [23:09:10] <lightguard_jp> sbryzak: Do you have anything you'd like to add about this release, or was it mostly in the blog? [23:09:11] <kenfinnigan> i'm sure that having 3 less modules to release helps a little [23:09:30] <sbryzak> just that we're going to be releasing CR1 in two weeks from now [23:09:40] <sbryzak> we can't slip this date because of the WFK schedule [23:09:54] <sbryzak> so we don't have much time to address any major issues [23:10:08] <sbryzak> i think this is a good lead in for talking about the next seam hack night ;) [23:10:09] *** jganoff has quit IRC [23:11:08] <sbryzak> so, i sent a list of outstanding issues to seam-dev [23:11:22] <lightguard_jp> #topic next hack night [23:11:22] *** jbott changes topic to "next hack night" [23:11:24] <sbryzak> just a moment while i count [23:11:28] *** jamezp has joined #seam-dev [23:11:28] *** ChanServ sets mode: +v jamezp [23:11:33] <lightguard_jp> #info check the mailing list for a list of issues for the hack night [23:11:46] <sbryzak> it looks like we have 40 issues listed there [23:11:53] <lightguard_jp> #info the focus for the hack night is bug squashing in preparation for CR1 [23:12:04] <sbryzak> jason and i will certainly be working on closing as many of them as possible [23:12:24] <kenfinnigan> so november's hack night will become the "come and build your app and we'll help" night? [23:12:31] <sbryzak> however i'm sure we won't get them all by next thursday [23:12:50] <sbryzak> kenfinnigan: yes, we're going to postpone it from this month [23:12:56] <kenfinnigan> no prob [23:13:13] <sbryzak> which makes sense, because we want everyone to build their app using the 3.1 final release [23:13:19] <kenfinnigan> very true [23:13:46] <sbryzak> so for this hack night, we'd like to concentrate on getting as many issues closed as we can [23:13:47] <hannelita> I'll blog and tweet about the hack night as usual [23:13:53] *** epbernard has joined #seam-dev [23:13:53] *** epbernard is now known as emmanuel [23:13:58] <sbryzak> make 3.1 as solid as possible [23:14:23] <sbryzak> if there are any issues in your module that you think should be fixed for the release [23:14:31] <sbryzak> but don't have 3.1.0.CR1 as the fix version, can you please update them [23:14:34] *** sannegrinovero has quit IRC [23:14:42] <sbryzak> i actually have a search filter set up in jira, one moment while i find it [23:14:53] *** sannegrinovero has joined #seam-dev [23:15:35] *** Diablo-D3 has joined #seam-dev [23:16:34] <sbryzak> ok, this should work: https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=12314291 [23:16:45] <sbryzak> according to that filter, we actually have 51 issues [23:16:56] <sbryzak> i'll post this link to seam-dev [23:17:05] <sbryzak> as soon as someone confirms it works for them ;) [23:17:07] *** cbrock has joined #seam-dev [23:17:34] <maschmid> sbryzak, works for me :) [23:17:39] <kenfinnigan> sbryzak: confirmed [23:17:52] <sbryzak> also, if that list contains issues for your module that you know for sure need more time to fix, please bump them to a future release [23:18:03] <sbryzak> maschmid kenfinnigan: thanks [23:18:25] <sbryzak> any questions about the next hack night? [23:19:03] <sbryzak> ok, let's move on [23:19:33] <lightguard_jp> #topic Release roadmap for 3.1.0 [23:19:33] *** jbott changes topic to "Release roadmap for 3.1.0" [23:19:46] <lightguard_jp> #info 3.1.0.CR1 scheduled for two weeks [23:19:54] <lightguard_jp> #info 3.1.0.Final at the end of the month [23:20:03] <lightguard_jp> Questions or concerns? [23:20:28] <kenfinnigan> not from me [23:21:15] <sbryzak> i would like to talk about the next release after 3.1.0.Final, but it can wait until we've finished with the other topics [23:22:54] <lightguard_jp> I only have one more, and I think it would fit in nicely with the next release, or at least be started with the next release. [23:23:14] <lightguard_jp> Shall we handle them together? [23:23:51] <sbryzak> sure, want me to go first? [23:23:54] <lightguard_jp> #topic Release after 3.1.0.Final and TomEE / OWB compat [23:23:54] *** jbott changes topic to "Release after 3.1.0.Final and TomEE / OWB compat" [23:23:57] <lightguard_jp> Sure [23:24:12] <sbryzak> ok, so moving forward from the 3.1 release [23:24:23] <sbryzak> i'd like to work on a point release, 3.1.1 [23:24:38] <sbryzak> in which we concentrate on polishing the modules a bit more, improving documentation and working on some new examples [23:24:55] <sbryzak> we have some nice examples underway which just need a little bit of love to get completed [23:25:02] <kenfinnigan> is that with the examples in the "app store" or where they are now? [23:25:09] <sbryzak> where they are now [23:25:12] <kenfinnigan> ok [23:25:17] <sbryzak> the app store idea won't be happening for quite some time [23:25:31] <sbryzak> also, i'd like to discontinue doing individual module releases [23:25:38] <lightguard_jp> #info proposed next release 3.1.1 to focus on improving documentation and examples [23:25:57] <sbryzak> based on feedback from the community, these are not well liked [23:26:07] <kenfinnigan> discontinue? how would that work without a bundle release? [23:26:20] <sbryzak> rather, we'll continue to only do bundled releases [23:26:43] <sbryzak> community likes bundled releases, doesn't like individual module releases [23:26:54] <sbryzak> any comments on that so far? :) [23:26:58] <kenfinnigan> do we lose flexibility for some people with not having module releases? [23:27:03] <clerum> but we should still be able to do a individual release outside of the bundle [23:27:12] <lightguard_jp> I'm with cody here [23:27:14] <clerum> between bundles [23:27:16] <sbryzak> i don't think we lose flexibility [23:27:31] <sbryzak> there's a few things we have to address to make this work [23:27:37] <lightguard_jp> I think being able to do point releases between bundles (unless we step up the time frame for bundled releases) is a good thing [23:27:42] <lightguard_jp> Like what we did with faces [23:27:46] <lightguard_jp> 3.0.1 and 3.0.2 [23:27:46] <clerum> +1 [23:27:51] <sbryzak> ok let's talk about that quickly [23:28:03] <sbryzak> part of what is required to make this work is more agile bundled releases [23:28:16] <sbryzak> so instead of every 6 months, we simply release when we need to [23:28:34] <sbryzak> so if a module has a critical update that needs to be released, we release a bundle [23:28:53] <clerum> ugh [23:29:05] <clerum> so if one module has an issue it ripples across all forcing a relealse? [23:29:21] <sbryzak> yes, but i don't see that as a bad thing [23:29:26] <kenfinnigan> how would we know when one modules api changes and breaks ones that depend on it? [23:29:31] <maschmid> clerum, not all, only the bom and distribution, right? [23:29:42] <kenfinnigan> would we need some kind of CI for all modules running from snapshots [23:29:56] <clerum> maschmid: good point [23:29:59] <kenfinnigan> or would we merge all the code into modules of a single git repo? [23:30:11] <sbryzak> kenfinnigan: that's the next thing i wanted to discuss [23:30:13] <clerum> if persitence had an issue which need a release after 3.1 [23:30:22] <lightguard_jp> If we're only talking about updating the bom for a point release along with any modules that need it, I'm fine with that [23:30:29] <sbryzak> if we only release bundles, then there's no point in having separate documentation, separate examples for everything [23:30:34] <lightguard_jp> We'll really need to set up some integration tests though [23:30:40] *** jamezp has quit IRC [23:30:48] <clerum> would faces get a new relealse or just a new bundle release still poiting to the original 3.1 release [23:31:01] <sbryzak> and honestly, having separate modules the way we do is a management nightmare [23:31:04] <clerum> so bundle where persistence is at 3.1.1 and faces is at 3.1 [23:31:26] <lightguard_jp> Merging all the code into one repo certainly has some pros [23:31:30] <sbryzak> to be frank for a moment, i really love the work you guys all do, but for a lot of the infrastructure you all seem to do your own thing ;) [23:31:47] <kenfinnigan> how would that work with the likes of faces and persistence that are planning to be moved into "homes" under other JBoss projects [23:31:51] <sbryzak> it's a major effort to standardise the module structure across all modules [23:31:56] <kenfinnigan> or would that not happen [23:32:01] <lightguard_jp> kenfinnigan: We'll worry abuot that later [23:32:12] <sbryzak> that's not going to happen now [23:32:20] <clerum> sbryzak: once standardized though that should be pretty stable [23:32:26] <sbryzak> no-one liked the idea [23:32:37] <sbryzak> clerum: that's the problem, it's not stable [23:32:43] <sbryzak> things change all the time [23:32:44] <clerum> get everyone on the same page and then no infrastructure changes unless it happens accross modules [23:33:25] <sbryzak> so this is just an idea at the moment, but i can see many advantages in combining all of the modules into one repo [23:34:00] <sbryzak> i'd like to discuss this idea thoroughly with everyone, because it is *just* an idea [23:34:17] <sbryzak> so let me hear some cons.. who wants to go first [23:34:28] <lightguard_jp> I think we should chew on this one a bit, put it out on the mailing list, and if we have agreement from the module leads put it up on the forums for the later community to discuss [23:34:39] <kenfinnigan> lightguard_jp: +1 [23:34:50] <sbryzak> certainly we'll chew on it, but surely someone has some initial impressions on the idea [23:34:57] *** koentsje has quit IRC [23:34:58] <clerum> being able to rapidly release a fixed module is one issue that jumps to mind [23:35:02] *** emmanuel has quit IRC [23:35:15] <sbryzak> ok, i think that can be addressed by improving the bundled release process [23:35:15] <maschmid> sbryzak, could be a barrier for potential new modules... just a thought [23:35:18] <lightguard_jp> Those that are only using certain features of Seam3 will be toast [23:35:35] <sbryzak> maschmid: how would it be a barrier? [23:35:45] <sbryzak> lightguard_jp: why is that? [23:35:47] <lightguard_jp> Say Seam University which is using JCR and Remoting now, having one large bundle is a lot of extra stuff you wouldn't want [23:35:53] <maschmid> sbryzak, well, it's easier now when they can just start their own repo :) [23:36:00] <sbryzak> no no no, we would still build it as separate artifacts [23:36:02] *** sannegrinovero has quit IRC [23:36:06] <kenfinnigan> does add some bloat [23:36:11] <sbryzak> each module would still be a submodule [23:36:17] <sbryzak> have its own api and impl jars [23:36:22] <sbryzak> we would not lose that [23:36:22] <lightguard_jp> sbryzak: I don't think we're completely understanding your proposal [23:36:40] <sbryzak> there would be no additional bloat [23:36:46] <lightguard_jp> So one seam git repo which has all of the modules as git submodules? [23:36:48] <sbryzak> you can still pick and choose which modules you want to use in your project [23:36:56] <sbryzak> i'm talking more in terms of module infrastructure [23:37:21] <sbryzak> lightguard_jp: is there such a thing as git submodules? [23:37:26] <lightguard_jp> yes [23:37:32] <clerum> submodule == folder? [23:37:42] <sbryzak> i was thinking more along the lines of maven submodules [23:38:21] <sbryzak> we really need to improve the release process so that we can produce a complete bundled release at the drop of a hat [23:38:21] <kenfinnigan> ok, i'm confused about the proposal too [23:38:34] <sbryzak> kenfinnigan: which bits? [23:38:42] <lightguard_jp> I'm still a little lost. Shane, could you explain the whole idea so we understand it a bit better? [23:39:12] <lightguard_jp> Or maybe in email form [23:39:16] <lightguard_jp> either way [23:39:18] <sbryzak> the idea is that we continue to main separate modules, but within the same git repo [23:39:19] <kenfinnigan> sbryzak: how it's a bundle release, but we still build module artifacts [23:39:22] <sbryzak> *maintain [23:39:38] <sbryzak> ok those are two separate things [23:39:55] <sbryzak> in the same way that you build a module now, say seam security [23:40:05] <sbryzak> you run mvn clean install from the root directory [23:40:15] <sbryzak> it goes and builds the api, impl and external submodules [23:40:18] <lightguard_jp> sbryzak: Okay, I think I'm understanding a bit better. git submodules seems like a good solution for this [23:40:19] <sbryzak> so what we would do [23:40:21] <kenfinnigan> ok, so we still build module artifacts, it's they're coming from the same repo so they're proper child modules because they're sub folders? [23:40:25] <sbryzak> is just move that one level lower [23:40:36] <sbryzak> yes [23:40:42] <lightguard_jp> http://progit.org/book/ch6-6.html -- Git submodules explained [23:41:03] <sbryzak> but it gives us the ability to build the entire seam stack in one go [23:41:40] <sbryzak> it makes logical sense to me, leading on from the fact that the community wants bundled releases as opposed to individual module releases [23:41:50] <sbryzak> and it makes it way easier to produce a bundled release [23:42:08] <sbryzak> from a project structure point of view [23:42:42] <sbryzak> lightguard_jp: thanks for the link.. do submodules still allow us to assign different committer rights? [23:42:44] <lightguard_jp> I see a potential for much lost time with merge conflicts / bad updates [23:43:03] <kenfinnigan> lightguard_jp: my thoughts [23:43:19] <sbryzak> lightguard_jp: where would the conflicts be? everyone would still be working within their own submodule [23:43:25] <kenfinnigan> can we restrict committ writes based on sub modules? that would be a big issue [23:43:35] <maschmid> there used to be some issues with various tools regarding git submodules... we need to check if everything we need works with it..(especially jenkins) [23:43:36] <lightguard_jp> sbryzak: All of the work for that module would still happen in that module's own repo, but you'd have an umbrella repo with the modules as essentially pointers to the other repos. [23:43:40] <sbryzak> kenfinnigan: that's a good question [23:43:57] <lightguard_jp> maschmid: Yeah, that would be something to look into [23:44:03] <sbryzak> lightguard_jp: good, i think that would work then [23:44:29] <kenfinnigan> that could work [23:44:34] <sbryzak> so anyway, in the interest of not derailing the meeting, let's continue with jason's last topic and take this to the mailing list [23:44:36] <lightguard_jp> maschmid: Would you mind looking into submodule tooling support? [23:44:50] <kenfinnigan> I hate to say it, but do we need to "prototype" the approach to make sure it can work with all the tools we use? [23:45:01] <sbryzak> kenfinnigan: i think that would be prudent [23:45:13] <sbryzak> we wouldn't look at doing this until after the 3.1 release [23:45:19] <sbryzak> too risky right now [23:45:20] <kenfinnigan> certainly [23:45:30] <sbryzak> but let's discuss it further first [23:45:43] <lightguard_jp> Okay, the last topic I had was TomEE compatibility. We're going to have people looking at TomEE I'm sure. As soon as they get their arq adapter we should add it to the test suites [23:45:55] <kenfinnigan> definitely [23:46:51] <lightguard_jp> Something I thought we should address in 3.1.1 or a 3.1.2 [23:47:07] *** jose_freitas_ has joined #seam-dev [23:47:22] <lightguard_jp> We should probably be doing a 3.1.2 as the list of things we want to do in 3.1.1 is getting larger, and the time frame isn't [23:47:28] <kenfinnigan> minor segway to prev topic. Thought of one big adv of single repo approach is being able to issue a pull request that includes changes that ripple through multiple modules in a single shot [23:47:53] <kenfinnigan> what is the planned date for 3.1.1? [23:48:25] <sbryzak> kenfinnigan: good point on that [23:48:33] <sbryzak> kenfinnigan: probably 6-8 weeks after 3.1 [23:48:36] <kenfinnigan> ok [23:49:43] *** jose_freitas has quit IRC [23:49:48] <kenfinnigan> any other topics? [23:49:55] <lightguard_jp> Nope [23:49:56] *** tsurdilo1 has joined #seam-dev [23:50:27] <sbryzak> git submodules look nice, but i have a feeling they won't work with the maven release plugin [23:50:30] *** jose_freitas has joined #seam-dev [23:51:05] <kenfinnigan> ok all, chat later [23:51:09] <lightguard_jp> sbryzak: We'd need to ask someone like Matthew McCullough [23:51:18] <lightguard_jp> kenfinnigan: later [23:51:18] *** kenfinnigan has left #seam-dev [23:51:25] <sbryzak> lightguard_jp: could you please follow up on that and do some research? [23:51:30] <lightguard_jp> Thanks everyone for coming! [23:51:35] *** jose_freitas_ has quit IRC [23:51:47] <lightguard_jp> #action lightguard_jp look into git submodules and maven release [23:52:05] <lightguard_jp> #action maschmid look into submodules and tooling [23:52:08] <lightguard_jp> maschmid: That okay? [23:52:09] <sbryzak> maschmid: could you please look into jenkins support? [23:52:13] <maschmid> lightguard_jp, sure [23:52:17] *** jose_freitas_ has joined #seam-dev [23:52:17] <lightguard_jp> maschmid: thanks [23:52:26] <lightguard_jp> I think that's it for today [23:52:34] <sbryzak> cool [23:52:38] *** tsurdilo has quit IRC [23:52:51] <lightguard_jp> Probably some more details to finalize, but good stuff [23:52:55] <lightguard_jp> #endmeeting [23:53:09] <sbryzak> yeah [23:53:11] *** jbott changes topic to "Seam 3.0.0.Final has been released! Development discussions for Seam (seamframework.org). Join #seam for user discussions. See http://seamframework.org/Seam3/Chat for logs and more info. TeamSpeak 3 server is available for Seam devs at 216.6.228.98:10024, password: seam-dev" [23:53:11] <jbott> Meeting ended Wed Oct 5 21:50:01 2011 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) [23:53:11] <jbott> Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/seam-dev/2011/seam-dev.2011-10-05-21.00.html [23:53:11] <jbott> Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/seam-dev/2011/seam-dev.2011-10-05-21.00.txt [23:53:11] <jbott> Log: http://transcripts.jboss.org/meeting/irc.freenode.org/seam-dev/2011/seam-dev.2011-10-05-21.00.log.html [23:53:35] <sbryzak> i really think we need to be able to build the entire stack in one go [23:53:39] <maschmid> sbryzak, will there be any .Final release of Seam Conversation? [23:53:52] <sbryzak> maschmid: will have to ask alesj [23:54:00] <sbryzak> i think it's stable enough [23:55:05] *** jose_freitas has quit IRC [23:55:50] <lightguard_jp> sbryzak: I'm leaving on a road trip (not vacation, should be working tomorrow and throughout the stay as normal) for the next week [23:56:12] <lightguard_jp> Send me an email if you need anything and I'll get on it when we stop [23:56:17] <clerum> cool [23:56:23] <clerum> any progress on the mail tests? [23:56:28] <lightguard_jp> clerum: Not yet [23:56:35] <lightguard_jp> Still broken [23:57:10] <sbryzak> lightguard_jp: no problems [23:57:23] <sbryzak> we should ask QA to help with the testsuite [23:57:36] <clerum> lightguard_jp: k [23:57:37] <sbryzak> jozef is extremely efficient at fixing those ;)