August 24, 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

[00:00:18] <lightguard_jp> I thought of simple admin and guest or something like that.
[00:00:23] <lightguard_jp> Maybe organizer as well
[00:00:37] <ssachtleben> damn
[00:00:43] <ssachtleben> ping lincolnthree :D
[00:01:00] <lightguard_jp> Yet again though, unless you can limit roles to a particular instance you're hosed
[00:01:04] <lightguard_jp> sbryzak: ping
[00:01:46] *** aslak has quit IRC
[00:03:55] *** ssachtleben_away has quit IRC
[00:06:18] <sbryzak> lightguard_jp: pong
[00:06:49] <lightguard_jp> sbryzak: Looking back at the conversation between myself and hannelita, is that possible with roles?
[00:08:22] <sbryzak> just reading now
[00:09:18] <sbryzak> hmm
[00:09:32] <sbryzak> one way to do it would be to create a group for each conference
[00:09:44] <sbryzak> and then assign the roles within that group
[00:09:56] <sbryzak> that seems a little hackish to me though
[00:10:18] <sbryzak> the other way would be to use ACLs
[00:10:26] <sbryzak> but.. they're still broken in seam 3
[00:10:43] <sbryzak> so they'd need to be resurrected first
[00:11:48] <hannelita> ok, lets do it simple
[00:11:49] <hannelita> :)
[00:12:55] <lightguard_jp> Guest and admin?
[00:13:07] <hannelita> yep
[00:13:12] <lightguard_jp> sbryzak: That a limitation of picketlink?
[00:13:37] <sbryzak> well, that's pretty much how security works as a standard
[00:15:03] <lightguard_jp> Adding that many groups though just seems like a flaw in the model.
[00:15:36] <lightguard_jp> I guess it could be done that way but you'd have to involve the conference for authorization of actions.
[00:16:04] <lightguard_jp> It would be a permission check with the identity, role and object
[00:16:11] <sbryzak> well if you look at it this way, there's going to be way more users than groups
[00:16:18] <sbryzak> and groups are identity objects just like users are
[00:16:20] <lightguard_jp> True.
[00:16:41] <sbryzak> so perhaps this is a valid use case for it
[00:17:07] <lightguard_jp> Good point. It would also show how to do this.
[00:17:13] <lightguard_jp> hannelita: What do you think about that?
[00:17:20] *** lincolnthree has joined #seam-dev
[00:17:41] <lightguard_jp> lincolnthree: Back online! Earthquake do that much damage to the phone infra?
[00:17:54] <lincolnthree> nah I went home :)
[00:18:20] <lightguard_jp> lincolnthree: Did you see the tweet that instruments picked up movement regarding the quake for 40 minutes
[00:19:10] <lincolnthree> wow
[00:19:12] <lincolnthree> that's amazing
[00:19:29] <hannelita> ok, so just guest and admin?
[00:19:45] <lightguard_jp> No, your idea, but creating a new group for each conference.
[00:19:52] <ssachtleben> lincolnthree question
[00:19:58] <hannelita> oh, okay :)
[00:20:02] <lincolnthree> ssachtleben: answer
[00:20:03] <lightguard_jp> So when a user signs up to be a speaker or attendee we'll add them to the group with the role.
[00:20:10] <lightguard_jp> We could also setup organizers that way too.
[00:20:10] <lincolnthree> i cant promise it will be useful ;)
[00:20:15] <ssachtleben> every tried mod_cluster, jboss as 7 and prettyfaces?
[00:20:19] <hannelita> I'll try to do that :D I'll ping you if I need help
[00:20:28] <lincolnthree> ssachtleben: apache mod_cluster?
[00:20:39] <lightguard_jp> hannelita: Okay, excellent.
[00:20:46] *** emmanuel has quit IRC
[00:21:04] <lincolnthree> jboss mod_cluster
[00:21:08] <lightguard_jp> hannelita: I also posted up on the mailing list the latest draft of the getting started guide if you'd like to review
[00:21:08] <ssachtleben> http://www.jboss.org/mod_cluster/downloads/1-1-3
[00:21:31] <hannelita> I saw this, just didnt have time to comment! :( sorry
[00:21:42] <lincolnthree> ssachtleben: i haven't. i assume youre having a problem?
[00:21:50] <lightguard_jp> Sure, no problem.
[00:21:53] <hannelita> I'm already writing a post indexing it.... Github is too bad for indexig things
[00:22:11] <hannelita> so ppl will be able to google and find your tutorial :)
[00:22:22] <lightguard_jp> Ah
[00:22:33] <lightguard_jp> hannelita: Please wait until we officially publish it
[00:22:42] <lightguard_jp> That is not the place it will officially live.
[00:22:45] <lightguard_jp> It's a staging area.
[00:23:26] <hannelita> Ok :)
[00:24:26] <lightguard_jp> thanks
[00:26:01] <hannelita> lightguard_jp: Sign up screen commited
[00:26:08] *** ssachtleben has quit IRC
[00:26:44] <hannelita> I will work at the roles today after work :)
[00:26:55] <lightguard_jp> hannelita: Excellent
[00:27:15] <lightguard_jp> If you want to push each feature that's fine, actually, that's probably better.
[00:27:29] <lightguard_jp> hannelita: Are you doing the sign up through the picketlink api or directly into the db?
[00:28:11] <lightguard_jp> sbryzak: Nice response to that forum post
[00:28:27] <sbryzak> well, it's the truth
[00:28:43] <lincolnthree> lightguard_jp: which post? sbryzak
[00:28:54] <sbryzak> seam's exploded into something far bigger than a few core devs can effectively maintain
[00:28:55] <lightguard_jp> http://seamframework.org/Community/Seam2Or3#comment165243
[00:29:07] <sbryzak> so responsibility has to fall somewhat on the community's shoulders
[00:29:28] <lightguard_jp> We're trying to herd it more than run it ourselves
[00:29:48] <sbryzak> that's right, and if someone complains about bugs they need to be asked why they're not helping to fix them
[00:29:54] <lincolnthree> yeah good reply
[00:30:22] <hannelita> lightguard_jp: db; do you think it's better if I use picketlink? I mean, maybe it's too much information for newbies.
[00:30:23] *** tsurdilo2 has quit IRC
[00:30:44] <hannelita> lightguard_jp: Or I can use picketlink for confbuzz and use db at my call4all app example
[00:30:47] <lightguard_jp> I think the correct / preferred method is to go through picketlink
[00:30:48] *** tsurdilo1 has joined #seam-dev
[00:30:52] <lightguard_jp> sbryzak: ^^ correct?
[00:30:57] <hannelita> lightguard_jp: so we would have both impls.
[00:31:53] *** ssachtleben has joined #seam-dev
[00:32:04] <ssachtleben> sorry back
[00:32:16] <lincolnthree> ssachtleben: np. what's your issue?
[00:32:19] <sbryzak> picketlink is preferred for security
[00:32:46] <lightguard_jp> Are there issues we can highlight if using the em directly?
[00:33:03] <lightguard_jp> Like caching with picketlink or anything
[00:33:24] <ssachtleben> lincolnthree: if I return a prettyface annotation id in a viewAction method I get double dashes
[00:33:38] <lincolnthree> annotation id?
[00:33:40] <ssachtleben> like domain.com//forums.html
[00:33:41] <lincolnthree> mappingId?
[00:33:46] <ssachtleben> yeah mappingid
[00:33:49] <lincolnthree> oh, yuck
[00:33:54] <lincolnthree> that's interesting
[00:34:13] <ssachtleben> its not happening on normal navigation and get requests
[00:34:28] <ssachtleben> only on method string return like pretty:blabla
[00:34:36] <lincolnthree> and this doesn't happen without mod_cluster?
[00:34:43] <ssachtleben> and it seems only happen with mod_cluster
[00:35:04] <lincolnthree> that's strange
[00:35:12] <lincolnthree> since I don't have a cluster
[00:35:17] <lincolnthree> could I ask you to try to find the root cause?
[00:35:18] <hannelita> lightguard_jp: Ok, I'll do that with picketlink :)
[00:35:33] <lincolnthree> I'd start in the PrettyNavigationHandler
[00:35:44] <lincolnthree> since that is what handles those return values
[00:40:44] <lightguard_jp> sbryzak: Are there problems with using the EM if all you have is a JPA based IDM? Caching in picketlink, constraints, etc ?
[00:41:02] <ssachtleben> I will allow the port of the jboss to external for testing without modcluster
[00:41:19] <ssachtleben> takes 15 mins
[00:41:21] <ssachtleben> but it doesnt occure on local build with context path
[00:41:41] <ssachtleben> and it doesnt occure with mod_jk and jboss 6
[00:41:42] <sbryzak> lightguard_jp: no.. what kind of problems?
[00:42:59] <lightguard_jp> sbryzak: Just any gotchas users may experience when using the entity manager directly.
[00:43:22] <lightguard_jp> sbryzak: Looking for a reason why it's the preferred method, I think it'll come up.
[00:43:24] <sbryzak> i don't quite understand.. use it directly for what?
[00:43:35] <lightguard_jp> For inserting security related data
[00:43:43] <lightguard_jp> New groups, indentities, roles, etc.
[00:43:51] *** cbrock has quit IRC
[00:43:53] <sbryzak> i wouldn't recommend it... you should be using the picketlink apis
[00:44:25] <lightguard_jp> Okay, is are there concrete reasons for not recommending it?
[00:44:47] <sbryzak> yes, you might make mistakes
[00:45:02] <sbryzak> if you use picketlink directly you eliminate that chance
[00:45:03] <lightguard_jp> Okay, so there are some checks or constraints picketlink does
[00:45:18] <sbryzak> it's built to do the right thing
[00:45:41] <sbryzak> if you're manually inserting and you get the identity type, or relationship type or something wrong, it won't work
[00:46:00] <sbryzak> or get the from and to properties in a relationship back to front
[00:46:06] <lightguard_jp> Okay, that'll work to put in as a warning in the getting started guide.
[00:46:11] <sbryzak> easier to just use the picketlink api
[01:03:36] *** jbossbot has quit IRC
[01:06:53] *** lincolnthree has left #seam-dev
[01:18:49] <sbryzak> lightguard_jp: are you ok to do the catch release for beta2?
[01:19:13] <lightguard_jp> sbryzak: Yeah, I can do it.
[01:19:24] <lightguard_jp> What needs to be changed for the solder stuff?
[01:19:55] <sbryzak> the new logging package is org.jboss.seam.logging
[01:19:57] <sbryzak> that's about it
[01:20:07] <sbryzak> you probably need to fix your arquillian dependencies also
[01:20:13] <sbryzak> and ensure the tests are passing
[01:20:30] <lightguard_jp> I stayed away from logging for the initial release, haven't added any yet ;)
[01:20:46] <lightguard_jp> Yeah, I'll have to check the tests
[01:31:46] *** tsurdilo2 has joined #seam-dev
[01:35:01] *** tsurdilo1 has quit IRC
[01:49:21] *** jbossbot has joined #seam-dev
[01:51:30] *** lightguard_jp has quit IRC
[01:52:22] *** ssachtleben has quit IRC
[01:54:46] <jbossbot> git [transaction] push develop 0cb749d.. Shane Bryzak update parent, seam-bom version, fix compiler errors, fix distribution
[01:54:46] <jbossbot> git [transaction] push develop URL: http://github.com/seam/transaction/compare/0eb905f...0cb749d
[01:57:48] <jbossbot> git [transaction] push 3.1.0.Beta2 8c5d3de.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[01:57:48] <jbossbot> git [transaction] push 3.1.0.Beta2 URL: http://github.com/seam/transaction/compare/0000000...8c5d3de
[01:57:55] <jbossbot> git [transaction] push 3.1.0.Beta2 URL: http://github.com/seam/transaction/compare/0000000...26ec408
[01:58:00] <jbossbot> git [transaction] push 3.1.0.Beta2 86c4d74.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[01:58:00] <jbossbot> git [transaction] push 3.1.0.Beta2 URL: http://github.com/seam/transaction/compare/8c5d3de...86c4d74
[02:02:29] <hannelita> ping all.... Is there any example of a seam module already using PicketLink? :) Or Confbuzz will be the first one?
[02:03:04] <sbryzak> hannelita: idmconsole uses it
[02:03:14] <hannelita> sbryzak: thanks
[02:04:44] <jbossbot> git [transaction] push master 0cb749d.. Shane Bryzak update parent, seam-bom version, fix compiler errors, fix distribution
[02:04:44] <jbossbot> git [transaction] push master 8c5d3de.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[02:04:44] <jbossbot> git [transaction] push master 86c4d74.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[02:04:44] <jbossbot> git [transaction] push master 665dedc.. Shane Bryzak Merge branch 'release/3.1.0.Beta2'
[02:04:45] <jbossbot> git [transaction] push master URL: http://github.com/seam/transaction/compare/0eb905f...665dedc
[02:04:45] <jbossbot> git [transaction] push develop 8c5d3de.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[02:04:46] <jbossbot> git [transaction] push develop 86c4d74.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[02:04:47] <jbossbot> git [transaction] push develop 3bc2443.. Shane Bryzak Merge branch 'release/3.1.0.Beta2' into develop
[02:04:48] <jbossbot> git [transaction] push develop URL: http://github.com/seam/transaction/compare/0cb749d...3bc2443
[02:10:03] *** tkimura has joined #seam-dev
[02:11:34] *** tsurdilo2 has quit IRC
[02:18:34] <jbossbot> git [persistence] push develop 3d5d972.. Shane Bryzak update parent and bom, fix compiler errors, fix dist
[02:18:34] <jbossbot> git [persistence] push develop URL: http://github.com/seam/persistence/compare/cd88918...3d5d972
[02:23:27] <jbossbot> git [persistence] push 3.1.0.Beta2 181f9ab.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[02:23:27] <jbossbot> git [persistence] push 3.1.0.Beta2 URL: http://github.com/seam/persistence/compare/0000000...181f9ab
[02:23:31] <jbossbot> git [persistence] push 3.1.0.Beta2 URL: http://github.com/seam/persistence/compare/0000000...ccd788a
[02:23:37] <jbossbot> git [persistence] push 3.1.0.Beta2 18c9cea.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[02:23:37] <jbossbot> git [persistence] push 3.1.0.Beta2 URL: http://github.com/seam/persistence/compare/181f9ab...18c9cea
[02:28:27] <jbossbot> git [persistence] push develop 181f9ab.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[02:28:27] <jbossbot> git [persistence] push develop 18c9cea.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[02:28:27] <jbossbot> git [persistence] push develop ad31c3c.. Shane Bryzak Merge branch 'release/3.1.0.Beta2' into develop
[02:28:27] <jbossbot> git [persistence] push develop URL: http://github.com/seam/persistence/compare/3d5d972...ad31c3c
[02:28:28] <jbossbot> git [persistence] push master 3d5d972.. Shane Bryzak update parent and bom, fix compiler errors, fix dist
[02:28:28] <jbossbot> git [persistence] push master 181f9ab.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[02:28:29] <jbossbot> git [persistence] push master 18c9cea.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[02:28:29] <jbossbot> git [persistence] push master 19eae8d.. Shane Bryzak Merge branch 'release/3.1.0.Beta2'
[02:28:30] <jbossbot> git [persistence] push master URL: http://github.com/seam/persistence/compare/db9a688...19eae8d
[02:36:04] *** hannelita has quit IRC
[02:43:25] <jbossbot> git [config] push develop a1ece6f.. Shane Bryzak update parent, bom, fix distribution
[02:43:25] <jbossbot> git [config] push develop URL: http://github.com/seam/config/compare/d53b19f...a1ece6f
[02:45:45] *** jamezp is now known as jamezp_afk
[02:46:27] <jbossbot> git [config] push 3.1.0.Beta2 686f85e.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[02:46:27] <jbossbot> git [config] push 3.1.0.Beta2 URL: http://github.com/seam/config/compare/0000000...686f85e
[02:46:32] <jbossbot> git [config] push 3.1.0.Beta2 URL: http://github.com/seam/config/compare/0000000...02bf8b2
[02:46:40] <jbossbot> git [config] push 3.1.0.Beta2 0c5a87a.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[02:46:40] <jbossbot> git [config] push 3.1.0.Beta2 URL: http://github.com/seam/config/compare/686f85e...0c5a87a
[02:53:35] <jbossbot> git [config] push develop 686f85e.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[02:53:35] <jbossbot> git [config] push develop 0c5a87a.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[02:53:35] <jbossbot> git [config] push develop 41f1eb2.. Shane Bryzak Merge branch 'release/3.1.0.Beta2' into develop
[02:53:36] <jbossbot> git [config] push develop URL: http://github.com/seam/config/compare/a1ece6f...41f1eb2
[02:53:36] <jbossbot> git [config] push master a1ece6f.. Shane Bryzak update parent, bom, fix distribution
[02:53:37] <jbossbot> git [config] push master 686f85e.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[02:53:38] <jbossbot> git [config] push master 0c5a87a.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[02:53:39] <jbossbot> git [config] push master e32c41b.. Shane Bryzak Merge branch 'release/3.1.0.Beta2'
[02:53:39] <jbossbot> git [config] push master URL: http://github.com/seam/config/compare/3dd6d91...e32c41b
[03:02:03] *** lazarotti has quit IRC
[03:16:25] *** daniel_hinojosa has quit IRC
[03:17:04] *** lazarotti has joined #seam-dev
[03:20:40] *** akazakov has quit IRC
[03:23:00] <jbossbot> git [validation] push develop 7b92305.. Shane Bryzak update seam-parent, bom, fix tests, distribution
[03:23:00] <jbossbot> git [validation] push develop URL: http://github.com/seam/validation/compare/1f738e6...7b92305
[03:30:22] <jbossbot> git [validation] push develop 2ebcafa.. Shane Bryzak fixed distribution
[03:30:22] <jbossbot> git [validation] push develop URL: http://github.com/seam/validation/compare/7b92305...2ebcafa
[03:34:47] <jbossbot> git [validation] push 3.1.0.Beta2 8a92e6d.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[03:34:47] <jbossbot> git [validation] push 3.1.0.Beta2 URL: http://github.com/seam/validation/compare/0000000...8a92e6d
[03:34:52] <jbossbot> git [validation] push 3.1.0.Beta2 URL: http://github.com/seam/validation/compare/0000000...12a4eee
[03:35:00] <jbossbot> git [validation] push 3.1.0.Beta2 6584478.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[03:35:00] <jbossbot> git [validation] push 3.1.0.Beta2 URL: http://github.com/seam/validation/compare/8a92e6d...6584478
[03:43:39] <jbossbot> git [validation] push develop 8a92e6d.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[03:43:40] <jbossbot> git [validation] push develop 6584478.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[03:43:40] <jbossbot> git [validation] push develop 8d0bf49.. Shane Bryzak Merge branch 'release/3.1.0.Beta2' into develop
[03:43:40] <jbossbot> git [validation] push develop URL: http://github.com/seam/validation/compare/2ebcafa...8d0bf49
[03:43:41] <jbossbot> git [validation] push master 1f738e6.. Shane Bryzak Merge branch 'release/3.1.0.Beta1' into develop
[03:43:42] <jbossbot> git [validation] push master 7b92305.. Shane Bryzak update seam-parent, bom, fix tests, distribution
[03:43:42] <jbossbot> git [validation] push master 2ebcafa.. Shane Bryzak fixed distribution
[03:43:43] <jbossbot> git [validation] push master 8a92e6d.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[03:43:44] <jbossbot> git [validation] push master 6584478.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[03:43:45] <jbossbot> git [validation] push master fe41e9c.. Shane Bryzak Merge branch 'release/3.1.0.Beta2'...
[03:43:45] <jbossbot> git [validation] push master URL: http://github.com/seam/validation/compare/8c05cc2...fe41e9c
[04:22:39] *** kenfinnigan has joined #seam-dev
[04:25:15] *** edburns_away is now known as edburns
[04:28:34] *** Diablo-D3 has joined #seam-dev
[04:46:54] <jbossbot> git [servlet] push develop 41b9c29.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta1
[04:46:54] <jbossbot> git [servlet] push develop dc882bc.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[04:46:54] <jbossbot> git [servlet] push develop 7125ef9.. Shane Bryzak Merge branch 'release/3.1.0.Beta1' into develop
[04:46:55] <jbossbot> git [servlet] push develop URL: http://github.com/seam/servlet/compare/489c513...7125ef9
[04:46:55] <jbossbot> git [servlet] push master 4b0afc5.. George Gastaldi Fix in Documentation by dhinojosa
[04:46:56] <jbossbot> git [servlet] push master b211e93.. George Gastaldi Removed combined and changed impl artifact name
[04:46:57] <jbossbot> git [servlet] push master ca67648.. Shane Bryzak updated versions
[04:46:58] <jbossbot> git [servlet] push master 2b43094.. Shane Bryzak update versions, fix compiler errors
[04:46:58] <jbossbot> git [servlet] push master 489c513.. Shane Bryzak fix dependencies
[04:46:59] <jbossbot> git [servlet] push master 41b9c29.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta1
[04:47:00] <jbossbot> git [servlet] push master dc882bc.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[04:47:01] <jbossbot> git [servlet] push master 8fe95db.. Shane Bryzak Merge branch 'release/3.1.0.Beta1'
[04:47:01] <jbossbot> git [servlet] push master URL: http://github.com/seam/servlet/compare/b871d07...8fe95db
[04:48:22] *** kenfinnigan has quit IRC
[04:48:32] <jbossbot> git [servlet] push develop 54cfa3b.. Shane Bryzak update parent version, bom, fix distribution
[04:48:32] <jbossbot> git [servlet] push develop URL: http://github.com/seam/servlet/compare/7125ef9...54cfa3b
[04:59:48] *** daniel_hinojosa has joined #seam-dev
[04:59:50] <jbossbot> git [remoting] push develop 4fc2749.. Shane Bryzak update parent, bom, fix compiler errors
[04:59:50] <jbossbot> git [remoting] push develop c156f23.. Shane Bryzak Merge branch 'develop' of github.com:seam/remoting into develop
[04:59:50] <jbossbot> git [remoting] push develop URL: http://github.com/seam/remoting/compare/c0abe7d...c156f23
[05:07:12] *** daniel_hinojosa has quit IRC
[05:11:51] *** mateus has joined #seam-dev
[05:14:30] *** prabhatjha has quit IRC
[05:15:14] <jbossbot> git [international] push develop 9683c8d.. Shane Bryzak update parent and bom versions, fix compiler errors, fix distribution
[05:15:14] <jbossbot> git [international] push develop URL: http://github.com/seam/international/compare/41fb8b0...9683c8d
[05:22:29] <jbossbot> git [international] push develop 98ceaec.. Shane Bryzak fix source classifier
[05:22:30] <jbossbot> git [international] push develop URL: http://github.com/seam/international/compare/9683c8d...98ceaec
[05:28:47] <jbossbot> git [international] push develop 7e92acc.. Shane Bryzak remove classifier
[05:28:47] <jbossbot> git [international] push develop URL: http://github.com/seam/international/compare/98ceaec...7e92acc
[05:31:13] <jbossbot> git [international] push 3.1.0.Beta2 618aba0.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[05:31:14] <jbossbot> git [international] push 3.1.0.Beta2 URL: http://github.com/seam/international/compare/0000000...618aba0
[05:31:17] <jbossbot> git [international] push 3.1.0.Beta2 URL: http://github.com/seam/international/compare/0000000...a87539a
[05:31:23] <jbossbot> git [international] push 3.1.0.Beta2 a9ec465.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[05:31:23] <jbossbot> git [international] push 3.1.0.Beta2 URL: http://github.com/seam/international/compare/618aba0...a9ec465
[05:35:33] <jbossbot> git [international] push develop 618aba0.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[05:35:33] <jbossbot> git [international] push develop a9ec465.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[05:35:33] <jbossbot> git [international] push develop 1817cf9.. Shane Bryzak version info
[05:35:33] <jbossbot> git [international] push develop d8608a0.. Shane Bryzak Merge branch 'release/3.1.0.Beta2' into develop
[05:35:34] <jbossbot> git [international] push develop URL: http://github.com/seam/international/compare/7e92acc...d8608a0
[05:35:35] <jbossbot> git [international] push master 9683c8d.. Shane Bryzak update parent and bom versions, fix compiler errors, fix distribution
[05:35:36] <jbossbot> git [international] push master 98ceaec.. Shane Bryzak fix source classifier
[05:35:36] <jbossbot> git [international] push master 7e92acc.. Shane Bryzak remove classifier
[05:35:37] <jbossbot> git [international] push master 618aba0.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[05:35:38] <jbossbot> git [international] push master a9ec465.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[05:35:39] <jbossbot> git [international] push master 1817cf9.. Shane Bryzak version info
[05:35:39] <jbossbot> git [international] push master 48bc2f0.. Shane Bryzak Merge branch 'release/3.1.0.Beta2'
[05:35:40] <jbossbot> git [international] push master URL: http://github.com/seam/international/compare/dee8e87...48bc2f0
[05:37:29] *** edburns is now known as edburns_away
[05:45:22] <jbossbot> git [wicket] push develop 6dba8df.. Shane Bryzak update parent, bom, fix compiler errors
[05:45:22] <jbossbot> git [wicket] push develop URL: http://github.com/seam/wicket/compare/485f00a...6dba8df
[05:47:22] *** lightguard_jp has joined #seam-dev
[05:53:07] <jbossbot> git [wicket] push 3.1.0.Beta2 f49149b.. Shane Bryzak fix classifier
[05:53:07] <jbossbot> git [wicket] push 3.1.0.Beta2 1d853e0.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[05:53:07] <jbossbot> git [wicket] push 3.1.0.Beta2 URL: http://github.com/seam/wicket/compare/0000000...1d853e0
[05:53:12] <jbossbot> git [wicket] push 3.1.0.Beta2 URL: http://github.com/seam/wicket/compare/0000000...421d86c
[05:53:18] <jbossbot> git [wicket] push 3.1.0.Beta2 0ca3518.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[05:53:18] <jbossbot> git [wicket] push 3.1.0.Beta2 URL: http://github.com/seam/wicket/compare/1d853e0...0ca3518
[05:56:59] <jbossbot> git [wicket] push develop f49149b.. Shane Bryzak fix classifier
[05:56:59] <jbossbot> git [wicket] push develop 1d853e0.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[05:56:59] <jbossbot> git [wicket] push develop 0ca3518.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[05:56:59] <jbossbot> git [wicket] push develop b2ad8bc.. Shane Bryzak Merge branch 'release/3.1.0.Beta2' into develop
[05:56:59] <jbossbot> git [wicket] push develop URL: http://github.com/seam/wicket/compare/6dba8df...b2ad8bc
[05:57:00] <jbossbot> git [wicket] push master 6dba8df.. Shane Bryzak update parent, bom, fix compiler errors
[05:57:01] <jbossbot> git [wicket] push master f49149b.. Shane Bryzak fix classifier
[05:57:02] <jbossbot> git [wicket] push master 1d853e0.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[05:57:02] <jbossbot> git [wicket] push master 0ca3518.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[05:57:03] <jbossbot> git [wicket] push master 23f2cad.. Shane Bryzak Merge branch 'release/3.1.0.Beta2'
[05:57:04] <jbossbot> git [wicket] push master URL: http://github.com/seam/wicket/compare/75cd1bd...23f2cad
[06:00:32] <jbossbot> git [faces] push develop 70fd68d.. Shane Bryzak update parent, bom versions
[06:00:32] <jbossbot> git [faces] push develop URL: http://github.com/seam/faces/compare/784ee63...70fd68d
[06:02:57] *** daniel_hinojosa has joined #seam-dev
[06:04:36] <jbossbot> git [security] push develop 1733e26.. Shane Bryzak update parent and bom, fix compiler errors
[06:04:36] <jbossbot> git [security] push develop URL: http://github.com/seam/security/compare/557eaaf...1733e26
[06:05:39] <lightguard_jp> sbryzak: I'll do Catch tonight
[06:06:03] <sbryzak> lightguard_jp: thanks, quite a few of the other modules need it done before they can be released
[06:09:09] *** daniel_hinojosa has quit IRC
[06:11:30] *** daniel_hinojosa has joined #seam-dev
[06:14:15] <jbossbot> git [reports] push develop 0b80a84.. Shane Bryzak fix distribution, compiler errors
[06:14:15] <jbossbot> git [reports] push develop URL: http://github.com/seam/reports/compare/b263da1...0b80a84
[06:15:27] *** mateus has quit IRC
[06:20:41] <jbossbot> git [reports] push 3.1.0.Beta2 0d51df3.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[06:20:41] <jbossbot> git [reports] push 3.1.0.Beta2 URL: http://github.com/seam/reports/compare/0000000...0d51df3
[06:20:46] <jbossbot> git [reports] push 3.1.0.Beta2 URL: http://github.com/seam/reports/compare/0000000...01ce8c7
[06:20:57] <jbossbot> git [reports] push 3.1.0.Beta2 9bf5faa.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[06:20:57] <jbossbot> git [reports] push 3.1.0.Beta2 URL: http://github.com/seam/reports/compare/0d51df3...9bf5faa
[06:22:46] <lightguard_jp> I love it when tests pass in the IDE but die on the cli
[06:23:49] *** gastaldi has joined #seam-dev
[06:23:58] <gastaldi> hey
[06:24:27] <sbryzak> lightguard_jp: could you add jenkins to the list of agenda items for tomorrow?
[06:24:32] <sbryzak> gataldi: heya
[06:24:41] <gastaldi> wow, my mailbox is filled with the jenkins warnings
[06:24:46] <sbryzak> gastaldi: just doing seam reports release
[06:24:53] <sbryzak> yeah i just got 16 of them
[06:24:57] <gastaldi> Cool
[06:25:14] <lightguard_jp> what do we want to talk about?
[06:27:05] <sbryzak> about setting up cloudbees
[06:27:14] <sbryzak> getting everyone access, etc
[06:27:28] <lightguard_jp> Okay
[06:27:39] <sbryzak> basically i want to explore our options
[06:28:19] <jbossbot> git [reports] push develop 0d51df3.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[06:28:19] <jbossbot> git [reports] push develop 9bf5faa.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[06:28:19] <jbossbot> git [reports] push develop b8ef99a.. Shane Bryzak Merge branch 'release/3.1.0.Beta2' into develop
[06:28:19] <jbossbot> git [reports] push develop URL: http://github.com/seam/reports/compare/0b80a84...b8ef99a
[06:28:19] <jbossbot> git [reports] push master 0b80a84.. Shane Bryzak fix distribution, compiler errors
[06:28:20] <jbossbot> git [reports] push master 0d51df3.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[06:28:21] <jbossbot> git [reports] push master 9bf5faa.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[06:28:21] <jbossbot> git [reports] push master 0f346c4.. Shane Bryzak Merge branch 'release/3.1.0.Beta2'
[06:28:22] <jbossbot> git [reports] push master URL: http://github.com/seam/reports/compare/2580d42...0f346c4
[06:28:29] <gastaldi> hum, we have only 5 modules on cloudbees
[06:28:42] <gastaldi> Ah ! We can make it work under Openshift ! :D
[06:28:53] <gastaldi> I suppose
[06:28:53] <lightguard_jp> I think that would take some work.
[06:29:31] <gastaldi> hummm
[06:29:35] <lightguard_jp> It would be amazing for Red Hat to offer it, but I think there's a lot of work that would need to happen, especially to setup slaves and have everything talking correctly.
[06:29:35] <gastaldi> Worth a shot :)
[06:29:45] <gastaldi> oh
[06:29:56] <gastaldi> Well, no slaves necessary initially
[06:30:05] <gastaldi> Let them run free :)
[06:30:22] *** lincolnthree1 has joined #seam-dev
[06:30:29] *** lincolnthree1 has left #seam-dev
[06:31:49] <gastaldi> yay ! Seam Reports is 3.1.0.Beta2 now ;)
[06:32:52] <sbryzak> yup, release is done
[06:32:58] <sbryzak> let's never talk about beta1
[06:33:09] <gastaldi> lol
[06:33:14] <gastaldi> It never existed
[06:34:13] <gastaldi> Maven is such a pain when it comes to releasing, yeah ?
[06:34:34] <sbryzak> not just releasing
[06:35:20] <gastaldi> We must have that M2Release plugin installed on jenkins. Too bad the one in cloudbees does not support that
[06:37:15] <lightguard_jp> gastaldi: We just don't have the control currently to install it.
[06:37:24] <gastaldi> lightguard_jp: Yeah, I know
[06:37:44] <gastaldi> lightguard_jp: Just wanted to recall this issue once again :)
[06:37:49] <lightguard_jp> Gotta pay them $$ to do that :)
[06:38:10] <gastaldi> Hum.. Not if on OpenShift :)
[06:38:21] <gastaldi> I really need to test that
[06:39:30] <gastaldi> https://www.redhat.com/openshift/blogs/whats-new-in-openshift-august-2011
[06:39:33] <gastaldi> Cool huh ?
[06:39:38] <gastaldi> 256 Mb of storage
[06:41:14] *** clerum has quit IRC
[06:42:41] <gastaldi> Have anyone used ExtJS ?
[06:43:17] <gastaldi> I was thinking of a web framework to use it and take advantage of CDI and JEE 6
[06:43:44] <Diablo-D3> heh
[06:43:53] <Diablo-D3> I dont get the point of all these goddamned JS frameworks
[06:43:59] 
[06:44:08] <Diablo-D3> gastaldi: well
[06:44:17] <Diablo-D3> a lot of the complex ones basically imply you're using standards compliant backends
[06:44:30] <Diablo-D3> like, outputting json or xml in a normal form
[06:44:57] <Diablo-D3> so you write your website client shit in js first, and then match your server side shit to it
[06:45:05] <Diablo-D3> its the opposite of, say, richfaces
[06:45:16] <Diablo-D3> where richfaces mocks up the client side shit to match your server side shit
[06:46:20] 
[06:46:24] <gastaldi> :)
[06:46:41] <Diablo-D3> exactly
[06:47:02] <Diablo-D3> the real problem is all these goddamned js frameworks are huge
[06:47:04] <Diablo-D3> and redundant
[06:47:10] <Diablo-D3> and you cant just glue together the parts you want either
[06:47:28] <Diablo-D3> what seam needs is a dummy cat+min module
[06:47:42] <gastaldi> cat+min ?
[06:47:54] <Diablo-D3> cat and minification
[06:48:10] <Diablo-D3> loading multiple js files == evil as hell
[06:49:17] <Diablo-D3> slow too
[06:50:05] <gastaldi> extjs has one
[06:50:09] <gastaldi> big one
[06:50:56] <Diablo-D3> no
[06:51:04] <Diablo-D3> extjs has several once you start writing your own code.
[06:51:10] <Diablo-D3> and dragging in other peoples extjs using shit
[06:51:17] <gastaldi> The interface is so pretty that you would hardly choose another framework
[06:51:21] <Diablo-D3> same thing if you s/extjs/jquery/
[06:51:40] <Diablo-D3> understand the problem now?
[06:52:32] <gastaldi> yeah
[06:52:43] 
[06:53:14] <lightguard_jp> I'm invoking http://seamframework.org/Seam3/Chat#H-ChatRoomConduct.
[06:53:23] <lightguard_jp> Diablo-D3: You've been asked to refrain from the language before.
[06:53:37] <lightguard_jp> Do it again and you're banned.
[06:53:41] <Diablo-D3> gastaldi: no, but thats the problem.
[06:53:50] <Diablo-D3> gastaldi: having more than one file of js is bad.
[06:54:06] <Diablo-D3> richfaces does this completely wrong
[06:54:17] <Diablo-D3> it could spam a dozen files, all unique for that request
[06:54:19] <Diablo-D3> its insane
[06:54:49] <Diablo-D3> who cares how fast whatever new browser's new js engine is
[06:55:05] <Diablo-D3> if you're feeding it crap, its going to be slow
[06:55:09] <Diablo-D3> dont feed it crap
[06:56:37] <lightguard_jp> That is messed up. Thank you maven, junit and hamcrest. Use the official hamcrest lib instead of what junit bundles and the stack trace changes
[06:57:35] <Diablo-D3> lightguard_jp: does it matter? java is a sinking ship!
[06:58:23] <Diablo-D3> oracle is the iceberg, etc etc etc
[06:58:46] <Diablo-D3> Im still working on my troll rhetoric for this one
[07:01:28] <lightguard_jp> sbryzak: Any reason we're using junit 4.8.1 instead of 4.8.2?
[07:03:01] <gastaldi> lightguard_jp: Huh, there is 4.9 now :)
[07:03:22] <lightguard_jp> They're at 4.9 now?
[07:03:30] <gastaldi> yeah
[07:03:31] <lightguard_jp> When did that happen? I looked a couple of weeks ago
[07:03:37] <gastaldi> Yesterday
[07:03:50] <gastaldi> https://github.com/KentBeck/junit/downloads
[07:04:45] <gastaldi> hum, not in  the official repo yet
[07:06:41] 
[07:07:00] <lightguard_jp> Aslak wasn't kidding when he said testng and junit are both moving in different directions. Maybe that was Dan.
[07:08:35] <lightguard_jp> sbryzak: What's the name of the logging jar?
[07:09:22] <lightguard_jp> We put it back into solder, didn't we?
[07:10:22] <gastaldi> ok, gotta sleep now
[07:10:27] <lightguard_jp> gastaldi: night
[07:10:30] 
[07:10:43] *** gastaldi has quit IRC
[07:28:23] <lightguard_jp> sbryzak: ping
[07:31:23] *** jharting has joined #seam-dev
[07:32:43] <sbryzak> lightguard_jp: pong, sorry was afk
[07:35:18] <lightguard_jp> I think I'm getting there.
[07:35:25] <lightguard_jp> Had a question but I think I figured it out
[07:35:56] <lightguard_jp> Testing this stuff when you have to include other artifacts in the sw archive is very error prone
[07:36:10] <lightguard_jp> I think we need to talk to aslak, andrew, and stuart to see if there's a better way
[07:36:18] <Diablo-D3> for what?
[07:39:00] <lightguard_jp> I'm getting java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;) for testing with embedded weld
[07:39:07] <lightguard_jp> sbryzak: any ideas ^^ ?
[07:39:20] <sbryzak> ah yes, slf4j version mismatch
[07:39:27] <Diablo-D3> ver mism... yeah
[07:39:33] <sbryzak> it's because weld is using an older version
[07:39:48] <sbryzak> need to override it with 1.5.10 i think
[07:40:48] <lightguard_jp> That's what it is
[07:41:08] <lightguard_jp> From the catch testsuite
[07:41:25] <lightguard_jp> Did the container boms get pulled up?
[07:41:28] <sbryzak> what does mvn dependency:tree say?
[07:41:50] <sbryzak> we're not really using the container boms yet, until we sort out the issues with surefire
[07:42:08] <sbryzak> i think ken may be using them, i'm not sure
[07:42:24] <lightguard_jp> bah
[07:42:27] <Diablo-D3> so guys
[07:42:34] <Diablo-D3> slf4j really is the best logging framework out there, right?
[07:42:38] <lightguard_jp> I have 1.6.1 and 1.5.10 for different jars
[07:43:05] <sbryzak> lightguard_jp: yeah you have to override slf4j-api i think
[07:43:24] <Diablo-D3> guys?
[07:43:25] <sbryzak> Diablo-D3: logging in java is a big mess
[07:43:30] <Diablo-D3> yes it is
[07:43:39] <Diablo-D3> but I wanna make sure Im ripping off the right API
[07:43:42] <sbryzak> if they had of gotten jdk logging right in the first place it wouldn't be in this state
[07:43:48] <Diablo-D3> Ive used slf4j, and I do like it
[07:43:59] <sbryzak> well if you're using seam, just use org.jboss.seam.logging.Logger
[07:44:07] <Diablo-D3> nope, this is for Seaking.
[07:44:08] <sbryzak> it will then delegate to the correct underlying logging api
[07:44:32] <sbryzak> for non seam, yes i recommend slf4j
[07:44:41] <Diablo-D3> well like
[07:44:45] <Diablo-D3> does any other language get it right?
[07:44:54] <Diablo-D3> because from what I can see, other languages dont even have real logging frameworks
[07:44:55] <sbryzak> who knows
[07:45:19] <sbryzak> i'm sure there would be some logging framework for .net
[07:45:47] <sbryzak> http://www.dotnetlogging.com/
[07:46:14] <sbryzak> looks like they have a million different logging libraries also
[07:46:33] <Diablo-D3> well c# copied java
[07:46:36] <Diablo-D3> including all the bad parts
[07:46:58] <Diablo-D3> holy fuck
[07:47:04] <Diablo-D3> sbryzak: thats insane!
[07:47:13] <Diablo-D3> theres like 9000 .net frameworks
[07:47:23] <Diablo-D3> at least java only has like 3
[07:48:26] *** tremes has joined #seam-dev
[08:04:10] <lightguard_jp> sbryzak: no workie. I've tried specifying my own version, excluding the one from weld-core in the container bom nothing seems to be working. I'm always getting the 1.6.1 version.
[08:04:26] <lightguard_jp> And I can't get more current versions of the other slf4j jars
[08:07:16] <lightguard_jp> might have it now
[08:08:12] *** chkal has joined #seam-dev
[08:08:59] <sbryzak> lightguard_jp: can you pastebin your dependency:tree ?
[08:11:08] *** oskutka has joined #seam-dev
[08:15:45] <lightguard_jp> sbryzak: We'll see if this one runs
[08:16:49] <lightguard_jp> sbryzak: So can't wait to move this over to gradle when it hits 1.0
[08:17:38] <sbryzak> i think i feel the same way
[08:17:58] <sbryzak> my ultimate fantasy is for jenkins to build the releases for us
[08:18:20] *** shervin_a has joined #seam-dev
[08:18:30] <jbossbot> git [social] push develop 1ea80f1.. Shane Bryzak update parent, bom, fix distribution, fix compiler errors
[08:18:30] <jbossbot> git [social] push develop URL: http://github.com/seam/social/compare/78d9e2d...1ea80f1
[08:18:41] *** lazarotti has quit IRC
[08:19:26] *** marekn has joined #seam-dev
[08:20:25] <lightguard_jp> sbryzak: Yes, that would be very nice
[08:23:04] <jbossbot> git [social] push develop fe22f6e.. Shane Bryzak fix example
[08:23:04] <jbossbot> git [social] push develop URL: http://github.com/seam/social/compare/1ea80f1...fe22f6e
[08:23:53] <lightguard_jp> sbryzak: Do we have a new bom?
[08:24:17] <sbryzak> yes, 3.1.0.Beta2
[08:24:30] <sbryzak> brb, going to electrocute myself
[08:24:49] <lightguard_jp> Should I call someone if you don't come back?
[08:30:54] *** mgoldmann has joined #seam-dev
[08:31:52] <sbryzak> it's ok, i survived
[08:32:07] <sbryzak> it rained really bad here the past week, and one of our light fittings filled up with water
[08:33:24] <lightguard_jp> doh
[08:33:49] <jbossbot> git [social] push 3.1.0.Beta2 3fd7490.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[08:33:49] <jbossbot> git [social] push 3.1.0.Beta2 URL: http://github.com/seam/social/compare/0000000...3fd7490
[08:33:53] <jbossbot> git [social] push 3.1.0.Beta2 URL: http://github.com/seam/social/compare/0000000...1fdc307
[08:33:59] <jbossbot> git [social] push 3.1.0.Beta2 172b7bd.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[08:33:59] <jbossbot> git [social] push 3.1.0.Beta2 URL: http://github.com/seam/social/compare/3fd7490...172b7bd
[08:35:18] *** aslak has joined #seam-dev
[08:41:33] <jbossbot> git [catch] push 3.1.0.Beta2 4f2f7a5.. LightGuard Fixing tests for Beta2
[08:41:33] <jbossbot> git [catch] push 3.1.0.Beta2 b750c52.. LightGuard Removing solder snapshot
[08:41:33] <jbossbot> git [catch] push 3.1.0.Beta2 936ab9c.. LightGuard Removing seam bom snapshot
[08:41:33] <jbossbot> git [catch] push 3.1.0.Beta2 b970443.. LightGuard Adding id for assembly
[08:41:34] <jbossbot> git [catch] push 3.1.0.Beta2 db318c7.. LightGuard [maven-release-plugin] prepare release 3.1.0.Beta2
[08:41:34] <jbossbot> git [catch] push 3.1.0.Beta2 URL: http://github.com/seam/catch/compare/0000000...db318c7
[08:41:35] <jbossbot> git [catch] push 3.1.0.Beta2 URL: http://github.com/seam/catch/compare/0000000...75efddd
[08:41:37] <jbossbot> git [catch] push 3.1.0.Beta2 6ae02e7.. LightGuard [maven-release-plugin] prepare for next development iteration
[08:41:37] <jbossbot> git [catch] push 3.1.0.Beta2 URL: http://github.com/seam/catch/compare/db318c7...6ae02e7
[08:41:45] <jbossbot> git [social] push develop 3fd7490.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[08:41:46] <jbossbot> git [social] push develop 172b7bd.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[08:41:46] <jbossbot> git [social] push develop 3c6192f.. Shane Bryzak Merge branch 'release/3.1.0.Beta2' into develop
[08:41:46] <jbossbot> git [social] push develop URL: http://github.com/seam/social/compare/fe22f6e...3c6192f
[08:41:46] <jbossbot> git [social] push master 78d9e2d.. Shane Bryzak Merge branch 'release/3.1.0.Beta1' into develop
[08:41:47] <jbossbot> git [social] push master 1ea80f1.. Shane Bryzak update parent, bom, fix distribution, fix compiler errors
[08:41:48] <jbossbot> git [social] push master fe22f6e.. Shane Bryzak fix example
[08:41:49] <jbossbot> git [social] push master 3fd7490.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[08:41:49] <jbossbot> git [social] push master 172b7bd.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[08:41:50] <jbossbot> git [social] push master 29bbe54.. Shane Bryzak Merge branch 'release/3.1.0.Beta2'
[08:41:51] <jbossbot> git [social] push master URL: http://github.com/seam/social/compare/43f305c...29bbe54
[08:45:52] <lightguard_jp> sbryzak: Are we releasing the staging repos?
[08:46:04] <sbryzak> yep
[08:48:28] <jbossbot> git [catch] push develop 4f2f7a5.. LightGuard Fixing tests for Beta2
[08:48:28] <jbossbot> git [catch] push develop b750c52.. LightGuard Removing solder snapshot
[08:48:28] <jbossbot> git [catch] push develop 936ab9c.. LightGuard Removing seam bom snapshot
[08:48:28] <jbossbot> git [catch] push develop b970443.. LightGuard Adding id for assembly
[08:48:28] <jbossbot> git [catch] push develop db318c7.. LightGuard [maven-release-plugin] prepare release 3.1.0.Beta2
[08:48:29] <jbossbot> git [catch] push develop 6ae02e7.. LightGuard [maven-release-plugin] prepare for next development iteration
[08:48:30] <jbossbot> git [catch] push develop c082b27.. LightGuard Merge branch 'release/3.1.0.Beta2' into develop
[08:48:30] <jbossbot> git [catch] push develop URL: http://github.com/seam/catch/compare/6fc3acf...c082b27
[08:48:31] <jbossbot> git [catch] push master 8af7337.. LightGuard Merge branch 'hotfix/3.1.0.Beta1-pom' into develop
[08:48:32] <jbossbot> git [catch] push master 5deb0a2.. LightGuard Fixing up pom versions for release
[08:48:33] <jbossbot> git [catch] push master da0c3ff.. LightGuard Merge branch 'hotfix/3.1.0.Beta1'
[08:48:33] <jbossbot> git [catch] push master 6cee6df.. LightGuard Merge branch 'hotfix/3.1.0.Beta1' into develop
[08:48:34] <jbossbot> git [catch] push master 6fc3acf.. LightGuard Pom version fixes for continued developement
[08:48:35] <jbossbot> git [catch] push master 4f2f7a5.. LightGuard Fixing tests for Beta2
[08:48:36] <jbossbot> git [catch] push master b750c52.. LightGuard Removing solder snapshot
[08:48:36] <jbossbot> git [catch] push master 936ab9c.. LightGuard Removing seam bom snapshot
[08:48:37] <jbossbot> git [catch] push master b970443.. LightGuard Adding id for assembly
[08:48:38] <jbossbot> git [catch] push master db318c7.. LightGuard [maven-release-plugin] prepare release 3.1.0.Beta2
[08:48:39] <jbossbot> git [catch] push master 6ae02e7.. LightGuard [maven-release-plugin] prepare for next development iteration
[08:48:39] <jbossbot> git [catch] push master 645ac0f.. LightGuard Merge branch 'release/3.1.0.Beta2'
[08:48:40] <jbossbot> git [catch] push master URL: http://github.com/seam/catch/compare/63bc68f...645ac0f
[08:48:53] <lightguard_jp> Hm been a while since I pushed master :)
[08:51:48] <lightguard_jp> Catch is done
[09:16:24] *** maschmid has joined #seam-dev
[09:21:43] <sbryzak> lightguard_jp: awesome, thanks
[09:28:11] <sbryzak> lightguard_jp: did you release it on nexus?
[09:35:59] <lightguard_jp> yes
[09:36:13] *** epbernard has joined #seam-dev
[09:36:13] *** epbernard is now known as emmanuel
[09:37:10] <sbryzak> lightguard_jp: i'm getting [ERROR] Failed to execute goal on project seam-servlet: Could not resolve dependencies for project org.jboss.seam.servlet:seam-servlet:jar:3.1.0-SNAPSHOT: Failure to find org.jboss.seam.catch:seam-catch-api:jar:3.1.0.Beta2 in https://repository.jboss.org/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapse
[09:37:11] <sbryzak> d or updates are forced -> [Help 1]
[09:37:47] *** emmanuel has quit IRC
[09:38:09] <lightguard_jp> sbryzak: :( I released it
[09:39:03] <lightguard_jp> Or thought I did
[09:39:28] <sbryzak> it looks like it's still in staging: https://repository.jboss.org/nexus/index.html#nexus-search;quick~seam-catch-api
[09:41:22] <lightguard_jp> Just released it
[09:43:11] *** Nirvana111 has joined #seam-dev
[09:43:18] <Nirvana111> www.emzproductions.net
[09:43:23] <sbryzak> that seems to be working better, thanks
[09:43:30] <lightguard_jp> :)
[09:43:35] <Nirvana111> hi
[09:43:56] <Nirvana111> guys, my friends new game is looking for beta testers if anyone is interested.
[09:44:04] <Nirvana111> Its gonna be comin out soon
[09:44:50] <sbryzak> is it built with seam?
[09:45:00] <Nirvana111> idk
[09:45:02] <Nirvana111> probably
[09:46:18] *** sannegrinovero has joined #seam-dev
[09:48:29] *** Nirvana111 has left #seam-dev
[09:48:54] <jbossbot> git [servlet] push develop 1176085.. Shane Bryzak fix compiler errors
[09:48:54] <jbossbot> git [servlet] push develop URL: http://github.com/seam/servlet/compare/54cfa3b...1176085
[09:54:19] *** emmanuel has joined #seam-dev
[09:55:24] *** sannegrinovero has quit IRC
[09:58:18] <jbossbot> git [servlet] push 3.1.0.Beta2 665b185.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[09:58:18] <jbossbot> git [servlet] push 3.1.0.Beta2 URL: http://github.com/seam/servlet/compare/0000000...665b185
[09:58:23] <jbossbot> git [servlet] push 3.1.0.Beta2 URL: http://github.com/seam/servlet/compare/0000000...ff35a81
[09:58:29] <jbossbot> git [servlet] push 3.1.0.Beta2 2b4627e.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[09:58:29] <jbossbot> git [servlet] push 3.1.0.Beta2 URL: http://github.com/seam/servlet/compare/665b185...2b4627e
[09:58:40] *** sannegrinovero has joined #seam-dev
[09:58:54] <lightguard_jp> heading to bed
[10:03:37] <jbossbot> git [rest] push develop 5dce9b9.. Jozef Hartinger Testcase for SEAMREST-49
[10:03:39] <jbossbot> jira [SEAMREST-49] String response not rendered by @ResponseTemplate [Open (Unresolved) Bug, Major, Jozef Hartinger] https://issues.jboss.org/browse/SEAMREST-49
[10:03:39] <jbossbot> git [rest] push develop URL: http://github.com/seam/rest/compare/f6d5ddc...5dce9b9
[10:03:53] <jbossbot> git [rest] push develop 37b8610.. Jozef Hartinger minor
[10:03:53] <jbossbot> git [rest] push develop URL: http://github.com/seam/rest/compare/5dce9b9...37b8610
[10:04:03] *** lightguard_jp has quit IRC
[10:06:10] <jbossbot> git [servlet] push develop 665b185.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[10:06:10] <jbossbot> git [servlet] push develop 2b4627e.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[10:06:11] <jbossbot> git [servlet] push develop 8969b26.. Shane Bryzak Merge branch 'release/3.1.0.Beta2' into develop
[10:06:11] <jbossbot> git [servlet] push develop URL: http://github.com/seam/servlet/compare/1176085...8969b26
[10:06:11] <jbossbot> git [servlet] push master 54cfa3b.. Shane Bryzak update parent version, bom, fix distribution
[10:06:12] <jbossbot> git [servlet] push master 1176085.. Shane Bryzak fix compiler errors
[10:06:12] <jbossbot> git [servlet] push master 665b185.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[10:06:13] <jbossbot> git [servlet] push master 2b4627e.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[10:06:14] <jbossbot> git [servlet] push master 800923e.. Shane Bryzak Merge branch 'release/3.1.0.Beta2'
[10:06:14] <jbossbot> git [servlet] push master URL: http://github.com/seam/servlet/compare/8fe95db...800923e
[10:33:22] <jbossbot> git [remoting] push 3.1.0.Beta2 7cc08e4.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[10:33:22] <jbossbot> git [remoting] push 3.1.0.Beta2 URL: http://github.com/seam/remoting/compare/0000000...7cc08e4
[10:33:23] *** alesj has joined #seam-dev
[10:33:26] <jbossbot> git [remoting] push 3.1.0.Beta2 URL: http://github.com/seam/remoting/compare/0000000...28ff2fa
[10:33:32] <jbossbot> git [remoting] push 3.1.0.Beta2 8756663.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[10:33:32] <jbossbot> git [remoting] push 3.1.0.Beta2 URL: http://github.com/seam/remoting/compare/7cc08e4...8756663
[10:39:18] <jbossbot> git [remoting] push develop 7cc08e4.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[10:39:18] <jbossbot> git [remoting] push develop 8756663.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[10:39:18] <jbossbot> git [remoting] push develop 24f8163.. Shane Bryzak Merge branch 'release/3.1.0.Beta2' into develop
[10:39:18] <jbossbot> git [remoting] push develop URL: http://github.com/seam/remoting/compare/c156f23...24f8163
[10:39:19] <jbossbot> git [remoting] push master 2503d28.. Shane Bryzak added new dependencies
[10:39:20] <jbossbot> git [remoting] push master b0b62f3.. Shane Bryzak updated version
[10:39:21] <jbossbot> git [remoting] push master 952354d.. Shane Bryzak added missing dependencies
[10:39:21] <jbossbot> git [remoting] push master f89095d.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta1
[10:39:22] <jbossbot> git [remoting] push master e2d2814.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[10:39:23] <jbossbot> git [remoting] push master c0abe7d.. Shane Bryzak Merge pull request #23 from maschmid/SEAMREMOTING-41...
[10:39:24] <jbossbot> jira [SEAMREMOTING-41] Model example broken on AS7: Could not commit transaction. [Resolved (Done) Bug, Major, Marek Schmidt] https://issues.jboss.org/browse/SEAMREMOTING-41
[10:39:24] <jbossbot> git [remoting] push master 4fc2749.. Shane Bryzak update parent, bom, fix compiler errors
[10:39:25] <jbossbot> git [remoting] push master c156f23.. Shane Bryzak Merge branch 'develop' of github.com:seam/remoting into develop
[10:39:26] <jbossbot> git [remoting] push master 7cc08e4.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta2
[10:39:27] <jbossbot> git [remoting] push master 8756663.. Shane Bryzak [maven-release-plugin] prepare for next development iteration
[10:39:27] <jbossbot> git [remoting] push master 21c04c8.. Shane Bryzak Merge branch 'release/3.1.0.Beta2'
[10:39:28] <jbossbot> git [remoting] push master URL: http://github.com/seam/remoting/compare/4338ba3...21c04c8
[10:53:47] *** daniel_hinojosa has quit IRC
[11:22:57] *** tkimura has quit IRC
[11:39:36] *** stuartdouglas has quit IRC
[11:40:33] *** stuartdouglas has joined #seam-dev
[11:43:10] *** alesj has quit IRC
[11:56:29] *** alesj has joined #seam-dev
[11:58:05] *** ssachtleben has joined #seam-dev
[12:11:25] *** emmanuel has quit IRC
[12:12:32] *** tsurdilo has joined #seam-dev
[12:29:23] *** tremes has quit IRC
[12:32:14] *** tsurdilo has quit IRC
[12:32:31] *** dabloem has joined #seam-dev
[12:32:39] *** tsurdilo has joined #seam-dev
[12:41:25] *** silvio has joined #seam-dev
[12:43:38] *** ssachtleben has quit IRC
[12:58:39] *** silvio has left #seam-dev
[13:13:21] *** tremes has joined #seam-dev
[13:23:31] *** epbernard has joined #seam-dev
[13:23:31] *** epbernard is now known as emmanuel
[13:32:17] *** jose_freitas has joined #seam-dev
[13:59:16] *** mateus has joined #seam-dev
[14:00:15] *** rmartinelli has joined #seam-dev
[14:03:31] *** dabloem has quit IRC
[14:09:21] *** mgoldmann_ has joined #seam-dev
[14:09:57] *** mgoldmann has quit IRC
[14:10:10] *** dabloem has joined #seam-dev
[14:10:25] *** mgoldmann has joined #seam-dev
[14:14:49] *** mgoldmann_ has quit IRC
[14:42:55] *** shervin_a has quit IRC
[14:59:24] *** mateus has quit IRC
[15:10:55] *** amitev2 has joined #seam-dev
[15:12:38] *** amitev has quit IRC
[15:18:54] *** rmartinelli has quit IRC
[15:19:47] *** rmartinelli has joined #seam-dev
[15:30:41] *** aslak has quit IRC
[15:34:26] *** edburns_away is now known as edburns
[15:38:38] *** lazarotti has joined #seam-dev
[15:41:36] *** lazarotti has quit IRC
[15:42:50] *** lazarotti has joined #seam-dev
[15:47:15] *** amitev2 has quit IRC
[15:47:27] *** amitev has joined #seam-dev
[16:05:40] *** clerum has joined #seam-dev
[16:06:11] *** hannelita has joined #seam-dev
[16:08:07] *** amitev2 has joined #seam-dev
[16:09:49] *** amitev has quit IRC
[16:10:59] *** amitev2 is now known as amitev
[16:21:42] *** chkal has quit IRC
[16:25:51] *** mbg has joined #seam-dev
[16:29:21] *** marekn has quit IRC
[16:30:46] *** gastaldi has joined #seam-dev
[16:30:52] <gastaldi> morning all
[16:34:06] <jose_freitas> morning gastaldi
[16:36:43] <gastaldi> hey jose_freitas
[16:39:44] *** bleathem has joined #seam-dev
[16:40:03] <clerum> morning
[16:40:37] <jose_freitas> hey clerum, good morning, how are you doing with s:debug?
[16:41:55] <clerum> no progress
[16:42:20] <clerum> we hashed a few more things out on irc
[16:42:25] <clerum> and put that in the jira
[16:42:27] <clerum> but that is about it
[16:44:50] *** jganoff has joined #seam-dev
[16:45:08] <gastaldi> tremes: ping
[16:45:49] <tremes> gastaldi: pong
[16:46:10] <gastaldi> tremes: I checked your seam config example. It seems very good
[16:46:31] <tremes> hi. thanks. i am actually reading your notification
[16:46:38] <gastaldi> I am afraid that some dependencies might have changed with the latest version of Seam
[16:48:21] <tremes> i am going to change pom definition tomorrow and probably dependencies too
[16:48:27] <gastaldi> Cool
[16:48:53] <gastaldi> another thing: Do you mind using jUnit for the tests ?
[16:49:48] <tremes> no i don't...should i use jUnit?
[16:50:17] <gastaldi> I see you are using TestNG. We are in the middle of deciding which test framework to go on, and as Arquillian is JUnit-enabled, we rather stick to it for awhile
[16:50:52] <gastaldi> Of course, if TestNG has some specific features you need, then no problem on that
[16:51:18] <gastaldi> but I see you are using just the assertion part
[16:51:23] <tremes> ok..i will check it and try to use jUnit
[16:51:37] <gastaldi> Cool
[16:51:40] <gastaldi> Thanks
[17:00:01] <tremes> ok.i am heading home.bye
[17:00:43] *** tremes has quit IRC
[17:01:19] *** amitev has quit IRC
[17:02:46] *** jharting has quit IRC
[17:06:25] *** lincolnthree has joined #seam-dev
[17:07:45] *** mbg has quit IRC
[17:08:12] *** mbg has joined #seam-dev
[17:16:24] *** alesj has quit IRC
[17:21:45] *** oskutka has quit IRC
[17:25:52] *** gastaldi has quit IRC
[17:33:16] *** jamezp_afk is now known as jamezp
[17:44:58] *** emmanuel has quit IRC
[17:48:20] *** kevinpollet has joined #seam-dev
[17:51:01] *** akazakov has joined #seam-dev
[17:57:56] *** ssachtleben has joined #seam-dev
[18:02:15] *** epbernard has joined #seam-dev
[18:02:15] *** epbernard is now known as emmanuel
[18:13:07] <lincolnthree> We need a "Seam Best Practices" guide
[18:13:18] <lincolnthree> I have no idea how best to use Seam 3
[18:13:23] <lincolnthree> There are too many options!
[18:13:49] <ssachtleben> hey lincolnthree
[18:13:54] <lincolnthree> hey ssachtleben
[18:14:00] <lincolnthree> thanks for your post on the forums
[18:14:19] <ssachtleben> neeeeeed solution for live going with as 7 :P
[18:14:40] <ssachtleben> I try to play a bit around with modcluster config
[18:14:46] <ssachtleben> its really strange :(
[18:15:08] <lincolnthree> ssachtleben: have you debugged prettyfaces to see where the extra / is coming from?
[18:15:25] <ssachtleben> nope
[18:15:59] <lincolnthree> i would start there
[18:16:04] <lincolnthree> if you can tell me where the / is beign added
[18:16:06] <lincolnthree> i can try to help
[18:16:09] <lincolnthree> right now I'm working blind
[18:16:11] <lincolnthree> i have no idea
[18:16:11] <ssachtleben> is it easy and fast to setup?
[18:16:19] <lincolnthree> debugging?
[18:16:35] <ssachtleben> do I need to add prettyfaces as project?
[18:17:48] <lincolnthree> don't you have it in your app?
[18:17:58] <ssachtleben> as maven dependency
[18:18:13] *** maschmid has quit IRC
[18:28:24] <ssachtleben> lincolnthree
[18:28:26] <ssachtleben> https://github.com/ocpsoft/prettyfaces/blob/master/impl-jsf2/src/main/java/com/ocpsoft/pretty/faces/application/PrettyNavigationHandler.java
[18:28:29] <ssachtleben> this will be used?
[18:28:34] <lincolnthree> yes
[18:29:12] <ssachtleben> url.getMetadata().setLeadingSlash(true); :D
[18:29:31] <lincolnthree> what does that return?
[18:29:36] <lincolnthree> there should only be 1 leading slash
[18:30:23] <ssachtleben> I try to find out
[18:30:48] <ssachtleben> you should download and setup your own modcluster for a test
[18:31:01] <ssachtleben> its really easy and fast
[18:31:22] <lincolnthree> ssachtleben: if you give me a sample app that reproduces the problem, and some instructions, i will :)
[18:31:40] <lincolnthree> (I would just do it, but I've got a lot of stuff going on right now :()
[18:31:47] <ssachtleben> if I dont use this
[18:31:49] <ssachtleben> ProxyPassReverse / balancer://mycluster
[18:32:11] <ssachtleben> the redirect is domain:8085 -> serverip:8088 (jboss real port)
[18:32:17] <ssachtleben> :D
[18:32:49] <lincolnthree> hm?
[18:33:37] <ssachtleben> I dont understand why the behaviour between h:link with outcome mappingId and s:viewAction with returning mappingId is different
[18:33:51] <lincolnthree> it is?
[18:33:53] <lincolnthree> interesting...
[18:34:07] <ssachtleben> h:link = 1 slash | s:viewAction = 2 slashes
[18:34:09] <lincolnthree> maybe the issue is in s:viewaction
[18:40:29] <jbossbot> git [solder] push develop c09f99e.. Marek Schmidt fix generation of "Dependencies:" field in MANIFEST
[18:40:30] <jbossbot> git [solder] push develop ae39ed7.. George Gastaldi Merge pull request #40 from maschmid/fixmanifestdependencies...
[18:40:30] <jbossbot> git [solder] push develop URL: http://github.com/seam/solder/compare/841ba07...ae39ed7
[18:43:54] *** gastaldi has joined #seam-dev
[18:44:22] *** mbg|away has joined #seam-dev
[18:45:13] <gastaldi> hey all
[18:45:24] <lincolnthree> *chirp*
[18:45:32] <gastaldi> * crickets *
[18:45:44] <gastaldi> hey lincolnthree
[18:46:05] <lincolnthree> hey gastaldi, feel like making the scaffolding in forge better?
[18:46:09] <lincolnthree> you do!!?
[18:46:11] <gastaldi> When will you change the logo in http://seamframework.org/Seam3/Tooling ?
[18:46:12] <lincolnthree> awesome thanks!
[18:46:15] <gastaldi> hahaha
[18:46:21] <gastaldi> I wish
[18:47:27] <gastaldi> Probably I may have time to look at that on october  :(
[18:51:08] 
[18:51:23] <lincolnthree> gastaldi: what do you mean when am i going to update the logo?
[18:51:28] <lincolnthree> it's already current?
[18:51:37] <gastaldi> Hehe I must be crazy
[18:52:10] <lincolnthree> ;)
[18:52:14] <gastaldi> :)
[18:52:19] <lincolnthree> just fixed it
[18:52:20] <lincolnthree> thanks
[18:52:30] <gastaldi> good bye HAL
[18:52:39] <lincolnthree> hello awesome
[18:52:40] 
[18:52:52] <gastaldi> Hum
[18:53:04] <gastaldi> I was trying to get that forge logo on ASCII art
[18:53:08] <gastaldi> It would be cool
[18:53:09] <gastaldi> ;D
[18:53:52] <gastaldi> lincolnthree: jose_freitas once suggested having a plugin to create EJBs
[18:53:56] <gastaldi> on Forge
[18:54:10] <lincolnthree> gastaldi: ascii art would be cool
[18:54:11] <lincolnthree> yeah?
[18:54:25] <gastaldi> I am waiting for his pull request yet :)
[19:00:41] <gastaldi> I still have on my to-do list the creation of a web-app with a terminal-like input for Forge
[19:01:03] <gastaldi> probably using this: http://terminal.jcubic.pl/
[19:01:10] <gastaldi> Or primefaces terminal component
[19:01:41] <lincolnthree> :-D
[19:01:43] <lincolnthree> That woudl be awesome
[19:01:50] <gastaldi> indeed
[19:01:55] <gastaldi> Applications on the Cloud
[19:01:58] <lincolnthree> when yous tart doing that
[19:01:59] <lincolnthree> let me know
[19:02:06] <gastaldi> of course
[19:02:06] <lincolnthree> let me know what gets in your way
[19:02:16] <lincolnthree> i think it would be an excellent test of the design
[19:02:54] <gastaldi> Is it possible to provide a different input ?
[19:02:59] <gastaldi> Instead of System.in ?
[19:03:16] <lincolnthree> not sure... right now probably not, but we could fix that
[19:05:10] <gastaldi> hum, that would be a blocker
[19:05:27] <lincolnthree> yes
[19:05:33] <lincolnthree> but your work would flush out what needs to be done :)
[19:05:40] <lincolnthree> nothing is a blocker
[19:05:43] <lincolnthree> anything can be changed
[19:05:53] <gastaldi> Forgers never get blocked !
[19:06:03] <lincolnthree> we hammer our way through
[19:06:07] <gastaldi> yeah
[19:06:20] <gastaldi> Together with Arquillians we conquer the world
[19:06:58] <gastaldi> Riding a new AS7 vehicle
[19:11:07] *** tsurdilo has quit IRC
[19:15:46] *** edburns is now known as edburns_away
[19:17:36] <ssachtleben> lincolnthree I get Not a PrettyFaces navigation string - passing control to default nav-handler
[19:17:51] <lincolnthree> explain?
[19:17:51] <ssachtleben> on a pretty mappingId return
[19:18:16] <ssachtleben> s:viewAction invoke -> return pretty mappingId -> that message occures?
[19:18:17] <lincolnthree> (that sounds right, but tell me what you are seeing, more detail the better :))
[19:18:27] <lincolnthree> ah, interesting
[19:18:33] <lincolnthree> tell me literally what you are seeing
[19:19:45] <ssachtleben> what seeing? just switched prettyfaces on debug logging
[19:19:50] <lincolnthree> ah
[19:19:56] <lincolnthree> can you attach your debugger?
[19:19:59] <lincolnthree> that's what I'm asking :)
[19:21:13] <ssachtleben> Navigation requested: fromAction [#{landingPageAction.validate}], outcome [pretty:weblog_overview]
[19:21:20] <ssachtleben> Navigation requested: fromAction [#{weblogOverviewAction.validate}], outcome [null]
[19:21:26] <ssachtleben> Not a PrettyFaces navigation string - passing control to default nav-handler
[19:21:40] <lincolnthree> so for some reason, s:viewAction returns null?
[19:21:40] <ssachtleben> this occures on my initial domain call
[19:21:48] <lincolnthree> when it calls your method
[19:21:55] <ssachtleben> returns null = stay on same page do not redirect
[19:22:11] <ssachtleben> there is no prettyfaces navigation message after the first request
[19:22:29] <ssachtleben> I think its something in PrettyNavigationHandler
[19:22:38] <lincolnthree> im really confused right now. can you list the steps of what you are doing and what is happening?
[19:22:51] <ssachtleben> is it hard to remote debug ? never did before
[19:23:02] <lincolnthree> you need to start the server with the debug JVM flags
[19:23:25] <ssachtleben> I could do that its kind of staging system
[19:23:26] <lincolnthree> point your eclipse debugger at it
[19:23:38] <lincolnthree> thanks gastaldi!!
[19:24:22] <gastaldi> nop
[19:27:26] *** kevinpollet has quit IRC
[19:28:26] *** kevinpollet has joined #seam-dev
[19:30:25] <ssachtleben> ok
[19:37:54] *** tsurdilo has joined #seam-dev
[19:38:25] *** maschmid has joined #seam-dev
[19:40:13] *** nilian has joined #seam-dev
[19:43:24] *** tsurdilo has quit IRC
[19:43:46] *** tsurdilo has joined #seam-dev
[19:47:44] <ssachtleben> it works :)
[19:52:17] <ssachtleben> lincolnthree PrettyNavigationHandler only handles the internal xhtml links which are fine
[19:52:42] <ssachtleben> whats about the url pattern build?
[19:53:06] <lincolnthree> which piece of the code?
[19:53:12] <lincolnthree> i need more info :)
[19:53:16] <lincolnthree> im working blind here
[19:54:33] <ssachtleben> @URLMapping(id = "landingpage_start", pattern = "/", viewId = "/pages/landingpage/landingpage.seam")
[19:54:44] <lincolnthree> that looks fine
[19:54:44] <ssachtleben> PrettyNavigationHandler works with the viewId
[19:55:04] <ssachtleben> but where is the pattern used?
[19:55:17] <lincolnthree> sec
[19:56:46] <lincolnthree> which links are wrong?
[19:57:20] *** gastaldi has quit IRC
[19:57:24] <lincolnthree> ok ssachtleben
[19:57:26] <ssachtleben> pattern = "/test" -> will be //test
[19:57:27] <lincolnthree> in PrettyNavigationHandler
[19:57:38] <lincolnthree> yes but where do you *see* that link?
[19:57:48] <ssachtleben> in browser? :D
[19:57:48] <lincolnthree> in the HTML or in the URL?
[19:57:53] <lincolnthree> more speific...
[19:57:56] <lincolnthree> specific
[19:58:07] <ssachtleben> url field? :D
[19:58:13] <lincolnthree> ok, that's a start ;)
[19:58:21] <lincolnthree> so line 57 of PrettyNavigationHandler
[19:58:23] <lincolnthree> what do you see?
[19:58:23] <ssachtleben> its the outbound rewrite of the url
[19:58:39] <ssachtleben> if (!pr.redirect(context, outcome))
[19:58:51] <lincolnthree> ok good
[19:58:53] <lincolnthree> look there
[19:59:09] <ssachtleben> ah damn
[19:59:13] <lincolnthree> That's what does the redirect
[19:59:13] <ssachtleben> I overstepped that :D
[19:59:15] <lincolnthree> PrettyRedirector
[19:59:32] <lincolnthree> I'm guessing something in there is wrong.
[19:59:38] <lincolnthree> In this setup.
[19:59:49] <lincolnthree> Step through that.
[20:00:02] <lincolnthree> Tell me what you see, tell me *exactly* where the extra slash is added.
[20:00:04] <lincolnthree> :)
[20:00:17] *** daniel_hinojosa has joined #seam-dev
[20:02:07] <ssachtleben> ok it ends in ln 78
[20:02:21] <ssachtleben> externalContext.redirect("/blob.html");
[20:02:33] <lincolnthree> that should be correct
[20:02:36] <ssachtleben> i see in browser url field //blog.html :D
[20:02:41] <lincolnthree> now we need to look at PrettyFacesWrappedResponse
[20:02:56] <lincolnthree> could you GIST me your pretty-config.xml?
[20:03:01] <lincolnthree> if you have one
[20:03:07] <ssachtleben> only annotations
[20:03:11] <lincolnthree> ok
[20:03:20] *** kevinpollet has quit IRC
[20:03:40] <lincolnthree> start looking at PFWR at line 89
[20:03:54] <ssachtleben> which pkg?
[20:04:10] <lincolnthree> com.ocpsoft.pretty.faces.servlet.PrettyFacesWrappedResponse
[20:04:48] <ssachtleben> got it
[20:06:45] *** edburns_away is now known as edburns
[20:08:25] *** gastaldi has joined #seam-dev
[20:08:29] <ssachtleben> just simple slashes in all method invokes
[20:08:34] <lincolnthree> ?
[20:08:58] <ssachtleben> like return super.encodeURL("/blog.html");
[20:09:16] <lincolnthree> what does that return?
[20:09:46] <ssachtleben> "/blog.html" :D
[20:09:49] <lincolnthree> heh
[20:10:00] <lincolnthree> looks like PrettyFaces works then
[20:10:22] <lincolnthree> something else is wrong
[20:10:29] <lincolnthree> go back to PrettyRedirector for a moment
[20:10:48] <lincolnthree> which line is the redirect being performed on? 78?
[20:11:04] <lincolnthree> what is the value of redirectURL there?
[20:11:15] <ssachtleben> isnt there somewhere the full url build like domain + path
[20:11:22] <lincolnthree> no
[20:11:31] <lincolnthree> the servlet container handles that
[20:11:34] <bleathem> ugh. I've got a monster-long jira issue to read through
[20:11:44] <bleathem> jira comments should be resitricted to 137 characters
[20:11:49] <bleathem> or 140
[20:11:52] <bleathem> whaterver twitter is
[20:13:34] <ssachtleben> ln 78 was also "/blog.html" yeah
[20:14:01] <lincolnthree> ok
[20:14:04] <lincolnthree> prettyfaces is working
[20:14:36] <lincolnthree> errr wait
[20:15:17] <lincolnthree> what is the value of contextPath on line 74 ?
[20:15:48] *** gastaldi has quit IRC
[20:16:02] <lincolnthree> bleathem: http://dubiousquality.blogspot.com/2011/08/facepocalypse.html
[20:17:49] <bleathem> lincolnthree: why did I just read that?
[20:17:58] <lincolnthree> bleathem: because you couldn't help it
[20:18:04] <bleathem> lol!
[20:18:10] <ssachtleben> contextpath is ""
[20:18:31] <bleathem> Someone needs to tell Gloria about Google+ and circles
[20:18:47] <ssachtleben> but on h:link with prettyfaces mappingId the rewritehandler doesnt handle it?
[20:19:53] *** sannegrinovero has quit IRC
[20:26:23] <ssachtleben> ok seems like there is something strange going on in modcluster
[20:26:27] <ssachtleben> http://community.jboss.org/message/622758#622758
[20:29:42] <lincolnthree> ssachtleben: looking
[20:30:38] <lincolnthree> ssachtleben: so ot
[20:30:52] <lincolnthree> I think that mod_cluster may be doing something wrong
[20:31:15] <lincolnthree> but try something else for me
[20:31:23] <lincolnthree> While debugging, you should be able to change variable values
[20:31:41] <lincolnthree> Before externalContext.redirect(""); I want you to remove the first slash from the URL
[20:31:46] <lincolnthree> and tell me what happens
[20:31:56] <lincolnthree> it's technically incorrect to do so, but
[20:32:04] <lincolnthree> let's just see
[20:37:15] <ssachtleben> ah ok
[20:43:58] <ssachtleben> funny
[20:44:19] <ssachtleben> incoming "/blog.html" made to "forums.html" results in domain//forums.html :D
[20:45:02] <lincolnthree> LOL
[20:45:03] <lincolnthree> yeah ok
[20:45:22] <lincolnthree> that's weird
[20:45:24] <lincolnthree> very weird
[20:45:47] <lincolnthree> here's a weird question ;)
[20:45:55] <lincolnthree> i want you to create a pretty-config.xml file
[20:45:59] <lincolnthree> try this rule:
[20:46:53] *** alesj has joined #seam-dev
[20:47:12] <lincolnthree> <rewrite match="^//(\.*)$" substitute="$1" redirect="301" />
[20:47:18] <lincolnthree> put that in your pretty config.xml file
[20:47:23] <lincolnthree> and let's see if the problem goes away ;)
[20:47:37] <ssachtleben> ok :D
[20:48:03] <lincolnthree> something tells me it will not :/
[20:48:04] <lincolnthree> but
[20:48:09] <lincolnthree> and it's a hack anyway
[20:48:10] <lincolnthree> we'll see
[20:48:30] <lincolnthree> http://ocpsoft.com/docs/prettyfaces/3.3.0/en-US/html_single/#getstarted.prettyconfigxml
[20:48:40] *** kevinpollet has joined #seam-dev
[20:55:06] *** msmigielski has joined #seam-dev
[20:56:15] *** msmigielski has quit IRC
[20:57:24] *** lightguard_jp has joined #seam-dev
[20:57:41] <ssachtleben> lincolnthree same behavior
[20:57:44] *** lightguard_jp has quit IRC
[20:58:09] *** lightguard_jp has joined #seam-dev
[20:58:14] <lincolnthree> ssachtleben: ha, thought so
[20:58:15] <lincolnthree> ok
[20:58:25] <lincolnthree> definitely a bug with mod_cluster I think
[21:00:11] *** jamezp is now known as jamezp_afk
[21:02:43] <lincolnthree> anyone know how to resolve this?
[21:02:44] <lincolnthree> SOLDER-119
[21:02:45] <jbossbot> jira [SOLDER-119] CNFE org.jboss.logmanager.Logger$AttachmentKey on AS7 [Open (Unresolved) Bug, Blocker, Ken Finnigan] https://issues.jboss.org/browse/SOLDER-119
[21:02:53] <ssachtleben> damn
[21:03:09] <lincolnthree> ssachtleben: i can't see a reason for that to be failing
[21:03:29] <ssachtleben> I cant use as7 then :(
[21:03:29] <lincolnthree> unless mod cluster for some reason requires you redirect to a fully-qualified URL
[21:03:32] <lincolnthree> but that would be strange
[21:03:40] <ssachtleben> mod_jk -> ajp port as 7 failes
[21:03:50] <ssachtleben> mod_cluster -> works but double slash
[21:03:55] <ssachtleben> argh :D
[21:03:56] <lincolnthree> ssachtleben: we will figure this out
[21:04:21] <lincolnthree> what happens if you change the URL to redirect to the *full* url?
[21:04:26] <lincolnthree> does that work?
[21:04:28] <lightguard_jp> bleathem: http://seamframework.org/Community/ReadConfiguratedFacesViewInCode May be a good enhancement, if it's not already there.
[21:04:29] <lincolnthree> (it should)
[21:06:05] <ssachtleben> yeah full url works fine with redirect
[21:06:11] *** mbg|away has quit IRC
[21:06:22] <jamezp_afk> lincolnthree: That could be an issue with mixing LogManager's.
[21:07:41] <jamezp_afk> lincolnthree: I'm wondering if the Solder logger needs to be registered within the logging subsytem.
[21:07:59] <lincolnthree> hm
[21:08:02] <lincolnthree> well
[21:08:05] <lincolnthree> i'll ignore for now
[21:08:06] <lincolnthree> no time for that
[21:08:26] <jamezp_afk> Sure. I'll grab some lunch and take a look after if you'd like me to.
[21:08:56] <lincolnthree> jamezp_afk: it looks like kenfinniganis working on it, but that would be great! no rush
[21:09:01] <lincolnthree> i don't need to use bleeding edge in what I'm doing
[21:09:22] <jamezp_afk> I'll take a quick look in a few then :-)
[21:09:26] <lincolnthree> k!
[21:09:57] <maschmid> lincolnthree, re SOLDER-119, add "Dependencies: org.jboss.logging,org.jboss.logmanager" to any manifest in war...
[21:09:58] <jbossbot> jira [SOLDER-119] CNFE org.jboss.logmanager.Logger$AttachmentKey on AS7 [Open (Unresolved) Bug, Blocker, Ken Finnigan] https://issues.jboss.org/browse/SOLDER-119
[21:10:18] <ssachtleben> lincolnthree could I possibly override the rewrite handler and append request.getHeader("x-forwarded-host") on the redirect ? :D
[21:10:21] <lincolnthree> ah. interesting
[21:10:42] <lincolnthree> thanks maschmid
[21:14:07] <maschmid> lincolnthree, forgot to mentiton, it is already fixed in solder... https://github.com/seam/solder/blob/ae39ed7a1385147ad5efb1ba507c7c819a4edbf9/impl/pom.xml#L166
[21:14:20] <lincolnthree> maschmid: ah ok, so jamezp_afk, don't worry about it !
[21:20:33] *** mateus has joined #seam-dev
[21:34:57] *** maschmid has quit IRC
[21:35:28] *** maschmid has joined #seam-dev
[21:38:22] <ssachtleben> OMG FIXED !!!
[21:38:41] <ssachtleben> lincolnthree sorry for blaming prettyfaces ;)
[21:38:51] <lincolnthree> ssachtleben: WOOT! what was it!!
[21:38:52] <lincolnthree> np!
[21:39:12] <ssachtleben> ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On -> ProxyPass * balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On
[21:39:24] <ssachtleben> ProxyPassReverse / balancer://mycluster/ -> ProxyPassReverse * balancer://mycluster/
[21:39:38] <lincolnthree> AH
[21:39:39] <lincolnthree> nice
[21:39:43] <ssachtleben> not sure why * dont make double slashes but now everything seems to work fine
[21:39:46] <lincolnthree> You should post that on the forums
[21:39:51] <ssachtleben> yeah I do :)
[21:39:52] <lincolnthree> on jboss and ocpsoft
[21:39:55] <lincolnthree> sweet!
[21:39:57] <lincolnthree> nice job :)
[21:40:38] <ssachtleben> modcluster docu says / but found some other examples with * :)
[21:41:42] <lincolnthree> might want to file an issue against ModCluster for that
[21:41:46] <lincolnthree> sounds like a bug
[21:41:49] <lincolnthree> either in docs or system itself
[21:46:54] <ssachtleben> yeah I just wait for some response on my solution maybe there is still a trick or something :D
[21:47:17] <ssachtleben> woot I can switch later finally to as7
[21:47:58] *** gastaldi has joined #seam-dev
[21:48:09] <gastaldi> yo all
[21:48:23] <lincolnthree> ssachtleben: well good thing you figured it out :)
[21:48:28] <lincolnthree> btw ssachtleben
[21:48:30] <lincolnthree> if you want to blow your mind
[21:48:35] <lincolnthree> http://ocpsoft.com/rewrite/
[21:48:55] <ssachtleben> lincolnthree that will be the next :D I have already included snapshot to my project :)
[21:49:46] <ssachtleben> My phase listener detects already which domain is mapped to which locale and fire locale change event
[21:49:55] <maschmid> gastaldi: yo to you too!
[21:50:12] <ssachtleben> just need to setup these locale depending rewrite configuration rules :D
[21:50:16] <gastaldi> :)
[21:52:46] *** jganoff has quit IRC
[21:53:26] <lincolnthree> sweet :)
[21:55:12] *** rmartinelli has quit IRC
[21:55:24] <ssachtleben> and I really appreciate your help on that slash problem :)
[21:55:59] <lincolnthree> you're welcome :)
[21:58:09] *** tsurdilo has quit IRC
[21:58:31] *** tsurdilo has joined #seam-dev
[22:01:42] *** mbg|wfh has joined #seam-dev
[22:04:01] <gastaldi> sbryzak: You there ?
[22:04:11] <gastaldi> If you are awake :P
[22:04:46] <gastaldi> hum, timezones should never exist. :)
[22:07:04] *** mbg has quit IRC
[22:07:14] <clerum> some people don't like working in the dark
[22:07:21] <gastaldi> yeah :)
[22:07:27] <clerum> 1/2 the world would be very pale
[22:07:44] <gastaldi> lincolnthree: Have you or anyone read any Adam Bien books ?
[22:07:49] *** mbg has joined #seam-dev
[22:07:52] *** jamezp_afk is now known as jamezp
[22:08:09] <lightguard_jp> gastaldi: I follow him on twitter and have read his blog posts. Does that count?
[22:08:17] <maschmid> http://transcripts.jboss.org/channel/irc.freenode.org/%23seam-dev/2011/index.html stopped recording a few days ago... the echelog.matzon.dk logs are OK...
[22:08:21] <gastaldi> :) not at all
[22:08:27] <gastaldi> maschmid: I noticed that too
[22:08:44] <lightguard_jp> maschmid: Yeah, our bot isn't here.
[22:09:00] <gastaldi> hum, where is the missing bot ?
[22:10:32] <jamezp> maschmid: I didn't really do anything with the Solder logging, but I'm not sure that's the fix we want.
[22:11:10] <jamezp> maschmid: Only saying that because we had to change to logging tooling to not have any dependencies on JBoss Logging.
[22:12:17] 
[22:12:42] <jamezp> JBoss Logging > slf4j :-)
[22:12:52] 
[22:13:13] <jamezp> We have i18n capabilities and vararg logger methods.
[22:13:13] <gastaldi> so, why not use JBoss Logging directly ?
[22:13:33] 
[22:13:47] <gastaldi> Classpath issues ?
[22:13:59] <jamezp> I think it was they (IIRC Ken and Dan) didn't want any more dependencies for Solder.
[22:14:07] <gastaldi> ah
[22:14:09] <gastaldi> Makes sense
[22:14:20] <maschmid> jamezp: Well, I agree that it is more a hack than a fix...
[22:14:31] <jamezp> Trust me I went through a huge refactor to make that happen :-)
[22:14:36] <gastaldi> lol
[22:14:53] <jamezp> maschmid: No problem. I was just noticing it is all.
[22:15:06] <gastaldi> we should have sonar running to detect stuff like that
[22:15:27] <gastaldi> Or anything similar
[22:16:02] <gastaldi> How cool would that be ?
[22:17:15] *** nilian has quit IRC
[22:19:18] *** nilian has joined #seam-dev
[22:19:28] <gastaldi> or not :P
[22:19:39] *** kevinpollet has quit IRC
[22:22:16] <jamezp> I've never used sonar, so sure it would be cool ;-)
[22:29:22] *** nilian has quit IRC
[22:29:50] <jose_freitas> sonar is the one tool to rule them all
[22:30:03] <gastaldi> jose_freitas: Agreed
[22:31:56] <jose_freitas> hey bleathem
[22:31:59] <jose_freitas> how you doing?
[22:32:49] <jose_freitas> any veridict on toodledo vs todoist/
[22:33:36] <jose_freitas> btw gastaldi: I tried evernote, and it's pretty cool, I'll use not to organize tasks but to take notes on links, videos and etc :)
[22:33:47] <gastaldi> nice huh ?
[22:34:21] <jose_freitas> yeap
[22:51:43] <jbossbot> git [parent] push master df9aab2.. Marek Schmidt fixes for jbossas-managed-7 and weld-ee-embedded-1.1, update weld version
[22:51:43] <jbossbot> git [parent] push master 00d8e70.. Shane Bryzak Merge pull request #3 from maschmid/arq-upgrade-cr4...
[22:51:43] <jbossbot> git [parent] push master URL: http://github.com/seam/parent/compare/f59c212...00d8e70
[22:51:57] <gastaldi> 5 min left for our regular meeting
[22:52:03] <lightguard_jp> sbryzak: You're up early.
[22:52:40] <sbryzak> i know, meeting in 10 mins though ;)
[22:53:06] *** edburns is now known as edburns_away
[22:53:13] <lightguard_jp> Yep
[22:53:31] <lightguard_jp> I don't think our bot will be in place by then.
[22:53:46] <gastaldi> :(
[22:53:50] <lightguard_jp> I'll have to send the logs over to Max to run it manually.
[22:54:27] 
[22:54:31] <gastaldi> :)
[22:54:39] <lightguard_jp> lol
[22:56:02] <lightguard_jp> Was hoping Rodney would be here too.
[22:56:06] <lightguard_jp> Perhaps not
[22:56:14] <gastaldi> rruss ?
[22:56:19] <gastaldi> your manager ?
[22:56:19] <lightguard_jp> Yeah
[22:56:21] <gastaldi> ;)
[22:56:42] 
[22:56:52] *** rruss has joined #seam-dev
[22:56:54] <lightguard_jp> I want a credit card this time ;)
[22:56:57] <lightguard_jp> Oh, and there he is
[22:57:02] <lightguard_jp> rruss: Were you ears burning?
[22:57:07] <gastaldi> lol
[22:57:13] <rruss> yup
[22:57:14] <rruss> :)
[22:57:27] <lincolnthree> he's on fire!
[22:57:34] <lincolnthree> is it the shoes!?
[22:57:45] <gastaldi> hahaha ! Boom shaka-laka
[22:58:08] <gastaldi> NBA Jam rules
[22:58:50] 
[22:58:57] <gastaldi> :)
[22:59:46] <gastaldi> In the red corner, lightguard_jp
[23:00:33] <gastaldi> damn, I need to stop watching UFC :P
[23:02:28] <gastaldi> hey, the DWG meeting is scheduled for tomorrow right ?
[23:02:38] <gastaldi> Will it be on IRC or TeamSpeak ?
[23:03:00] <lightguard_jp> Good question
[23:03:30] <gastaldi> Who do we call ?
[23:04:02] <lightguard_jp> Ken
[23:04:10] *** kenfinnigan has joined #seam-dev
[23:04:18] <lightguard_jp> We'll start.
[23:04:22] <gastaldi> wow lightguard_jp, say the lotto numbers for me
[23:04:37] <gastaldi> Everytime you say, people appear
[23:04:50] <lightguard_jp> 4 3 8 5 1
[23:04:53] 
[23:04:54] <gastaldi> :D
[23:05:06] *** ChanServ sets mode: +o lightguard_jp
[23:05:12] <lightguard_jp> #startmeeting
[23:05:18] <lightguard_jp> Welcome everyone!
[23:05:30] <lightguard_jp> I hope we have some good discussion again this week
[23:05:30] <gastaldi> :( No meeting bot
[23:05:42] <lightguard_jp> no, but I'll send the logs to Max and he can put them up for us.
[23:06:14] <lightguard_jp> The first item we have is Beta2
[23:06:17] <lightguard_jp> #topic Beta2
[23:06:33] <lightguard_jp> I think most of you know 3.1.0.Beta1 was a bit of a flop :)
[23:06:44] <gastaldi> It never existed anyway
[23:06:46] <gastaldi> :)
[23:06:50] <lightguard_jp> #info 3.1.0.Beta1 will not be a public beta, internal only.
[23:07:00] <lightguard_jp> #info we're moving forward with 3.1.0.Beta2
[23:07:20] <lightguard_jp> I believe most of the modules have been updated and released
[23:07:24] <lightguard_jp> sbryzak: correct?
[23:07:32] <sbryzak> most of them, yes
[23:07:36] <sbryzak> we have about 5 to go
[23:07:42] <sbryzak> jcr, jms, rest, security and faces
[23:07:55] <sbryzak> hmm, qa guys must all be in bed now
[23:08:01] <lightguard_jp> #info jcr, jms, rest, security and faces need to be released for 3.1.0.Beta2
[23:08:12] <maschmid> I am on a sofa
[23:08:30] <sbryzak> maschmid: ah cool, you're here ;)
[23:08:42] <sbryzak> so i'll get the remaining modules released today
[23:08:55] <lightguard_jp> If there are people that can help with the 3.1.0.Beta2 releases we'd welcome the help.
[23:08:58] <sbryzak> and hopefully the qa team will be able to test the release over the next week
[23:09:13] <sbryzak> what i'd like everyone to do is test their own modules
[23:09:22] <sbryzak> deploy all their own examples, and ensure they run on as7
[23:09:40] <sbryzak> also, if everyone could please review their documentation
[23:09:57] <sbryzak> if there's been any new chapters added, we need to manually add them to the bundled seam distribution
[23:10:07] <sbryzak> it's unfortunate, but it's because maven sucks
[23:10:18] <gastaldi> Blasphemy !
[23:10:45] <sbryzak> so i think what we'll do, is test the beta2 release over the next 2 weeks
[23:10:49] <lightguard_jp> #info either let lightguard_jp or sbryzak know about new doc chapters or create a pull request for the build module.
[23:10:56] <maschmid> sbryzak: SOLDER-119 is still not fixed propely in beta2 (it is now in the latest solder commit)
[23:10:57] *** johnament has joined #seam-dev
[23:10:57] <jbossbot> jira [SOLDER-119] CNFE org.jboss.logmanager.Logger$AttachmentKey on AS7 [Resolved (Done) Bug, Blocker, Ken Finnigan] https://issues.jboss.org/browse/SOLDER-119
[23:11:00] <sbryzak> fix as many issues as we find, and then we'll release CR1
[23:11:11] <sbryzak> it would be nice to sort out the test suite structure by then
[23:11:13] <johnament> so cr1 is the next version?
[23:11:20] <sbryzak> yep, CR1 will be next
[23:11:39] <lightguard_jp> #info 3.1.0.CR1 will be the next Seam 3 release, in a couple of weeks
[23:12:07] <sbryzak> btw, has anyone had a chance to look at the mail module?
[23:12:13] <sbryzak> i'd really like to get it ready for CR1
[23:12:36] <sbryzak> i'll take that as a no ;)
[23:12:37] <lightguard_jp> #info if any of the leads would like us to go through their documentation, let sbryzak or lightguard_jp know and we'll help out, or give some suggestions for improvements.
[23:12:43] <johnament> sbryzak: so no release this weekend?
[23:13:01] <sbryzak> johnament: beta2 release should be finished today
[23:13:08] <johnament> oh, ok.
[23:13:10] <johnament> no test changes.
[23:13:11] <lightguard_jp> sbryzak: I did some work to get it working on the testsuite structure, not 100% there though.
[23:13:15] <sbryzak> johnament: did you have a chance to look at the jms and jcr modules?
[23:13:16] <gastaldi> lightguard_jp: Reports needs some documentation
[23:13:43] 
[23:14:07] <lightguard_jp> clerum: Would try running your example on AS7 for mail?
[23:14:07] <johnament> sbryzak: jcr's done, was going to clean up jms tonight
[23:14:08] <sbryzak> gastaldi: can you write some basic documentation on how to use it?
[23:14:39] <lightguard_jp> gastaldi: If you have some time to at least write an outline or basics we can help flesh it out.
[23:14:42] <sbryzak> gastaldi: even if it's just some rough notes, jason or i can do some editing
[23:15:01] <clerum> ?
[23:15:07] *** mbg|wfh has quit IRC
[23:15:12] 
[23:15:24] <lightguard_jp> clerum: Run your mail example on AS7 to verify everything works, unless that's been done already.
[23:15:45] <clerum> lightguard_jp: as far as I know mail is still broken with reguards to tests
[23:15:52] <lightguard_jp> gastaldi: Okay, how about a quick write up of the features, or even a small bullet list
[23:15:57] <clerum> I was waiting for someone to resolve that
[23:16:13] <lightguard_jp> clerum: Yes, the tests are broken still. We're wondering if the example runs.
[23:16:24] <sbryzak> clerum: i should be able to take a look at the tests later today
[23:16:25] <johnament> mvn clean install -DskipTests=true
[23:16:31] <gastaldi> lightguard_jp: I try to dig into it. The seamframework.org page already has this
[23:16:34] <lightguard_jp> clerum: Sorry, I've been doing the getting started drafts, haven't gotten to finishing up the tests.
[23:16:43] <sbryzak> clerum: has the module restructure been done?
[23:16:53] <lightguard_jp> gastaldi: Okay, cool. We can probably take that and go with it.
[23:17:00] <clerum> no I held up on that so I could have working tests before ripping it all apart
[23:17:22] <sbryzak> ok, i'll try to have a look at it today
[23:17:31] <clerum> sounds good
[23:17:33] <lightguard_jp> sbryzak: Partly. The tests need some inclusion of jars in the sw archive.
[23:18:04] <sbryzak> lightguard_jp: dependency jars for mail?
[23:18:12] <kenfinnigan> I hope to have the solder testsuite working tonight
[23:18:14] <lightguard_jp> Yeah, pretty much.
[23:18:22] <sbryzak> np, i'll try to sort it out
[23:18:25] <lightguard_jp> sbryzak: you take mail and I'll work on the Reports docs?
[23:18:43] <sbryzak> lightguard_jp: sounds good to me
[23:18:48] <lightguard_jp> OKay
[23:18:54] <sbryzak> kenfinnigan: awesome, that was the next topic
[23:18:58] <lightguard_jp> #action lightguard_jp will work with gastaldi on the Reports docs
[23:19:05] <maschmid> kenfinnigan: regarding the solder testsuite, can you take a look at https://github.com/seam/solder/pull/41 ?
[23:19:06] <lightguard_jp> #action sbryzak will work on the mail tests
[23:19:15] <lightguard_jp> Yep
[23:19:21] <lightguard_jp> #topic Testing
[23:19:41] <lightguard_jp> We've hit some little road bumps with this :)
[23:19:50] <lightguard_jp> I think we have a few solutions and would like some feedback.
[23:19:51] <gastaldi> I suggest we use JUnit only
[23:20:01] <sbryzak> are there issues with testng?
[23:20:08] <lightguard_jp> Not that I know of.
[23:20:27] <gastaldi> sbryzak: No, but it would be nice to have one preferred framework
[23:20:28] <lightguard_jp> The only testng stuff I'm aware of are the ftests QA is doing on examples.
[23:20:49] <sbryzak> i don't have a problem standardizing on one testing framework
[23:20:53] <lightguard_jp> I think junit is our defacto standard as arquillian works best with junit at present.
[23:20:57] <gastaldi> yeah
[23:21:04] <sbryzak> as long as all modules use it
[23:21:19] <sbryzak> if everyone agrees to that, then i'll remove testng from the parent
[23:21:22] <lightguard_jp> Are there any modules using testng?
[23:21:55] <lightguard_jp> I'm doing a grep now
[23:21:55] <gastaldi> good question
[23:21:58] <sbryzak> wait a sec.. so can qa use junit for the functional tests?
[23:22:04] <sbryzak> maschmid: ^^
[23:22:24] <maschmid> well, we can, but we would have to rewrite the ftests.
[23:22:31] <gastaldi> sbryzak: You talking about selenium ?
[23:22:40] <johnament> maybe you should rewrite the ftests...
[23:22:51] <gastaldi> +1 to test rewriting :)
[23:22:51] <lightguard_jp> The only tests using testng or in the examples.
[23:22:59] <sbryzak> yeah selenium
[23:23:08] <kenfinnigan> maschmid: I will take a look, but I won't be able to merge the request as I don't have those rights
[23:23:13] <sbryzak> maschmid: how much work would it be to rewrite the tests?
[23:23:14] <lightguard_jp> maschmid: Arquillian drone works well.
[23:23:22] <sbryzak> i'm sure everyone could help with that
[23:23:46] <sbryzak> lightguard_jp: does drone support junit?
[23:23:58] <lightguard_jp> I rewrote the ones in mail in an hour or so, with having to lookup how to do it and setup.
[23:24:00] *** mateus has quit IRC
[23:24:00] <lightguard_jp> sbryzak: Yes
[23:24:10] <gastaldi> com.thoughtworks.selenium.SeleneseTestCase
[23:24:19] <sbryzak> i haven't looked at it yet.. anyone know how it compares with selenium?
[23:24:35] 
[23:24:49] <lightguard_jp> Drone and ajocado use selenium under the hood
[23:25:00] <lightguard_jp> It's another wrapper like what QA has with their wrapper.
[23:25:16] <lightguard_jp> It starts up the selenium server and everything.
[23:25:16] <maschmid> sbryzak: will have to look at it... it would make sense to rewrite them to use ajocado .. no point on doing any rewrite without that
[23:25:37] <gastaldi> yeah
[23:25:39] <lightguard_jp> https://docs.jboss.org/author/display/ARQ/Drone
[23:25:43] <lightguard_jp> Docs are a little out of date though.
[23:25:43] <sbryzak> i agree
[23:25:52] <lightguard_jp> Take a look at the mail tests in the example currently.
[23:25:54] <jose_freitas> what advantage would change example tests bring?
[23:26:05] <sbryzak> maschmid: do you think you could review it tomorrow, and give your opinion on whether it will be feasible for seam's testing requirements?
[23:26:21] <lightguard_jp> jose_freitas: It would unite all of the tests on one structure, technology set and framework.
[23:26:33] <lightguard_jp> Also shows users how to write their own
[23:26:38] <maschmid> sbryzak: sure
[23:27:06] <gastaldi> +1 to all that
[23:27:07] <jose_freitas> ok, lightguard_jp, that's a good argument
[23:27:08] <gastaldi> :)
[23:27:08] <sbryzak> great, then we'll make it a goal for CR1 to standardize on one test framework, and rewrite the ftests to use drone
[23:27:23] <lightguard_jp> maschmid: You can ping me as well for questions, of course aslak would be the go to person though :)
[23:27:28] <gastaldi> yaaay
[23:27:49] <lightguard_jp> #info great, then we'll make it a goal for CR1 to standardize on one test framework, and rewrite the ftests to use drone
[23:28:13] <lightguard_jp> sbryzak: Want to talk about the surefire question and options?
[23:28:19] <sbryzak> yes
[23:28:26] <sbryzak> i was just about to ask about that
[23:28:51] <sbryzak> so what's our current status on the testsuite structure and surefire?
[23:29:01] <sbryzak> have we made any progress?
[23:29:06] <maschmid> kenfinnigan: yes, I meant looking at it, you can just take and do whatever you want with it if you want to work on the solder testsuite...
[23:29:08] <gastaldi> kenfinnigan is the person for that ?
[23:29:21] <johnament> i converted jcr to the format you described sbryzak
[23:29:21] <lightguard_jp> sbryzak: No, not really. at least I don't think so
[23:29:25] <kenfinnigan> maschmid: ok cool, will bear those changes in mind when working on it
[23:29:34] <gastaldi> johnament: Excellent refactor on JCR
[23:29:44] <johnament> sbryzak: so far, it works pretty good, no major issues running it and reduced coding a lot in the tests.
[23:29:49] <gastaldi> Those repeated tests was really annoying
[23:29:53] <lightguard_jp> sbryzak: I think the issues we've uncovered are still outstanding.
[23:29:56] <gastaldi> were
[23:30:19] <sbryzak> so, can someone summarise the issues exactly?
[23:30:37] <lightguard_jp> I'm not sure who else has run across these or note.
[23:30:38] <lightguard_jp> not*
[23:30:42] <sbryzak> it's to do with how surefire treats dependencies right?
[23:31:01] <lightguard_jp> #info the issues I've found have to with surefire, dependencies and adding additional tests.
[23:31:15] <kenfinnigan> what are the issues?
[23:31:24] <lightguard_jp> #info surefire doesn't have a good way of adding additional tests outside of the standard maven directory structure.
[23:31:38] <sbryzak> stuartdouglas: ping
[23:31:47] <gastaldi> lightguard_jp: Have you tried using the build-helper-plugin ?
[23:31:48] *** mgoldmann has quit IRC
[23:31:55] <lightguard_jp> #info the jar up common, then explode it is a massive hack, and I think it has problems working in an IDE, at least it does with Idea, don't know about eclipse.
[23:32:03] *** mgoldmann has joined #seam-dev
[23:32:06] <gastaldi> http://mojo.codehaus.org/build-helper-maven-plugin/usage.html
[23:32:21] <sbryzak> we seem to have multiple container support in the persistence tests
[23:32:25] <kenfinnigan> i've been meaning to test it with eclipse to see if the tests can work with that hack, but I suspect they won't
[23:32:28] <lightguard_jp> gastaldi: The problem is still the same, unless you're going to copy the source each time before the source is compiled.
[23:32:30] <johnament> lightguard_jp: why are you making it so complicated?
[23:32:32] <sbryzak> i'd like to ask stuart how he did them
[23:32:33] <lightguard_jp> It's nasty
[23:32:34] *** dabloem has quit IRC
[23:32:51] <lightguard_jp> sbryzak: He subclassed each test
[23:33:05] <johnament> lightguard_jp: why not make it src/test/some-container-specific for container specific tests?
[23:33:16] <lightguard_jp> that's one way to do it, but it creates a lot of unneeded code and classes.
[23:33:24] <lightguard_jp> Also makes maintaining the tests a headach.
[23:33:26] <sbryzak> ah, yeah too much code
[23:33:27] <lightguard_jp> headache*
[23:33:46] <stuartdouglas> hi guys
[23:33:49] <stuartdouglas> you pinged?
[23:33:51] <gastaldi> hey stuartdouglas
[23:33:53] <sbryzak> hey stuart
[23:34:07] <sbryzak> was just going to ask how you setup the tests in the persistence module, but lightguard_jp already answered ;)
[23:34:08] <lightguard_jp> johnament: The problem is getting the common stuff in there easily. As the common area would contain tests to run on each container.
[23:34:36] <johnament> lightguard_jp: src/test/java ?
[23:34:36] <lightguard_jp> sbryzak: What were our ideas again?
[23:34:45] <sbryzak> so just to crystalize our goal here.. we want to be able to simply provide a pom that imports the container bom, and executes the base tests in that container
[23:34:48] <kenfinnigan> can we not change the default maven test directories to include the local tests but then also others?
[23:34:49] <sbryzak> without requiring any additional code
[23:35:00] <lightguard_jp> johnament: You'd have to copy it from common before compilation, which maven doesn't support.
[23:35:03] <sbryzak> with the option of adding container-specific test classes
[23:35:06] 
[23:35:08] <sbryzak> does that sum it up?
[23:35:18] <johnament> lightguard_jp: wouldn't src/test/java be common?
[23:35:29] <lightguard_jp> sbryzak: We may also have additional specific container tests to run as well besides the basic ones.
[23:35:33] <lightguard_jp> That's where things get tricky.
[23:35:33] <sbryzak> gastaldi: i believe there's a surefire issue
[23:35:46] <sbryzak> lightguard_jp: that's what i said ;)
[23:35:55] <johnament> sbryzak: not if the base cases are all in src/test/java
[23:36:00] 
[23:36:05] <lightguard_jp> sbryzak: Right, too much text flying by while I'm typing :)
[23:36:17] <lightguard_jp> johnament: but s/t/j where?
[23:36:34] <lightguard_jp> Each container is it's own module to side step classpath issues.
[23:36:44] <sbryzak> we need to spend some more time testing the multi-profile idea
[23:36:58] <sbryzak> i'd like to know if we can come up with a workaround
[23:37:05] <lightguard_jp> sbryzak: the multi-profile idea that aslak presented requires a patch to surefire.
[23:37:08] <sbryzak> the alternative of course is to hack the surefire plugin
[23:37:09] <kenfinnigan> could we have src/test/java in a container module, and then also add ../../base/src/test/java to the test source path?
[23:37:33] <lightguard_jp> kenfinnigan: surefire can only handle one test source path
[23:37:44] <kenfinnigan> hmmm
[23:38:02] <sbryzak> did someone already ask if we can just copy the test source?
[23:38:08] <sbryzak> for base tests i mean
[23:38:12] <kenfinnigan> what about using a copy plugin to create a new test directory that merges them?
[23:38:27] <sbryzak> that's what i was thinking.. the base module doesn't even need to be a maven project then
[23:38:30] <sbryzak> it can just be a directory
[23:38:31] <kenfinnigan> that is somewhere that doesn't result in them being committed
[23:38:41] <johnament> lightguard_jp: we tried multi-module.  I have everything in one module, works fine for me.
[23:38:47] <sbryzak> kenfinnigan: in the target dir would work
[23:38:52] <kenfinnigan> yeah
[23:38:56] 
[23:38:59] <lightguard_jp> johnament: Running multiple containers?
[23:39:04] <johnament> lightguard_jp: yes
[23:39:09] <lightguard_jp> in one maven pass?
[23:39:13] <johnament> lightguard_jp: no
[23:39:24] <lightguard_jp> johnament: I think that's what we're hoping for.
[23:39:26] <bleathem> lightguard_jp: did you ping?
[23:39:35] <johnament> lightguard_jp: that would be a bit much...
[23:39:39] <lightguard_jp> bleathem: while ago, had a forum message for you to look at.
[23:39:49] <lightguard_jp> johnament: That helps keep release simple.
[23:40:08] <lightguard_jp> And helps us test in multiple containers to test portability for a release.
[23:40:27] <johnament> lightguard_jp: that sounds more like a QA thing rather than a build sanity thing
[23:40:30] <lightguard_jp> Running tests in 5 different runs for example is a bit much, imo
[23:40:30] <gastaldi> http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing
[23:40:30] <sbryzak> i would rather have the different containers run separately
[23:40:31] <maschmid> lightguard_jp: we use lot of shell scripts anyway in jenkins, so that wouldn't be a problem...
[23:40:41] <kenfinnigan> the surefire plugin only working with a single test dir, is that a single source or compile dir?
[23:40:41] <sbryzak> it should be a manual choice for the user
[23:40:49] <johnament> sbryzak: that was my take
[23:40:55] <lightguard_jp> kenfinnigan: both
[23:41:07] <johnament> sbryzak: for example, by default seam jcr runs weld + modeshape
[23:41:16] <kenfinnigan> how can that be, does surefire compile the test code?  didn't think it did
[23:41:21] <sbryzak> johnament: yep, weld embedded should be the default
[23:41:24] <johnament> sbryzak: but you can pick options for jackrabbit, and i'm going to add in owb
[23:41:28] <sbryzak> then you can manually run the other containers if you like
[23:41:36] <sbryzak> and jenkins will be set up with separate jobs to run them all
[23:41:40] <lightguard_jp> kenfinnigan: I haven't looked at all of the code, just enough to see it doesn't do what I was hoping it would.
[23:41:52] <johnament> sbryzak: that was what I thought was going to happen, sounds like lightguard_jp had a different take
[23:42:11] <johnament> sbryzak: maybe i'll take an a/i to poll the team to see which they prefer?
[23:42:18] <gastaldi> What if we fork the surefire plugin ?
[23:42:25] <gastaldi> And do what we need ?
[23:42:28] <lightguard_jp> gastaldi: that's a possibility.
[23:42:43] <sbryzak> johnament: i'd rather we discuss it here and reach an agreement ;)
[23:42:46] <gastaldi> How hard would that be ?
[23:42:50] <johnament> ok
[23:42:56] <johnament> but i have to run now :-)
[23:42:58] <kenfinnigan> i'd want to steer away from that if possible, as then everyone wanting to use the same test structure would need to patch their plugin to use it
[23:43:10] <lightguard_jp> johnament: Thanks for attending, glad to have you at the meetings again :)
[23:43:14] <johnament> my vote is default container
[23:43:22] <sbryzak> johnament: your vote is counted ;)
[23:43:35] *** johnament has quit IRC
[23:43:44] <sbryzak> lightguard_jp: what was the alternative idea?
[23:43:59] <lightguard_jp> sbryzak: To patching surefire?
[23:44:16] <sbryzak> to using weld embedded as the default container
[23:44:24] <gastaldi> lightguard_jp: It may be released under a different groupId / artifactId
[23:44:25] <sbryzak> and manually running the tests for other containers
[23:44:27] <lightguard_jp> gradle for the testsuite was on the table for a short time :)
[23:44:50] <kenfinnigan> i think if we want to be sure that all our modules run in AS7, that needs to be the default container
[23:45:04] <gastaldi> +1 to AS7
[23:45:09] <sbryzak> kenfinnigan: that's a good point actually
[23:45:35] <sbryzak> it's a big download hit though for someone who downloads a module's source and tries to build it
[23:45:39] <maschmid> it doesn't matter which is default, we will have jenkins jobs for AS7 in either case
[23:45:50] <lightguard_jp> sbryzak: That would work, we'll have to do some setup in Jenkins to get it to work, and have some process in place for not releasing or at the very least notifying if something is broken on one container. We've taken a beating already for incompat, I'd rather not go through it again.
[23:46:09] <kenfinnigan> maschmid: true, but my concern is more around a developer making changes to the module and not remembering to run the AS7 container
[23:46:15] <gastaldi> what if we setup an Ant script for that ? :P
[23:46:20] <kenfinnigan> this means you don't know it's broken until the CI job runs
[23:46:23] <sbryzak> lightguard_jp: that would be my preference, and it kind of brings us to the next topic of jenkins
[23:46:46] <sbryzak> kenfinnigan: jenkins will let them know if they broke something
[23:46:53] <lightguard_jp> I'd like to keep the feedback loop as tight as possible.
[23:47:08] <lightguard_jp> sbryzak: Do we run each testsuite on every commit?
[23:47:12] <kenfinnigan> true, but i always prefer ensuring those tests are run before the code is even committed
[23:47:15] <sbryzak> lightguard_jp: i believe we do
[23:47:18] <lightguard_jp> Or at midnight?
[23:47:29] <lightguard_jp> I'm with Ken
[23:47:39] <sbryzak> kenfinnigan: i like the principle of the idea, but it might not be practical
[23:47:49] <maschmid> CI jobs are generally checking in 15 minutes intervals for commits I think
[23:47:53] <gastaldi> yeah, tests may take too much time to run
[23:47:59] <lightguard_jp> sbryzak: All depends on what deem as not maintainable.
[23:48:07] <sbryzak> 15 minutes is good
[23:48:11] <lightguard_jp> If we're open to forking surefire for it, then it's not really a problem.
[23:48:25] <gastaldi> cool
[23:48:31] 
[23:48:34] <gastaldi> :)
[23:48:43] <gastaldi> Case solved
[23:48:46] <sbryzak> we're not going to be able to run the testsuite for all containers before every commit
[23:48:57] <gastaldi> https://github.com/apache/maven-surefire
[23:49:10] <sbryzak> so we really need to depend on jenkins to let us know when we've broken something
[23:49:19] <kenfinnigan> sbryzak: agree with that, but if we're saying we support AS7 without any changes or fixes, then I feel we need to be testing that every time
[23:49:31] <lightguard_jp> sbryzak: We could setup a matrix setup in jenkins to run the suite in parallel
[23:49:51] <lightguard_jp> That would run quickly and get back to what John was thinking we'd do.
[23:50:02] <lightguard_jp> kenfinnigan: +1
[23:50:09] <sbryzak> kenfinnigan: if we have jenkins run every 15 minutes though, then we'll know pretty shortly after we commit if we've broken something
[23:50:21] <lightguard_jp> I feel we should be doing embedded weld and AS7 at least.
[23:50:30] <sbryzak> and it's not like the snapshots need to be stable
[23:50:36] <lightguard_jp> Once the embedded OWB container works we could do that as well.
[23:50:40] <lightguard_jp> The embedded tests run quickly.
[23:51:10] <sbryzak> yeah but i'm thinking of the barrier for new developers who might want to download a module just to play with it
[23:51:31] <gastaldi> sbryzak: Maven will download the entire internet anyway
[23:51:35] <lightguard_jp> We could setup sandbox rules
[23:51:41] <kenfinnigan> agree with all the comments
[23:51:43] <sbryzak> yeah but as7 will double the size of that download
[23:51:47] <maschmid> kenfinnigan: we still have a QA process, no need to make all the snapshots work at all times everywhere....
[23:51:51] <lightguard_jp> run with embedded weld or whatever, then when it graduates we can beef up the test suite.
[23:51:53] <kenfinnigan> but as a lot of modules are maintained/lead by the community
[23:52:06] <gastaldi> sbryzak: Yeah, just once
[23:52:09] <kenfinnigan> not everyone would be able to go back in to fix a container test error immediately after a CI job
[23:52:33] <sbryzak> i think the goal should be to run the tests in the most lightweight container we have
[23:52:37] <sbryzak> which would be embedded weld
[23:52:42] <kenfinnigan> and it's not a good intro to a module for the first time to take your first fork, build it and have it fail on AS7
[23:52:45] <sbryzak> that will uncover any immediate test issues
[23:53:10] <lightguard_jp> Yeah, running on embedded weld should uncover 90% of issues
[23:53:31] <lightguard_jp> It's also not that difficult to setup.
[23:53:33] <sbryzak> kenfinnigan: i think there's a very slim chance of that happening
[23:53:38] <maschmid> kenfinnigan: don't worry, if you break AS7 support of some module, I am going after you :)
[23:54:31] <sbryzak> and while our goal is to build for as7 by default, we should really work in any container
[23:54:38] <kenfinnigan> if everyone else if happy with that, that's fine
[23:54:46] <lightguard_jp> Sounds like we're at the run on embedded weld and AS7 for modules and have them in different testing modules?
[23:54:47] <gastaldi> fine for me
[23:54:51] <kenfinnigan> I just felt that if we could be stricter about what breaks, then why not
[23:54:51] <sbryzak> so a glassfish user can download a module and use it in glassfish
[23:55:18] <sbryzak> i totally agree with your points
[23:55:25] <sbryzak> but we need to keep the development process lightweight
[23:55:52] <sbryzak> it just means we need to use jenkins more judiciously
[23:56:10] <lightguard_jp> I think having a sandbox / incubator idea which only focuses on embedded weld then it's beefed up once it graduates is great idea.
[23:56:24] <sbryzak> lightguard_jp: should we move on to the jenkins topic?
[23:56:24] <lightguard_jp> Of course having jenkins run everything besides embedded containers would work too.
[23:56:39] <lightguard_jp> Do we have a resolution we can log for this?
[23:56:50] <lightguard_jp> #chair sbryzak
[23:57:08] <lightguard_jp> sbryzak: If you think we do, add an #agree message
[23:57:18] <sbryzak> well, imho we should use weld embedded as the default test container, and then have jenkins run the tests on all other containers
[23:57:19] <gastaldi> Jenkins should release modules too instead of having being done manually  (but the plugin is missing in cloudbees)
[23:57:35] <maschmid> sbryzak: agreed
[23:57:42] <lightguard_jp> gastaldi: down boy, we're not there yet.
[23:57:45] <lightguard_jp> ;)
[23:57:46] <sbryzak> that way we pick up most of the test issues immediately, and jenkins notifies us of any container-specific issues shortly after
[23:57:48] <gastaldi> lightguard_jp: Sorry :)
[23:57:51] <kenfinnigan> gastaldi: really?  I thought I saw something in the config that would do it?
[23:58:08] 
[23:58:13] <kenfinnigan> ah ok
[23:58:19] <sbryzak> we also have the option to run the as7 tests manually before we commit
[23:58:22] <lightguard_jp> Okay, I think we've reached our decision.
[23:58:27] <lincolnthree> gastaldi: you can have jenkins do releases
[23:58:33] <gastaldi> lincolnthree: I know
[23:58:36] <sbryzak> so as a matter of discipline we should probably start forcing ourselves to do that
[23:58:39] <gastaldi> lincolnthree: But not on cloudbees
[23:58:42] <lincolnthree> gastaldi: it's not a paid version option.
[23:58:43] <lincolnthree> oh
[23:58:44] <lincolnthree> okay
[23:58:47] <lincolnthree> that might be the case
[23:58:52] <lightguard_jp> #agreed embedded weld will be the default test environment for modules and AS7 will run by jenkins jobs. Of course users can run AS7 tests on their own as well.
[23:59:05] <sbryzak> lightguard_jp: that sums it up nicely
[23:59:19] <sbryzak> so.. jenkins on cloudbees
[23:59:19] <gastaldi> lincolnthree: Is that what you mean ?
[23:59:22] <lightguard_jp> Great, let's move on then, we have a couple left
[23:59:29] <lightguard_jp> #topic jenkins on cloudbees.
[23:59:35] <kenfinnigan> just for clarification, will the weld-embedded tests still be in the testsuite module?
[23:59:42] <sbryzak> apparently we have the go-ahead to get a paid instance
[23:59:55] <gastaldi> Why not placing it under OpenShift ?
[23:59:56] <lightguard_jp> Yes, I need to get some info from rruss
[23:59:59] <sbryzak> kenfinnigan: yes
[23:59:59] <lightguard_jp> Then we can move forward

top