August 17, 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
August 17, 2011 [00:00:06] <sbryzak> someone else might have a better idea ;) [00:00:22] <clerum> I have the staging repo set in my settings.xml but mvn only appears to be checking https://repository.jboss.org/nexus/content/groups/public-jboss/) [00:00:40] <hannelita> I really think ppl need more info abut seam [00:00:44] <clerum> it sthat because it is defined in my pom? [00:02:02] <sbryzak> hannelita: what if we had a weekly interactive irc session that focussed on one particular subject? [00:02:10] <sbryzak> clerum: i'm not sure.. best to just build it locally [00:02:15] <clerum> I did [00:02:21] <sbryzak> clerum: did you checkout 3.1.0.Beta1? [00:02:26] <clerum> yes [00:02:28] <sbryzak> otherwise you'll be building a snapshot [00:02:35] <clerum> then it complained about Solder 3.1.0.Beta1 [00:02:45] <clerum> so I checked that out and built it but I get build fail [00:02:47] <clerum> test failures [00:02:48] <sbryzak> the bom complained about solder? [00:02:58] <sbryzak> ah, yeah skip the tests [00:03:05] <sbryzak> most of the modules have broken tests at the moment [00:03:16] <sbryzak> we're going to make fixing them a priority for CR1 [00:03:16] <hannelita> sbryzak: Would be goo to... or more webinars [00:03:34] <hannelita> sbryzak: *good [00:03:40] <sbryzak> webinars are good, but they're not interactive... irc would give you the opportunity to ask questions [00:03:48] <clerum> mvn clean install -DskipTests ? [00:03:52] <clerum> I'm super new to mvn [00:03:55] <hannelita> sbryzak: True [00:04:17] <sbryzak> and much easier to link to code snippets etc on irc [00:05:06] <lightguard_jp> I'd like to do more irc stuff like that, but we always end up getting the same people. [00:05:18] <hannelita> sbryzak: I mean, my experience with blog shws me that ppl want "for dummies" tutorials [00:05:31] <hannelita> (or screencasts) [00:06:04] <lightguard_jp> hannelita: Since you have a fair amount of people following you and asking questions, would you ask around and see what people think about that idea? [00:06:07] <sbryzak> hannelita: i agree, and i hope we have a lot of that sort of content on seam univeristy when it comes online [00:06:22] <lightguard_jp> hannelita: Do you have that pull request for confbuzz? [00:06:36] *** aslak has quit IRC [00:06:46] <hannelita> for example, ppl look at the examples on github and say "OMG, WTF IS IDENTITYOBJECT??". No jokes, ppl dont understand that easily [00:07:10] <sbryzak> hmm, interesting point [00:07:45] <sbryzak> ok, i can see how we might take for granted that our users have a certain level of understanding [00:07:49] <hannelita> lightguard_jp: I'm at work now, I will pull request you when I get home ;) did some sign up features and a speaker profile [00:08:44] <hannelita> sbryzak lightguard_jp I've been trying to write the tutorials on my blog according to ppl ask me to do [00:08:59] <hannelita> "easy-reading" stuff, explaining step by step [00:09:25] *** josefreitas_aw has joined #seam-dev [00:09:49] <hannelita> this was a good experience I got from Ruby community - they explain everything step by step. Thats pretty good and community is happy with that :) [00:10:45] <clerum> problem with not getting the staging repo to works is I have to clone and build all the dep modules [00:10:48] <sbryzak> i think we need more of that kind of tutorial for seam [00:11:33] <sbryzak> in fact, that's one of the points our doc guys make, to provide simple, step by step "how to"s for our products [00:12:30] <clerum> I have a great salesforce.com type example project that I'm developing that fills in a lot of holes [00:12:57] <lightguard_jp> clerum: Is it open? [00:13:06] <clerum> shortly [00:13:12] <lightguard_jp> Perfect [00:13:28] <clerum> might be nice have running on openshift or something [00:13:45] <lightguard_jp> You should be able to get it to run on express [00:13:46] <clerum> seam + hibernate (search) + richfaces [00:14:18] <clerum> booking is great but it's very flow driven [00:15:21] <clerum> more importantly I want to get it out there to expose some issues we don't see developing the modules [00:17:39] <hannelita> I need 72-hour-days :P, so then I will be able to code new examples (like the call4all) and write tutorials (for dummies series) [00:19:22] <clerum> any hits on a failing selinium test [00:19:22] <clerum> https://gist.github.com/b21229740edad267d0b5 [00:19:28] <clerum> looks like a config issue [00:21:33] <lightguard_jp> clerum: What's the source of that test? [00:22:20] <clerum> https://github.com/codylerum/mail/blob/develop/examples/sendmail/src/test/java/org/jboss/seam/mail/examples/sendmail/ftest/SeleniumMailTest.java\ [00:22:25] <clerum> https://github.com/codylerum/mail/blob/develop/examples/sendmail/src/test/java/org/jboss/seam/mail/examples/sendmail/ftest/SeleniumMailTest.java [00:24:23] <lightguard_jp> Yeah, I'd say a setup issue. [00:24:41] <lightguard_jp> If you look at the basic servlet example you might find something there. [00:26:12] <lightguard_jp> https://github.com/seam/examples/blob/master/catch-basic-servlet/src/test/resources/ftests.xml [00:26:51] *** josefreitas_aw has quit IRC [00:27:12] <clerum> yeah it has that too [00:27:50] <lightguard_jp> you're deploying a webapp? [00:27:57] <clerum> more importantly it looks like my mvn test -Pjbossas-remote-6 isn't working at all [00:29:27] <clerum> no tests even attempt to run [00:31:31] <lightguard_jp> errors? exceptions? [00:31:41] <clerum> Running TestSuite [00:31:41] <clerum> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.291 sec [00:31:50] <lightguard_jp> hm [00:32:29] <lightguard_jp> TestNG tests? [00:33:31] <clerum> arquillian [00:34:22] <lightguard_jp> Right, but are you using testng or junit for the tests? [00:34:41] <clerum> junit [00:35:01] <lightguard_jp> That's very strange it's not picking up tests. [00:35:24] <lightguard_jp> Which module?= [00:35:30] <clerum> mail [00:35:46] <clerum> how can I check out a specific commit point? [00:35:57] <lightguard_jp> hehe, sorry, which sub directory of mail? [00:36:10] <clerum> the tests are run from examples/sendmail [00:36:35] <clerum> https://github.com/seam/mail/tree/develop/examples/sendmail [00:37:33] <lightguard_jp> Other profiles work? [00:37:42] <clerum> no clue [00:37:50] <clerum> I mean mvn clean install at the root works [00:37:53] <lightguard_jp> Try the weld-ee-embedded-1.1 [00:38:01] <clerum> same [00:38:59] <clerum> doesn't run anything [00:39:26] <lightguard_jp> do a mvn help:effective-pom -Pjbossas-remote-6 and see if surefire is in there at all [00:41:56] <clerum> this is what eclipse spits out for effective pom [00:41:57] <clerum> https://gist.github.com/32a6c76e00580c22d5d8 [00:42:29] *** hannelita has quit IRC [00:43:55] <clerum> trying an oder commit [00:44:03] <clerum> trying an older commit [00:44:22] <lightguard_jp> Staring on line 1957 it says skip [00:44:41] *** hannelita has joined #seam-dev [00:44:41] <clerum> maybe something with the new bom [00:45:37] <lightguard_jp> Try with -DskipTests=false and see what happens [00:46:14] <lightguard_jp> Tests run in Catch, I didn't have to change anything wrt pom for testing when I moved to the new bom [00:48:06] *** stuartdouglas has left #seam-dev [00:51:14] <clerum> progress [00:53:08] <hannelita> lightguard_jp: about confbuzz app... there wasnt any sign up yet, right? [00:54:08] *** stuartdouglas has joined #seam-dev [00:54:59] <lightguard_jp> hannelita: bo [00:55:06] <lightguard_jp> hannelita: No, there was not [00:55:21] <lightguard_jp> clerum: That picked up the tests? [00:55:34] <hannelita> lightguard_jp: okay, i will pull rquest that feature in a few minutes :) [00:55:38] <clerum> deps for the functional tests seem to have broken it [00:56:41] <lightguard_jp> Ah [00:57:05] <clerum> I think it is running now except for the Render tests [00:57:35] <clerum> which have never worked as far as I can remember [00:58:45] <lightguard_jp> Thought Ken got those to work [00:59:15] <clerum> well failing now [00:59:18] <clerum> https://gist.github.com/1f75e80002fc41be7a0a [00:59:31] <clerum> but at least picking it up [01:03:18] <clerum> no clue where to even start on that [01:05:35] <lightguard_jp> Not sure why you don't have shrinkwrap on the cp [01:05:45] <lightguard_jp> That's very strange. It builds but doesn't run [01:06:50] <clerum> thats with as6 remote [01:07:28] <lightguard_jp> Does a clean test with that profile compile? [01:08:41] <clerum> yes [01:09:27] <clerum> same error [01:09:52] <clerum> ah grrr [01:11:30] <clerum> I really hate how the arquallian tests are so brittle [01:12:01] <clerum> with having the jar versions statically defined [01:12:01] <clerum> .importFrom(MavenArtifactResolver.resolve("org.jboss.seam.solder:seam-solder:3.1.0.Beta1")).as(JavaArchive.class)) [01:12:27] <clerum> but that wasn't the problem either [01:13:09] <lightguard_jp> Yes, that part sucks. [01:13:25] <lightguard_jp> clerum: According to that stack trace you're missing shrinkwrap on the classpath [01:13:34] <lightguard_jp> Unless you solved that one [01:14:12] <clerum> its there [01:14:26] <clerum> otherwise I would have tons of red all over my eclipse window when I have the test open [01:14:52] <clerum> shrinkwrap beta3 [01:15:45] <lightguard_jp> Right, but it's not there at runtime for whatever reason [01:16:54] <clerum> runtime on the jboss server? [01:16:58] <clerum> or runtime locally? [01:17:13] <lightguard_jp> Locally [01:17:14] <clerum> eh same error when ee embedded [01:17:36] <lightguard_jp> java.lang.NoClassDefFoundError: org/jboss/shrinkwrap/descriptor/api/Node [01:17:40] <lightguard_jp> from that gist you posted [01:17:58] <lightguard_jp> It's the descriptor portion... [01:18:00] <lightguard_jp> hrm [01:18:27] <clerum> I show 1.0.0-beta-3 in the test scope [01:18:42] <clerum> being suced in from arquilian 1.0.0.Alpha5 [01:19:46] <lightguard_jp> In the effective pom I see them in dependencyManagement, but not as a dependency. [01:20:17] *** alesj has quit IRC [01:21:58] <clerum> so I need to add a dep for that in addtion to arquillan? [01:21:59] <clerum> thats new [01:22:56] *** mbg has joined #seam-dev [01:23:07] *** cbrock has quit IRC [01:23:39] <lightguard_jp> For the resolver yes. [01:23:52] <lightguard_jp> Arquillian doesn't pull in the resolver stuff, I don't think. [01:24:51] <clerum> do you know which artifact? [01:26:33] <clerum> added and same problem [01:26:52] <clerum> new effective pom [01:26:53] <clerum> https://gist.github.com/637428504cf22fd31d73 [01:27:10] *** mbg has quit IRC [01:27:42] *** mbg has joined #seam-dev [01:29:37] <lightguard_jp> :( [01:29:55] <lightguard_jp> If you're happy with it, save the tests we can figure that out after the beta [01:30:21] <clerum> I can't refactor all of this with the tests not working [01:30:29] <clerum> that just doesn't seem like a good idea [01:32:55] <lightguard_jp> Fair enough [01:33:17] <jbossbot> git [mail] push develop 363c54f.. Cody Lerum remove functional test [01:33:17] <jbossbot> git [mail] push develop 1c85cf7.. Cody Lerum remove functional deps in pom [01:33:17] <jbossbot> git [mail] push develop 8369836.. Cody Lerum update tests and pom for Solder 3.1.0.Beta1 [01:33:17] <jbossbot> git [mail] push develop 3ea6303.. codylerum Merge pull request #8 from codylerum/develop... [01:33:17] <jbossbot> git [mail] push develop URL: http://github.com/seam/mail/compare/51598a9...3ea6303 [01:34:22] <lightguard_jp> clerum: You're missing the shrinkwrap-resolver-api and shrinkwrap-resolver-impl-maven, possibly the dscriptors api and impl, not the core shrinkwrap [01:35:02] <clerum> looks like the version I have for descritors in my classpath is beta 1 [01:35:06] <clerum> which doesn't have Node [01:35:14] <clerum> where is that version coming from... [01:35:17] <lightguard_jp> That could be it. [01:36:04] <clerum> coming from Arquillian-API 1.0.0.Alpha5 [01:36:26] <lightguard_jp> clerum: If you're using the most current parent pom we're using arquillian CR2 [01:36:32] *** sbryzak has quit IRC [01:36:47] <lightguard_jp> There are some code changes that will need to happen to use it, mostly classes were moved around [01:37:37] <clerum> no time lke the present [01:39:10] <clerum> http://www.jboss.org/arquillian [01:39:15] <clerum> so still says alpha 5 [01:39:23] <lightguard_jp> It's a little out of date :) [01:40:17] <lightguard_jp> https://repository.jboss.org/nexus/index.html#nexus-search;quick~arquillian-core [01:40:22] <clerum> the only arquillian version I find is <dependency> [01:40:22] <clerum> <groupId>org.jboss.arquillian</groupId> [01:40:22] <clerum> <artifactId>arquillian-junit</artifactId> [01:40:23] <clerum> <version>1.0.0.Alpha5</version> [01:40:23] <clerum> <scope>test</scope> [01:40:23] <clerum> </dependency> [01:40:32] <clerum> and CR2 doesn't appear valid [01:40:44] <lightguard_jp> that one changed [01:40:58] <lightguard_jp> https://repository.jboss.org/nexus/index.html#nexus-search;quick~arquillian-container-junit [01:42:45] <lightguard_jp> clerum: Take a look at tests in Catch [01:42:57] *** hannelita has quit IRC [01:43:29] <lightguard_jp> https://github.com/seam/catch/blob/develop/testsuite/pom.xml [01:44:16] <lightguard_jp> https://github.com/seam/catch/blob/develop/testsuite/internals/base/src/main/java/org/jboss/seam/exception/control/test/traversal/TraversalPathTest.java [01:44:20] <lightguard_jp> Hope those help a bit [01:46:49] <clerum> I'm going to have to turn this over to someone who knows arquillan better [01:47:26] <clerum> I took a look at the deps and added them [01:47:26] <lightguard_jp> clerum: I can take a look later [01:48:01] <clerum> but the two hours I had today are gone and I've made no acutal progress getting things refactored or woking on the doc [01:48:36] <clerum> someone who knows this could probably fix it in 10 minutes so it's not a great use of my time unfortunatly [01:49:18] <clerum> I can handle the refactoring if someone can get the test suite running [01:50:37] <clerum> If you could take a look later that would be great. I would love to get this sucker wrapped up [01:51:50] *** edburns_away is now known as edburns [01:52:49] *** sbryzak has joined #seam-dev [01:52:50] *** sbryzak has joined #seam-dev [01:53:05] *** bleathem has joined #seam-dev [02:05:49] *** mbg is now known as mbg|away [02:07:03] <lightguard_jp> clerum: Yeah I'll look later tonight. [02:15:11] <lightguard_jp> clerum: Most current on seam/mail or your fork? [02:15:43] <lightguard_jp> Looks like either one [02:15:52] <lightguard_jp> clerum: Do you care which one I use? [02:21:03] *** tkimura has joined #seam-dev [02:21:36] *** tsurdilo has quit IRC [02:24:36] *** hannelita has joined #seam-dev [02:26:46] *** lightguard_jp has quit IRC [02:31:48] *** mbg|away is now known as mbg [02:37:46] *** akazakov has quit IRC [02:38:08] *** jamezp is now known as jamezp_afk [03:09:19] *** tkimura has quit IRC [03:09:48] *** tkimura has joined #seam-dev [03:18:55] *** hannelita has quit IRC [04:12:21] <clerum> bleathem: what version do we use for RF 4.1 M1 [04:12:35] <clerum> 4.1.0.20110805-M1? [04:28:39] <jbossbot> git [social] push develop b995082.. Shane Bryzak updated versions, fixed compiler errors [04:28:39] <jbossbot> git [social] push develop URL: http://github.com/seam/social/compare/ca7b2da...b995082 [04:36:02] <jbossbot> git [social] push develop 883b5c5.. Shane Bryzak fix compiler errors [04:36:02] <jbossbot> git [social] push develop URL: http://github.com/seam/social/compare/b995082...883b5c5 [04:38:44] *** hannelita has joined #seam-dev [04:39:57] <jbossbot> git [social] push develop 8026d91.. Shane Bryzak fix distribution [04:39:57] <jbossbot> git [social] push develop URL: http://github.com/seam/social/compare/883b5c5...8026d91 [04:45:03] <jbossbot> git [social] push 3.1.0.Beta1 d383f54.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta1 [04:45:03] <jbossbot> git [social] push 3.1.0.Beta1 URL: http://github.com/seam/social/compare/0000000...e084c19 [04:50:35] <jbossbot> git [social] push develop d383f54.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta1 [04:50:35] <jbossbot> git [social] push develop 0b97933.. Shane Bryzak [maven-release-plugin] prepare for next development iteration [04:50:35] <jbossbot> git [social] push develop 78d9e2d.. Shane Bryzak Merge branch 'release/3.1.0.Beta1' into develop [04:50:35] <jbossbot> git [social] push develop URL: http://github.com/seam/social/compare/8026d91...78d9e2d [04:50:41] <jbossbot> git [social] push master ef032f4.. Antoine Sabot-Durand RESOLVED - issue SEAMSOCIAL-5: Update code formatting to community... [04:50:43] <jbossbot> jira [SEAMSOCIAL-5] Update code formatting to community formatting rules [Resolved (Done) Task, Major, Antoine Sabot-Durand] https://issues.jboss.org/browse/SEAMSOCIAL-5 [04:50:43] <jbossbot> git [social] push master 7411695.. Antoine Sabot-Durand RESOLVED - issue SEAMSOCIAL-6: Errors with Facebook component the... [04:50:44] <jbossbot> jira [SEAMSOCIAL-6] Errors with Facebook component the sample application [Resolved (Done) Bug, Major, Antoine Sabot-Durand] https://issues.jboss.org/browse/SEAMSOCIAL-6 [04:50:44] <jbossbot> git [social] push master a2ccac8.. Antoine Sabot-Durand RESOLVED - issue SEAMSOCIAL-7: Errors with Twitter component the... [04:50:45] <jbossbot> jira [SEAMSOCIAL-7] Errors with Twitter component the sample application [Resolved (Done) Bug, Major, Antoine Sabot-Durand] https://issues.jboss.org/browse/SEAMSOCIAL-7 [04:50:45] <jbossbot> git [social] push master 832fa88.. Antoine Sabot-Durand Adding the web client example as a module in parent project.... [04:50:45] <jbossbot> git [social] push master f9cdd64.. Antoine Sabot-Durand Refactoring OAuthServiceHandler to OAuthService... [04:50:46] <jbossbot> git [social] push master 54c0f7b.. Antoine Sabot-Durand Refactoring OAuthServiceHanlderScribe to OAuthServiceHandler... [04:50:46] <jbossbot> git [social] push master af033a2.. Antoine Sabot-Durand Refactor @Facebook Qualifier to @SetFacebook, FacebookHandler to... [04:50:47] <jbossbot> git [social] push master 789a686.. Antoine Sabot-Durand Refactor @LinkedIn qualifier to @SetLinkedIn, @LinkedInHandler to... [04:50:49] <jbossbot> git [social] push master b43fb83.. Antoine Sabot-Durand Refactor @Twitter qualifier to @SetTwitter, TwitterHandler to Twitter... [04:50:49] <jbossbot> git [social] push master ca472f6.. Antoine Sabot-Durand Last details about the refactoring in example web app and... [04:50:49] <jbossbot> git [social] push master 5365e9b.. Todd Morrison Add unique refId to each user against social network provider. ... [04:50:51] <jbossbot> git [social] push master ab68137.. Marek Schmidt fix ftest [04:50:51] <jbossbot> git [social] push master cd39f83.. Marek Schmidt Add Facebook OAuth ftest [04:50:52] <jbossbot> git [social] push master cb60e69.. Marek Schmidt Add empty facebook login fields to the ftest.properties [04:50:53] <jbossbot> git [social] push master 1fa158e.. Antoine Sabot-Durand Merge pull request #2 from DeepElement/develop... [04:50:53] <jbossbot> git [social] push master 8b5debf.. Antoine Sabot-Durand Merge pull request #3 from maschmid/fixtest2... [04:50:54] <jbossbot> git [social] push master 5a4141d.. LightGuard Fixing [SEAMSOCIAL-5] [04:50:55] <jbossbot> git [social] push master 4d99f13.. Antoine Sabot-Durand Merge branch 'multi_account' into develop [04:50:55] <jbossbot> git [social] push master 4e6e9c0.. Antoine Sabot-Durand Adding bin in gitignore and deleting bin directory [04:50:56] <jbossbot> git [social] push master e5aa47e.. Antoine Sabot-Durand OPEN - issue SEAMSOCIAL-12: Allow the support of multi-account on a... [04:50:57] <jbossbot> jira [SEAMSOCIAL-12] Allow the support of multi-account on a given social service [Closed (Done) Enhancement, Minor, Antoine Sabot-Durand] https://issues.jboss.org/browse/SEAMSOCIAL-12 [04:50:58] <jbossbot> git [social] push master 454fc4c.. Antoine Sabot-Durand CODING IN PROGRESS - issue SEAMSOCIAL-12: Allow the support of... [04:50:59] <jbossbot> git [social] push master c83d796.. Antoine Sabot-Durand SEAMSOCIAL-12 : support of 2 way to inject a service bean. Either with... [04:51:00] <jbossbot> git [social] push master f31f8b9.. Antoine Sabot-Durand CLOSED - issue SEAMSOCIAL-12: Allow the support of multi-account on a... [04:51:00] <jbossbot> git [social] push master f9bd0ae.. Antoine Sabot-Durand Merge branch 'multi_account' into develop [04:51:01] <jbossbot> git [social] push master a5ed8d4.. Antoine Sabot-Durand Added more details on usage in readme file. [04:51:12] <jbossbot> git [social] push master 194cdf1.. Antoine Sabot-Durand CODING IN PROGRESS - issue SEAMSOCIAL-14: Avoid using an Enum to... [04:51:13] <jbossbot> jira [SEAMSOCIAL-14] Avoid using an Enum to qualify services [Closed (Done) Enhancement, Major, Antoine Sabot-Durand] https://issues.jboss.org/browse/SEAMSOCIAL-14 [04:51:14] <jbossbot> git [social] push master fc6cc34.. Antoine Sabot-Durand CLOSED - issue SEAMSOCIAL-14: Avoid using an Enum to qualify services ... [04:51:14] <jbossbot> git [social] push master a03dba4.. Antoine Sabot-Durand Corrected Qualified OAuthService classes [04:51:15] <jbossbot> git [social] push master e9db848.. Antoine Sabot-Durand RESOLVED - issue SEAMSOCIAL-17: Adding scope support for OAuth 2.0... [04:51:16] <jbossbot> jira [SEAMSOCIAL-17] Adding scope support for OAuth 2.0 services [Resolved (Done) Feature Request, Minor, Antoine Sabot-Durand] https://issues.jboss.org/browse/SEAMSOCIAL-17 [04:51:17] <jbossbot> git [social] push master 6081274.. Antoine Sabot-Durand Support for Facebook update [04:51:17] <jbossbot> git [social] push master 38676b6.. Antoine Sabot-Durand Added a jboss-web.xml to set the context in JBoss [04:51:19] <jbossbot> git [social] push master 00a98f4.. Antoine Sabot-Durand Add a debug page to check active services [04:51:19] <jbossbot> git [social] push master b1714b3.. Antoine Sabot-Durand CLOSED - issue SEAMSOCIAL-13: Loose the coupling with Scribe-Java... [04:51:20] <jbossbot> jira [SEAMSOCIAL-13] Loose the coupling with Scribe-Java Library by using Injection [Closed (Done) Task, Major, Antoine Sabot-Durand] https://issues.jboss.org/browse/SEAMSOCIAL-13 [04:51:20] <jbossbot> git [social] push master 0033b0f.. Antoine Sabot-Durand RESOLVED - issue SEAMSOCIAL-18: OAuthServiceSettingsImpl is mandatory... [04:51:21] <jbossbot> jira [SEAMSOCIAL-18] OAuthServiceSettingsImpl is mandatory for all providers [Resolved (Done) Bug, Major, Antoine Sabot-Durand] https://issues.jboss.org/browse/SEAMSOCIAL-18 [04:51:22] <jbossbot> git [social] push master 3b4c75f.. Antoine Sabot-Durand Deleting Intellij config files commited by error [04:51:22] <jbossbot> git [social] push master faf4a95.. Antoine Sabot-Durand excluding iml Intellij Files [04:51:23] <jbossbot> git [social] push master 69d411e.. Antoine Sabot-Durand Correcting Arquillian test after refactoring [04:51:25] <jbossbot> git [social] push master 7362ce5.. Antoine Sabot-Durand Update Readme after refactoring [04:51:25] <jbossbot> git [social] push master ef4b8ed.. Antoine Sabot-Durand Packages renaming and introducing exception management [04:51:25] <jbossbot> git [social] push master d902429.. Antoine Sabot-Durand Added Seam Solder after test to run the web app in JBoss AS 7 and seam... [04:51:26] *** hannelita has quit IRC [04:51:27] <jbossbot> git [social] push master a5aada4.. Antoine Sabot-Durand Correcting Source file format... [04:51:27] <jbossbot> git [social] push master 5a75e7e.. Antoine Sabot-Durand Compatibility with JBoss AS 7 CR1 for social-web-client web app [04:51:28] <jbossbot> git [social] push master 91db580.. Antoine Sabot-Durand Added comment and exception management to OAuthProvider [04:51:29] <jbossbot> git [social] push master 74429a1.. Antoine Sabot-Durand Comment & formatting [04:51:29] <jbossbot> git [social] push master 8579a96.. Antoine Sabot-Durand Refactoring to prepare the addition of models object in social services [04:51:31] <jbossbot> git [social] push master 6aaac39.. Antoine Sabot-Durand Added support of JAXB implementation for JBoss AS7 [04:51:31] <jbossbot> git [social] push master 5e69dda.. Antoine Sabot-Durand Change import section to correct compilation error [04:51:32] <jbossbot> git [social] push master e23992d.. Antoine Sabot-Durand Integration of Twitter user mapping and method [04:51:33] <jbossbot> git [social] push master 2fd26ed.. Antoine Sabot-Durand Corrected copyrights and instructions in README [04:51:33] <jbossbot> git [social] push master d18e585.. Antoine Sabot-Durand Switch to Json profile for LinkedIn... [04:51:34] <jbossbot> git [social] push master d2992b5.. Antoine Sabot-Durand Removing dependencies to Jaxb for JBoss AS7 [04:51:35] <jbossbot> git [social] push master 0f9f402.. Antoine Sabot-Durand Switched Seam-Parent bom version 11 [04:51:35] <jbossbot> git [social] push master 1f0a65b.. Antoine Sabot-Durand generate @Default from @RelatedTo service... [04:51:36] <jbossbot> git [social] push master 2c6f322.. Antoine Sabot-Durand Preparing the inline setting of service beans [04:51:37] <jbossbot> git [social] push master 54570b8.. George Gastaldi Removed combined and changed impl artifact name [04:54:39] <bleathem> clerum: are you asking about the maven version? [04:55:20] <bleathem> clerum: errr... the richfaces version in the nexus maven repository [04:59:19] *** mbg is now known as mbg|away [05:01:22] *** gastaldi has joined #seam-dev [05:05:21] <jbossbot> git [wicket] push develop e2d38cf.. Shane Bryzak fix compiler errors because of new shrinkwrap version, fix other stuff [05:05:21] <jbossbot> git [wicket] push develop URL: http://github.com/seam/wicket/compare/9d7dabd...e2d38cf [05:05:59] <gastaldi> hey [05:07:27] <jbossbot> git [wicket] push develop 66a69d3.. Shane Bryzak removed arq deps from distribution [05:07:27] <jbossbot> git [wicket] push develop URL: http://github.com/seam/wicket/compare/e2d38cf...66a69d3 [05:07:27] <sbryzak> gastaldi: heya [05:09:18] <gastaldi> hey sbryzak [05:09:44] <gastaldi> Hum, Solder could turn into a one jar only , WDYT ? [05:09:55] [05:10:09] <sbryzak> interesting thought, i think it has merit [05:10:19] <sbryzak> you should bring it up at the meeting tomorrow [05:10:28] <gastaldi> it will solve that problem :) [05:10:53] <sbryzak> agreed [05:11:13] <sbryzak> i would like to see logging separated out also [05:11:19] <gastaldi> indeed [05:11:29] <sbryzak> since we have a separate jar for it anyway [05:11:36] <sbryzak> i think a seam-logging module makes sense [05:11:41] <gastaldi> yeah [05:11:43] <gastaldi> Absolutely [05:11:48] <sbryzak> and more intuitive for new users [05:11:54] <sbryzak> who don't know what solder is [05:12:11] <gastaldi> Well, we have JBoss Logging, SLF4J, commons-logging, log4j [05:12:12] <gastaldi> :) [05:12:27] <jbossbot> git [wicket] push 3.1.0.Beta1 c1cdb4c.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta1 [05:12:27] <jbossbot> git [wicket] push 3.1.0.Beta1 URL: http://github.com/seam/wicket/compare/0000000...4c9d0d1 [05:12:43] [05:13:14] <sbryzak> yeah, but SOLDER-102 [05:13:15] <jbossbot> jira [SOLDER-102] Change way in which JBoss Logging is embedded [Resolved (Done) Enhancement, Major, Ken Finnigan] https://issues.jboss.org/browse/SOLDER-102 [05:13:32] <sbryzak> it delegates to jboss logging [05:13:41] <sbryzak> however i think we require it for typesafe messaging [05:13:48] <gastaldi> hum [05:13:48] <sbryzak> er, typesafe logging i mean [05:14:00] <gastaldi> Yeah, that justifies a seam-logging module [05:15:01] <sbryzak> we can discuss it tomorrow [05:17:01] <gastaldi> cool [05:21:13] <gastaldi> wow, the list is on fire ! :) [05:22:10] <sbryzak> yeah we stirred the hornets nest [05:22:44] <jbossbot> git [wicket] push develop c1cdb4c.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta1 [05:22:44] <jbossbot> git [wicket] push develop 9cb8285.. Shane Bryzak [maven-release-plugin] prepare for next development iteration [05:22:44] <jbossbot> git [wicket] push develop 485f00a.. Shane Bryzak Merge branch 'release/3.1.0.Beta1' into develop [05:22:44] <jbossbot> git [wicket] push develop URL: http://github.com/seam/wicket/compare/66a69d3...485f00a [05:22:44] <jbossbot> git [wicket] push master d2163a3.. Marek Schmidt fixing the numberguess example, SEAMWICKET-32, SEAMWICKET-33 [05:22:46] <jbossbot> jira [SEAMWICKET-32] wicket-numberguess - dependencies incorrectly scoped [Resolved (Done) Bug, Minor, Marek Schmidt] https://issues.jboss.org/browse/SEAMWICKET-32 [05:22:47] <jbossbot> jira [SEAMWICKET-33] wicket-numberguess - fails to deploy on GlassFish due to missing slf4j dependency [Resolved (Done) Bug, Major, Marek Schmidt] https://issues.jboss.org/browse/SEAMWICKET-33 [05:22:47] <jbossbot> git [wicket] push master 9d7dabd.. George Gastaldi Merge pull request #8 from maschmid/fixexample... [05:22:47] <jbossbot> git [wicket] push master e2d38cf.. Shane Bryzak fix compiler errors because of new shrinkwrap version, fix other stuff [05:22:48] <jbossbot> git [wicket] push master 66a69d3.. Shane Bryzak removed arq deps from distribution [05:22:49] <jbossbot> git [wicket] push master c1cdb4c.. Shane Bryzak [maven-release-plugin] prepare release 3.1.0.Beta1 [05:22:50] <jbossbot> git [wicket] push master 9cb8285.. Shane Bryzak [maven-release-plugin] prepare for next development iteration [05:22:51] <jbossbot> git [wicket] push master 75cd1bd.. Shane Bryzak Merge branch 'release/3.1.0.Beta1' [05:22:51] <jbossbot> git [wicket] push master URL: http://github.com/seam/wicket/compare/96a4e86...75cd1bd [05:26:35] <gastaldi> thanks for the cleanup on Seam Reports [05:30:23] <gastaldi> gotta sleep now [05:30:25] <gastaldi> bye ! [05:30:34] <sbryzak> gastaldi: good night [05:30:44] [05:30:51] *** gastaldi has quit IRC [05:31:10] *** mbg|away is now known as mbg [06:18:26] *** hannelita has joined #seam-dev [06:37:10] *** clerum has quit IRC [06:37:44] *** clerum has joined #seam-dev [06:49:37] *** hannelita has quit IRC [07:14:29] *** jamezp_afk is now known as jamezp [07:16:48] *** hannelita has joined #seam-dev [07:24:41] *** lightguard_jp has joined #seam-dev [07:33:45] *** hannelita has quit IRC [07:35:13] <sbryzak> lightguard_jp: ping [07:36:14] <lightguard_jp> sbryzak: Yes [07:36:24] <sbryzak> hey jason [07:36:47] <sbryzak> those changes you made to the module release page, replacing -Drelease with -Prelease [07:36:52] <sbryzak> they're wrong ;) [07:36:58] <sbryzak> we use property-based profile activation, not id-based [07:37:02] <sbryzak> so -P doesn't work [07:37:20] <sbryzak> could you fix it pls? [07:37:31] <lightguard_jp> Worked with Catch [07:37:41] *** mbg is now known as mbg|away [07:37:45] <sbryzak> perhaps the profile in catch is called release [07:37:52] <sbryzak> but it's not that in other modules [07:38:05] <sbryzak> in faces for example it's called distribution [07:38:06] <lightguard_jp> okay [07:39:00] <lightguard_jp> Kick the server and I'll change it :) [07:39:12] <sbryzak> bah, it's down again? [07:39:23] <lightguard_jp> Still trying to load [07:39:36] <sbryzak> np, i'm on it [07:39:36] <lightguard_jp> Been sitting there for two minutes [07:39:51] <lightguard_jp> Is this because of ir2 and ceylon again? [07:40:07] <sbryzak> i wish i knew [07:40:18] <lightguard_jp> Logs aren't telling you much? [07:40:46] <sbryzak> they probably would, but it would take ages to go through them and get useful info out [07:41:39] <lightguard_jp> :( [07:41:40] <sbryzak> it's still trying to shut down [07:42:19] <sbryzak> it's just funny that christian didn't pick up on these scalability issues when he was developing the site [07:44:16] <lightguard_jp> No kidding [07:44:20] <lightguard_jp> Or maybe he just didn't care [07:46:47] <sbryzak> btw, i don't think i'm going to do a public release of beta1 [07:47:01] <sbryzak> i'm not at all happy with it [07:47:04] <lightguard_jp> Should we skip it and do Beta2? [07:47:07] <sbryzak> i think we should keep it internal only [07:47:15] <sbryzak> yeah exactly [07:47:25] <lightguard_jp> Okay, I'm fine with that [07:47:29] <sbryzak> beta1 has served its purpose in showing us how much stuff is broken [07:47:33] <sbryzak> pretty much all the tests are broken [07:47:35] <lightguard_jp> Should have been Alpha1 huh? [07:47:42] <sbryzak> in hindsight, yes [07:47:57] <sbryzak> i don't even think that qa can test beta1 [07:48:11] <lightguard_jp> Ooph [07:48:23] <lightguard_jp> Mostly because of the solder changes? [07:48:32] <sbryzak> we can discuss it more during the irc meeting, but i wanted to give you a heads up [07:48:40] <sbryzak> solder changes, test changes [07:48:49] <sbryzak> i also think we should split out logging [07:48:56] <sbryzak> into it's own module [07:49:09] <sbryzak> since we've broken backwards compatibility anyway [07:49:12] *** lazarotti has quit IRC [07:49:35] <sbryzak> it would be far more intuitive for a user to have an import for org.jboss.seam.logging than org.jboss.seam.solder.logging [07:49:37] <lightguard_jp> away from solder? [07:49:40] <sbryzak> yes [07:49:51] <lightguard_jp> I'm fine with that [07:52:19] <lightguard_jp> We need to spend some time and get jenkins setup with the paid FOSS account (Rodney okay'd it) and setup the release plugin [07:52:36] <lightguard_jp> Then once all the modules have the right structure and everything it'll all be push button [07:53:22] *** rruss has quit IRC [07:53:30] <lightguard_jp> I've thought about doing one repo that has all of the modules as git sub modules [07:53:51] <lightguard_jp> Then you'd just update the sub-modules, commit and let jenkins do the release, how cool would that be? [07:53:58] <sbryzak> is the intention to give all our developers access? [07:54:32] <lightguard_jp> Module leads, at least access so they can do builds themselves, and update config if they need to. [07:54:33] <sbryzak> if we could somehow automate the release i would jump for joy [07:54:50] <sbryzak> what we really need to automate is a release build for all the modules [07:54:57] <lightguard_jp> The config part we may or may not give access to, not sure 100% on that one yet. [07:54:58] <sbryzak> i don't think anyone does that [07:55:13] <sbryzak> and i would love to have standard tests for the distributions [07:55:25] <sbryzak> i.e. checking they conform to the standard directory structure, e.g. [07:55:26] *** rruss has joined #seam-dev [07:55:32] <lightguard_jp> Yes, a git repo with all the modules as sub-modules, that's only updated when it's release time could do that. [07:55:41] <sbryzak> checking that the readme and license files are there [07:56:01] <lightguard_jp> In jenkins when you push to that repo you could have it build and release each module. [07:56:24] <lightguard_jp> Or you could set up a matrix job to do that (I think, I still consider myself a Jenkins n00b) [07:56:35] <lightguard_jp> Fixed the release page [07:57:15] <sbryzak> so are you volunteering to set all this up? :) [07:57:31] <lightguard_jp> AS7 has spoiled me [07:57:39] <lightguard_jp> Watching AS6 start is like watching paint dry [07:58:01] <lightguard_jp> Could be worse though, could be AS5.0 [07:58:30] <lightguard_jp> sbryzak: I have the Jenkins book. Be awesome if a community member were better at it. [07:59:43] <sbryzak> we could ask at the irc meeting [08:00:33] <lightguard_jp> I asked once before. George seems to know a bit [08:00:48] <lightguard_jp> Not sure how deep his knowledge goes though [08:07:01] *** mgoldmann has joined #seam-dev [08:07:25] *** DiabloD3 has joined #seam-dev [08:07:40] <lightguard_jp> sbryzak: Any of the qa folk online or not yet? [08:07:55] <lightguard_jp> They probably don't get in until 9 their time [08:07:58] <sbryzak> doesn't look like it [08:08:08] <sbryzak> and i haven't seen ondrej online this week at all [08:08:15] <lightguard_jp> They typically hang out on the vpn #seam don't they? [08:08:34] *** tremes has joined #seam-dev [08:10:35] <sbryzak> yes [08:22:09] <sbryzak> stuartdouglas: ping [08:22:15] <stuartdouglas> sbryzak: pong [08:22:20] <sbryzak> hey stuart [08:22:32] <sbryzak> were you explaining to someone the other day how to get jboss logging working in as7? [08:23:03] <stuartdouglas> you just put a module dependency on jboss-logging in the manifest [08:23:16] <sbryzak> how does that look? [08:23:25] <sbryzak> and do you still need to distribute the jboss-logging jar with your app? [08:23:37] <stuartdouglas> Dependencies: org.jboss.logging [08:23:45] <stuartdouglas> in MANIFEST.MF [08:23:53] <stuartdouglas> and it will use the app servers version [08:23:58] <stuartdouglas> https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7 [08:23:59] <sbryzak> great, thanks [08:24:07] <sbryzak> i'll stick that in an e-mail for seam-dev [08:24:11] <sbryzak> everyone will need to know about it [08:24:27] <stuartdouglas> theres an example of the maven config needed to generate the manifest in that document [08:24:45] <sbryzak> cool, that will be helpful [08:25:41] <lightguard_jp> Yes, that's a better solution than using the xml in the war, imo [08:25:54] <sbryzak> ah, i have a dependency for org.slf4j.impl already, do you comma-separate if you have more than one? [08:26:09] <stuartdouglas> yes [08:26:18] <sbryzak> thanks [08:26:37] <lightguard_jp> stuartdouglas: Do you work from home or do you go into the office? [08:26:47] <stuartdouglas> I work from home [08:27:09] <sbryzak> it's a 2 hour train ride for stuart to get to the office :) [08:27:15] <lightguard_jp> Ah [08:27:32] <sbryzak> i think it's almost faster for me to get to the sydney office than him [08:28:23] <sbryzak> stuartdouglas: i'm still getting this deployment error, any ideas? [08:28:24] <sbryzak> Caused by: java.lang.NoClassDefFoundError: org/jboss/logmanager/Logger$AttachmentKey [08:28:24] <sbryzak> at org.jboss.seam.solder.logging.internal.JBossLogManagerProvider.<clinit>(JBossLogManagerProvider.java:36) [08:28:57] <sbryzak> in my MANIFEST.MF i have: Dependencies: org.slf4j.impl,org.jboss.logging [08:31:56] *** marekn has joined #seam-dev [08:32:05] <stuartdouglas> sbryzak: you also need a dependency on org.jboss.logmanager [08:33:14] <sbryzak> thanks [08:34:20] <lightguard_jp> Anyone know if there's some internal doc about how to use the ftest setup? [08:34:35] <lightguard_jp> bleathem: ^^ maybe you know, I'm sure you guys use ftest more [08:34:56] <bleathem> we do use it a lot, but I haven't touched it yet [08:35:47] <lightguard_jp> Any idea if there's some docs or something you guys have about using it or setting it up? [08:36:50] *** maschmid has joined #seam-dev [08:39:29] <lightguard_jp> Starting to feel like it would be better to change all of these mail tests to use arquillian and drone instead of the QE ftest setup [08:46:27] *** daniel_hinojosa has quit IRC [08:47:53] <lightguard_jp> clerum: Still here? [08:51:32] <lightguard_jp> stuartdouglas: You haven't used Arquillian Drone, have you? [08:51:36] <stuartdouglas> no [08:51:38] <bleathem> lightguard_jp: should be somewhere, but I don't know [08:51:47] <lightguard_jp> bleathem: Okay, no problem [08:52:47] *** bleathem has quit IRC [08:55:56] *** rruss has quit IRC [09:02:22] <maschmid> sbryzak: Ondrej and Jozef are on PTO this week... [09:02:37] <sbryzak> ah, that would explain things [09:04:27] <maschmid> sbryzak: btw. is there any known trick to make the solder 3.1.0.Beta1 work on AS7? (SOLDER-119) [09:04:28] <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 [09:04:51] <sbryzak> yes, read my latest post to seam-dev ;) [09:06:57] <maschmid> sbryzak: I see :) [09:07:30] <marekn> lightguard_jp, sbryzak: what do you want to know about ftest? I know a little about it [09:08:05] <lightguard_jp> marekn: The Seam Mail tests are using it, I think I may just rewrite them to use arquillian drone [09:08:05] <marekn> lightguard_jp, sbryzak: I suppose Seam3 have got maven profile for that [09:09:17] <marekn> lightguard_jp: well, ftest is only launching selenium tests in browser [09:09:58] <lightguard_jp> Always wanted something more setup, which should have already been setup with deps or ftests.xml [09:09:58] <marekn> lightguard_jp: and all setup should be in profile except jboss.home property for real container [09:10:02] <lightguard_jp> But it didn't seem to work [09:11:03] <marekn> one thing is important selenium remote client doesn't work in current browsers, if there is not upgrade to selenium driver version 2 [09:11:11] <maschmid> I think that even with the ftest profile, you still have to deploy and start the container manually... the ftest profile just starts the selenium... [09:11:58] <lightguard_jp> All the more reason to use arquillian ;) [09:12:27] <sbryzak> lightguard_jp: did you just delete some spam from sfwk.org recently? [09:12:41] <lightguard_jp> Yes [09:12:55] <sbryzak> np, was wondering where it went.. you're fast ;) [09:13:11] <lightguard_jp> Came across on one of the Seam 3 forum posts [09:13:28] <sbryzak> yeah, it's much easier to spot when they post it in the forums [09:14:07] <lightguard_jp> Yeah, the other ones I'm typically told about. [09:16:24] <lightguard_jp> sbryzak: Can we setup in the seam-parent to add the jboss logging info in the manifest? [09:16:34] <lightguard_jp> Looks like it's just in the archive plugin confi [09:16:36] <lightguard_jp> config [09:17:08] <sbryzak> hmm, you don't think it would be better to do on an example by example basis? [09:17:20] <sbryzak> we don't actually want it for as6 builds [09:17:26] <lightguard_jp> We'll need it when we pull it out into it's own module anyway. [09:17:34] <sbryzak> not that it would probably hurt, but it just seems like bad form [09:17:46] <lightguard_jp> We're targeting AS7, right? [09:18:01] <sbryzak> that's our default target, but we should have poms for other container versions also [09:18:49] <lightguard_jp> That'll get nasty [09:19:09] <lightguard_jp> It's probably worth trying and see what happens on any other server. [09:19:29] *** chkal has joined #seam-dev [09:19:59] <sbryzak> we should really have builds for as7, as6, gf and tomcat at minimum [09:20:16] <sbryzak> so the default pom should be for as7, then we have pom-as6.xml, pom-gf.xml, etc [09:21:47] <lightguard_jp> We need tomcat tests [09:22:27] <lightguard_jp> We've been getting slammed over the past couple of weeks on the forums for tomcat support [09:22:28] <sbryzak> we should have tests for all containers that arq supports [09:23:45] <lightguard_jp> +1 [09:24:12] *** jamezp is now known as jamezp_afk [09:28:28] <nickarls> stuartdouglas: ping [09:28:36] <stuartdouglas> nickarls: pong [09:29:04] <nickarls> is there any magic in getting SMPC to work with a @SessionScoped @Stateful? [09:29:16] <stuartdouglas> shouldn't be [09:29:53] <nickarls> I have the producer and @Inject EntityManager and load a collection and then later when I do em.contains() on one of the items it returns false [09:30:06] <nickarls> I thought it would still be attached [09:30:22] <nickarls> same when remove comes in from the UI I get a detached error [09:30:25] <stuartdouglas> that is very odd [09:30:50] <stuartdouglas> what does your smpc producer look like? [09:31:13] <stuartdouglas> actually, is your SMPC session scoped as well? [09:31:28] *** aslak has joined #seam-dev [09:31:36] <nickarls> http://pastebin.com/DuBnUjGb [09:31:47] <stuartdouglas> thats conversation scoped [09:31:56] <stuartdouglas> so it is shorted lived the an session scoped bean [09:32:04] <stuartdouglas> so that is why they get detached [09:32:18] <nickarls> I thought the @CS was just some marker [09:32:43] <stuartdouglas> no, it means that it is conversation scoped [09:33:33] <nickarls> stuartdouglas: I must have stopped reading the docs before the " It only specifies the scope of the created SMPC, not the EntityManagerFactory." ;-) [09:33:49] <nickarls> saw the "as the @ConversationScoped annotation is removed by the seam persistence portable extension" [09:34:31] <lightguard_jp> stuartdouglas: I spoke with someone, and they had an idea that may help ease some confusion with that. Create a new annotation called @PersistenceUnitScope(Class<? extends Annotation>) or something like that. The value would be the scope you want your em scoped [09:36:27] <stuartdouglas> lightguard_jp: are scopes allowed to have members? [09:37:06] <lightguard_jp> stuartdouglas: It wouldn't be a scope, just a normal annotation. [09:37:26] <stuartdouglas> actually thats a good idea [09:37:32] <stuartdouglas> can you create a JIRA [09:37:37] <lightguard_jp> The name may be something different [09:37:40] <lightguard_jp> Sure [09:39:52] <lightguard_jp> SEAMPERSIST-66 [09:39:53] <jbossbot> jira [SEAMPERSIST-66] Create a new annotation to configure the scope of the Persistence Unit when it is produced [Open (Unresolved) Enhancement, Major, Unassigned] https://issues.jboss.org/browse/SEAMPERSIST-66 [09:46:22] <nickarls> stuartdouglas: thanks, that did the trick. [09:47:03] <stuartdouglas> why do you want a session scoped pc anyway? [09:47:19] <stuartdouglas> they can cause all kinds of problems [09:47:50] <stuartdouglas> cause the entites never get released if you are not careful it can just get bigger and bigger [09:48:05] <stuartdouglas> which means slower and slower to flush, and can also eat heaps of memory [09:48:50] <nickarls> It's not me personally, just helping in a project migration. But I agree, conversation would be better. [09:48:58] *** emmanuel has joined #seam-dev [10:00:50] <nickarls> It would be easier if Weld/Seam would have single-JSF-lifecycle-conversation switching [10:00:54] *** koentsje has joined #seam-dev [10:01:44] <nickarls> as there is a menu tree on the left and if you click a node and start a conversation, you would have to be able to do the same thing when clicking on another node [10:02:03] <nickarls> I'll have to see if the noCid parameter or h:link could be used to stop propagation... [10:05:28] *** shervin_a has joined #seam-dev [10:33:51] *** sannegrinovero has joined #seam-dev [10:38:17] *** alesj has joined #seam-dev [10:44:01] <lightguard_jp> Second set of eyes would be helpful on this one: http://seamframework.org/Community/InjectRequestBeansIntoAServletFails [10:44:08] <lightguard_jp> I don't see anything really wrong there [10:44:41] *** mgoldmann has quit IRC [10:46:12] *** alesj has quit IRC [10:51:37] *** mgoldmann has joined #seam-dev [10:53:11] *** kevinpollet has joined #seam-dev [10:53:29] *** kevinpollet has quit IRC [10:54:01] <clerum> lightguard_jp: strange [10:56:41] <lightguard_jp> clerum: You're still up? [10:56:53] <clerum> well just got up [10:57:03] <clerum> doing some equipment maintenence from 3-4 am [10:57:34] <clerum> will his producer return a null value? [10:57:59] <clerum> ah now it won't I see the events are setitng [10:58:11] <clerum> err [10:58:35] <clerum> maybe they seem to be in aloop [10:59:00] <clerum> the prodcuers assume the events set the values for account and user [10:59:10] *** koentsje has quit IRC [10:59:15] <clerum> and the events both inject values produced by the producers [10:59:22] <lightguard_jp> Could be. [10:59:27] <clerum> is that possibly activating another session context? [10:59:33] <lightguard_jp> Not really sure what's going on. [11:00:01] <clerum> seems like that should throw a cyclical dependency error [11:00:54] <clerum> yeah that shouldn't work [11:02:37] <clerum> or does it.. [11:02:38] <nickarls> I think I have seen some strangeness with session scoped stuff and sessionlisteners [11:02:51] <clerum> err I do something similar [11:03:04] *** fiorenzino has joined #seam-dev [11:03:52] <clerum> I guess I would need to see the declaration of the event that fires the userAuthenticated [11:04:17] <lightguard_jp> clerum: If you don't mind replying, that may help spark an idea [11:04:26] <lightguard_jp> clerum: I'm also getting closer on your tests [11:04:42] <nickarls> https://issues.jboss.org/browse/WELD-892 ? [11:04:44] <jbossbot> jira [WELD-892] Calling session-scoped components from session initialized observer goes into infinite loop [Open (Unresolved) Bug, Major, Ales Justin] https://issues.jboss.org/browse/WELD-892 [11:04:48] <lightguard_jp> I rewrote them to not use the QE selenium stuff but to use the arquillian equiv [11:05:55] <nickarls> hmm, correction, apparently he wasn't using a servlet event observer [11:06:54] <lightguard_jp> It still may boil down to the same issue. [11:07:18] <nickarls> does anyone know if it's possible to have a seam catch (or other) interceptor ordered so the transaction doesn't die on persistence exceptions? [11:07:57] <lightguard_jp> I think that's a bug in persistence / transaction. [11:08:09] <lightguard_jp> Seems like it's rolling them back before catch can get to them. [11:08:23] <lightguard_jp> I think that's what I uncovered a while back, but forgot to create a JIRA [11:08:59] <nickarls> I have a case where the Oracle DB has certain unique constraint violations that can result in exceptions that are really not that fatal. [11:09:22] <lightguard_jp> Ah, you just need to log them or swallow them? [11:09:51] <nickarls> yep. Catch sees them but the transaction is dead on retry already [11:10:54] <lightguard_jp> Yeah, go through the transaction code and look to see if it's rolling things back. [11:10:59] <lightguard_jp> I think it is, but I don't remember where [11:11:47] <nickarls> but if it's just a matter of interceptor ordering, catch could swallow it before the transactioninterceptor would see it? [11:12:05] <nickarls> (it's a session EJB) [11:12:24] <lightguard_jp> If the interceptor doing the transactions is CDI based. [11:12:41] <lightguard_jp> You could use an interceptor to fire into catch. [11:13:01] <lightguard_jp> You'd put that interceptor in before the transaction one in your beans.xml and it should work [11:13:36] <nickarls> yep, I already have a catch interceptor but I think I would have to order with respect to internal EJB interceptors and that migght be... nontrivial [11:14:09] <nickarls> perhaps I should just try a pojo and use transactions/persistence for the interceptors [11:14:13] <lightguard_jp> I think you'd be correct. [11:14:22] *** fiorenzino has left #seam-dev [11:21:46] *** fiorenzino has joined #seam-dev [11:25:41] *** fiorenzino has quit IRC [11:26:09] *** fiorenzino has joined #seam-dev [11:27:27] *** fiorenzino_ has joined #seam-dev [11:27:49] *** fiorenzino_ has quit IRC [11:28:05] *** fiorenzino has joined #seam-dev [11:30:00] *** fiorenzino has quit IRC [11:33:07] *** tkimura has quit IRC [11:37:28] *** fiorenzino has joined #seam-dev [11:42:42] *** tremes has quit IRC [11:46:30] *** tsurdilo has joined #seam-dev [12:14:50] *** sannegrinovero has quit IRC [12:15:00] *** tsurdilo1 has joined #seam-dev [12:17:17] *** tsurdilo has quit IRC [12:17:36] *** tsurdilo2 has joined #seam-dev [12:19:33] <lightguard_jp> clerum: Still here? [12:20:50] *** tsurdilo1 has quit IRC [12:21:06] <clerum> yep [12:21:27] <lightguard_jp> I'm pretty close, I think just some shrinkwrap stuff. [12:21:31] <lightguard_jp> Shall I push? [12:21:36] <lightguard_jp> Or hold off until it's done? [12:21:43] <clerum> sure push [12:21:53] <clerum> I can look at in in the am too [12:26:16] *** tsurdilo1 has joined #seam-dev [12:29:45] *** tsurdilo2 has quit IRC [12:30:47] <clerum> off to catch a few ours sleep. [12:30:51] <jbossbot> git [mail] push develop c967577.. LightGuard First stab at fixing up tests [12:30:51] <jbossbot> git [mail] push develop 3bd4e27.. LightGuard Fixing pom from bad rebase [12:30:51] <jbossbot> git [mail] push develop URL: http://github.com/seam/mail/compare/3ea6303...3bd4e27 [12:31:03] <lightguard_jp> Hope that worked okay and I didn't screw up the poms :) [12:31:05] <clerum> lightguard_jp:thanks for looking [12:31:18] <lightguard_jp> clerum: Sure, still got a few things left to do though. [12:31:18] <clerum> eh we need to get it squared aways [12:31:33] <lightguard_jp> At least you can focus on docs now. [12:31:48] <clerum> thats where I want to be [12:31:57] <clerum> at a place I can refactor the modules into an api and impl [12:32:00] <clerum> and the docs [12:32:03] <lightguard_jp> Cool. I'm going to bed too. [12:32:07] <clerum> k [12:32:08] <clerum> later [12:32:09] <clerum> thanks [12:32:12] <lightguard_jp> Sure thing. [12:32:16] <nickarls> is there some way of configuring a @Conversational view in @ViewConfig? So that it would start a conversation if one is not available? [12:32:33] <lightguard_jp> nickarls: viewaction? [12:33:13] <nickarls> yes, that or the jsf preRenderView are options [12:37:14] *** lightguard_jp has quit IRC [12:42:42] *** shervin_a has quit IRC [13:01:30] *** sannegrinovero has joined #seam-dev [13:01:57] *** tremes has joined #seam-dev [13:18:39] *** rmartinelli has joined #seam-dev [13:42:55] *** mateus has joined #seam-dev [13:51:29] *** emmanuel has quit IRC [13:57:22] *** epbernard has joined #seam-dev [13:57:22] *** epbernard is now known as emmanuel [14:02:25] *** rruss has joined #seam-dev [14:23:22] *** aslak has quit IRC [14:23:43] *** aslak has joined #seam-dev [14:26:05] *** aslak has quit IRC [14:26:43] *** aslak has joined #seam-dev [14:33:08] *** gastaldi has joined #seam-dev [14:33:16] <gastaldi> hey [14:36:30] *** emmanuel has quit IRC [14:39:36] *** clerum has quit IRC [14:41:23] *** clerum has joined #seam-dev [14:46:39] <jose_freitas> hey gastaldi, good morning [14:47:15] <gastaldi> hey jose_freitas, good morning [14:47:21] <gastaldi> :) [14:47:30] <gastaldi> ready for TDC this weekend ? [15:02:59] <jose_freitas> nope [15:02:59] <jose_freitas> hahaha [15:03:02] *** edburns is now known as edburns_away [15:03:04] <jose_freitas> want to help me? [15:03:06] *** edburns_away is now known as edburns [15:03:43] *** edburns has quit IRC [15:07:04] <gastaldi> I wish I could :) [15:08:18] *** alesj has joined #seam-dev [15:11:19] <jose_freitas> aren't you coming? [15:13:01] <gastaldi> unfortunately not :( [15:13:11] *** mbg|away is now known as mbg [15:13:30] [15:14:22] <gastaldi> until october, I am stuck :P [15:14:28] <gastaldi> damn [15:27:16] <jose_freitas> hehehe [15:27:20] <jose_freitas> that's ok [15:30:37] *** jganoff has joined #seam-dev [15:36:03] *** lazarotti has joined #seam-dev [15:41:25] *** lazarotti has quit IRC [15:42:07] *** lazarotti has joined #seam-dev [15:54:51] *** chkal has quit IRC [15:56:23] *** koentsje has joined #seam-dev [16:01:00] *** hannelita has joined #seam-dev [16:39:51] <gastaldi> It seems that Ctrl+C is not supported on Forge [16:42:15] <jose_freitas> gastaldi: what forge plugins do you use(just for curiosity) [16:46:19] <gastaldi> Just metawidget and persistence [16:46:22] <gastaldi> the basic ones [16:47:14] <gastaldi> Damn, I am getting a java.lang.ClassNotFoundException: sun.util.calendar.ZoneInfo from [Module "deployment.coelho.war:main" from Service Module Loader] [16:47:33] <gastaldi> When I add a java.util.Date as a field [16:47:40] <gastaldi> And try to save it [16:48:45] <gastaldi> http://community.jboss.org/thread/169938?tstart=0 [16:49:25] <clerum> really? [16:49:37] <clerum> java.util.Date isn't supported by default? [16:50:23] *** edburns has joined #seam-dev [16:50:37] <edburns> Is bleatham on vacation right now? [16:52:51] <jose_freitas> edburns : nope. saw him yesterday [16:53:01] <jose_freitas> he'll probably be here in one hour [16:53:32] <edburns> jose_freitas: Ok, thanks. [16:58:21] *** daniel_hinojosa has joined #seam-dev [17:01:28] *** balunasj has joined #seam-dev [17:02:36] *** daniel_hinojosa has quit IRC [17:03:32] *** mateus has quit IRC [17:05:12] *** bleathem has joined #seam-dev [17:21:32] *** marekn has quit IRC [17:24:46] <gastaldi> clerum: I applied the fix proposed on the forum and worked allright [17:24:57] <gastaldi> Maybe it will be fixed on 7.0.1 / 7.1 [17:28:02] <edburns> bleathem: Hello, are you here? [17:28:09] <bleathem> hi edburns [17:28:46] <edburns> bleathem: I haven't seen any replies on my "[758-ViewActions] Realization of Resolution Attempt One" email. [17:29:05] <bleathem> I've started looking at what you shared for the viewAction stuff [17:29:11] <edburns> bleathem: I'd like to get one of our writers to create a blog entry describing the feature and showing how to use it. [17:29:23] <bleathem> haven't gotten through it yet though [17:29:31] <edburns> bleathem: but I don't want to sic them on the content until I at least have sign off from you. [17:29:32] <bleathem> I'll make a point of doing so today [17:29:50] <edburns> bleathem: Ok. Let me tell you how to get the latest spec. [17:29:56] <edburns> In fact, I'll send it to the eg. [17:29:59] <bleathem> We had a RichFaces M1 release yesterday, which was all-cosuming for me [17:31:05] <bleathem> but I'll have some time for this today! [17:32:42] <edburns> bleathem: I just sent mail titled: "[ADMIN] How to view the latest spec (except for the PDF)". Can you please confirm you've received that email here? [17:34:08] <edburns> bleathem: Once you've signed off on the feature, and I've applied any changes we agree upon, can I set up a 40 minute meeting between you and I and a writer to suss out the blog entry? [17:34:52] *** tremes has quit IRC [17:34:56] <bleathem> sure, sounds good [17:37:47] *** oranheim_ has joined #seam-dev [17:37:49] *** daniel_hinojosa has joined #seam-dev [17:38:34] *** koentsje has quit IRC [17:39:50] <edburns> bleathem: Ok, I'll try to line up a writer. Did you receive the email? [17:40:04] <edburns> bleatham: I sent it to jsr344-experts [17:40:13] *** oranheim has quit IRC [17:40:13] *** oranheim_ is now known as oranheim [17:42:36] <bleathem> edburns: yes, I received the email [17:45:25] <edburns> bleathem: Ok, following the instructions in there, are you able to get what you need to review the feature? [17:45:35] *** balunasj has quit IRC [17:47:25] *** oranheim_ has joined #seam-dev [17:47:36] <bleathem> edburns: that's fantastic, I didn't know nexus had that feature! [17:47:36] *** aslak has quit IRC [17:47:45] <bleathem> edburns: works well for me, following your instructions [17:47:51] <bleathem> I'll review today [17:48:03] *** aslak has joined #seam-dev [17:49:33] *** oranheim has quit IRC [17:49:33] *** oranheim_ is now known as oranheim [17:51:54] <clerum> gastaldi: ? [17:53:38] *** tsurdilo1 has quit IRC [17:54:29] <clerum> gastaldi: oh on the java.util.Date [17:54:33] <gastaldi> yeah [17:57:01] <gastaldi> Is there any metawidget expert in here / [17:57:02] <gastaldi> ? [17:57:14] <gastaldi> I am using Primefaces with Metawidget [17:57:36] <gastaldi> jose_freitas: Have you used both ? [18:01:14] *** maschmid has quit IRC [18:02:36] <oranheim> edburns: will JSF 2.2 become fully HTML5 compliant? [18:04:38] <edburns> oranheim: That is one of the goals. [18:05:21] <oranheim> I think that is a very important goal. Would that mean JSF will adopt and maintain two render kits. One for HTML 4.01 and another for 5? [18:05:29] <clerum> bleathem: I was asking about the maven version. 4.1.0.20110805-M1 looks like the lastest [18:05:56] <oranheim> html 5 would also make a lot of sense to jsf, because more natural/native support for jsf components are found within html5 [18:07:59] *** mgoldmann has quit IRC [18:08:33] *** daniel_hinojosa has quit IRC [18:08:34] <clerum> oranheim: http://www.jcp.org/en/jsr/detail?id=344 [18:09:41] <bleathem> clerum: indeed it is [18:09:52] <bleathem> clerum: we timestamp the milestone releases [18:10:02] <bleathem> clerum: the CR and Final releases won't have timestamps [18:10:04] <oranheim> I was hoping for some more ambitions that this: [18:10:04] <oranheim> * Support for select HTML5 features, possibly including the following. [18:10:05] <oranheim> o HTML5 Forms (Flow and Interactive content models) [18:10:05] <oranheim> o HTML5 Heading and Sectioning content model [18:10:05] <oranheim> o HTML5 Metadata content model [18:10:11] <clerum> so there could be multiple M1 releases? [18:10:34] <bleathem> clerum: not multiple public ones, but multiple internal ones [18:10:41] <bleathem> clerum: we have an extensive QE process [18:10:44] <clerum> ah ok makes sense [18:11:06] <clerum> so I don't need to monitor for a version change until M2 is annoucned [18:11:08] <bleathem> clerum: and the effort to drop the timestamp once QE has approved isn't really justifiable for milestone releases [18:11:15] <bleathem> clerum: correct [18:11:43] <clerum> bleathem: has anyone mentioned that they miss the links to the tag reference on the show case? [18:11:52] <clerum> it's killing me [18:11:54] *** daniel_hinojosa has joined #seam-dev [18:11:57] <bleathem> ah [18:12:00] <clerum> was unaware how much I used that [18:12:21] <bleathem> file a jira, I'll see if I can get that in for M2 [18:12:26] <clerum> will do [18:12:55] <clerum> I strayed to primefaces for a bit but I'm loving RF4 [18:13:07] <bleathem> clerum: have you seen this: http://docs.jboss.org/richfaces/latest_4_0_X/vdldoc/ [18:13:12] <clerum> not as pretty in default style but more more predictable [18:13:16] *** tsurdilo has joined #seam-dev [18:13:26] <clerum> bookedmarked [18:13:39] <clerum> thats what I was looking for [18:13:43] <bleathem> clerum: style is going to be a big issue for us in 4.2 [18:14:08] <bleathem> clerum: cool, it's a nice doc (auto generated) [18:14:19] <clerum> great I think it drives a lot of users to primefaces [18:14:24] <bleathem> clerum: but we could (should?) link to it from the showcase [18:14:30] <clerum> should [18:14:36] <clerum> I'll file a jira [18:14:43] <bleathem> great, thanks! [18:17:56] *** fiorenzino has left #seam-dev [18:18:08] <gastaldi> Damn, I am starting to hate Primefaces [18:18:11] <gastaldi> :P [18:18:24] <gastaldi> At least with MetaWidget :) [18:18:38] *** balunasj has joined #seam-dev [18:34:26] *** jamezp_afk has quit IRC [18:34:46] *** alesj has quit IRC [18:35:03] *** lazarotti has quit IRC [18:39:48] *** jamezp has joined #seam-dev [18:43:34] *** ssachtleben has joined #seam-dev [18:44:33] *** oranheim_ has joined #seam-dev [18:46:03] *** akazakov has joined #seam-dev [18:47:33] *** oranheim has quit IRC [18:47:48] *** oranheim has joined #seam-dev [18:48:55] *** oranheim_ has quit IRC [18:56:44] *** daniel_hinojosa has quit IRC [19:00:06] *** koentsje has joined #seam-dev [19:01:46] *** daniel_hinojosa has joined #seam-dev [19:12:18] <gastaldi> Anyone here worked on MetaWidget or know who may help ? :P [19:13:16] *** oranheim_ has joined #seam-dev [19:14:37] *** oranheim has quit IRC [19:14:37] *** oranheim_ is now known as oranheim [19:39:01] *** balunasj has quit IRC [19:40:24] *** oranheim_ has joined #seam-dev [19:41:21] <clerum> gastaldi: is metawidget like a crud component for entities? [19:41:54] <gastaldi> Kinda [19:41:57] <gastaldi> yeah [19:42:11] *** oranheim has quit IRC [19:42:12] *** oranheim_ is now known as oranheim [19:42:17] <gastaldi> But it renders the form fields only [19:42:33] <gastaldi> And you can configure it to use Primefaces, Richfaces, etc [19:42:47] [19:43:03] *** rruss has quit IRC [19:48:05] *** aslak has quit IRC [19:53:12] *** lazarotti has joined #seam-dev [19:55:45] <bleathem> gastaldi: I know lincoln has experience with meta-widget via Forge [19:56:47] [19:57:03] <gastaldi> Now I want primefaces OR richfaces working with it [19:57:33] <gastaldi> But it seems it rips off the <script> tags on the head [19:59:09] *** emmanuel has joined #seam-dev [20:02:54] *** sannegrinovero has quit IRC [20:08:21] *** bitshuffler has joined #seam-dev [20:16:36] *** daniel_hinojosa has quit IRC [20:24:04] *** jamezp has quit IRC [20:31:08] *** daniel_hinojosa has joined #seam-dev [20:33:43] *** clerum has quit IRC [20:35:38] *** clerum has joined #seam-dev [20:39:17] *** jamezp has joined #seam-dev [20:48:22] *** nilian has joined #seam-dev [20:52:04] *** bleathem is now known as bleathem_away [20:56:17] *** lightguard_jp has joined #seam-dev [21:12:38] *** lazarotti has quit IRC [21:19:06] *** rruss has joined #seam-dev [21:20:35] *** rruss has quit IRC [21:20:41] *** rruss has joined #seam-dev [21:22:42] *** rruss has quit IRC [21:22:48] *** rruss has joined #seam-dev [21:38:40] *** gastaldi has quit IRC [21:42:26] *** jganoff has quit IRC [21:43:44] *** mbg is now known as mbg|away [21:45:42] *** cbrock has joined #seam-dev [21:47:02] *** jganoff has joined #seam-dev [21:53:17] *** lazarotti has joined #seam-dev [22:00:41] *** nilian has quit IRC [22:02:39] *** cbrock has quit IRC [22:05:39] *** cbrock has joined #seam-dev [22:10:27] *** sgilda has quit IRC [22:10:42] *** bitshuffler has quit IRC [22:10:55] *** sgilda has joined #seam-dev [22:16:58] *** mbg|away is now known as mbg [22:19:14] *** bleathem_away is now known as bleathem [22:26:10] *** johnament has joined #seam-dev [22:31:03] *** nilian has joined #seam-dev [22:33:34] *** maschmid has joined #seam-dev [22:35:23] *** rmartinelli has quit IRC [22:54:05] *** koentsje has quit IRC [22:56:13] *** nilian has quit IRC [23:05:14] *** ChanServ sets mode: +o lightguard_jp [23:05:19] *** lightguard_jp sets mode: +o jbott [23:05:55] <sbryzak> morning guys [23:06:04] *** mojavelinux has joined #seam-dev [23:06:16] <jose_freitas> evening sbryzak [23:06:17] <lightguard_jp> Morning Shane [23:06:26] <lightguard_jp> Hey mojavelinux [23:06:30] <johnament> good afternoon sbryzak [23:06:34] <lightguard_jp> Also a big hello to everyone else :) [23:06:39] <jose_freitas> I smell some nice discussions today :) [23:06:40] <clerum> hello [23:06:49] <johnament> i brought my knife [23:06:58] <sbryzak> that's not a knife [23:07:02] <johnament> this is totally going to be greasers vs. soc's [23:07:04] <lightguard_jp> Shall we start? [23:07:20] <lightguard_jp> #startmeeting [23:07:20] <jbott> Meeting started Wed Aug 17 21:00:55 2011 UTC. The chair is lightguard_jp. Information about MeetBot at http://wiki.debian.org/MeetBot. [23:07:20] <jbott> Useful Commands: #action #agreed #help #info #idea #link #topic. [23:07:29] <lightguard_jp> #chair sbryzak mojavelinux [23:07:29] <jbott> Current chairs: lightguard_jp mojavelinux sbryzak [23:07:50] <lightguard_jp> Welcome everyone to the meeting. [23:07:53] *** kenfinnigan has joined #seam-dev [23:08:00] <lightguard_jp> Ah, great, you made it Ken! [23:08:01] <kenfinnigan> Hey all [23:08:18] <kenfinnigan> On my phone so may be slow to respond! [23:08:34] <lightguard_jp> We will have some great topics to talk about and finalize today. [23:09:01] <sbryzak> let's get into it, what's first on the agenda? [23:09:04] <lightguard_jp> As I hope you've seen we'll be talking about Logging (things have changed in Seam 3.1) and Testing [23:09:11] <lightguard_jp> #topic Logging [23:09:11] *** jbott changes topic to "Logging" [23:09:27] <lightguard_jp> sbryzak: Would you like to explain what's going on? [23:09:32] <sbryzak> yep, sure [23:09:35] *** jganoff has quit IRC [23:09:37] <lightguard_jp> I think you probably understand it best [23:10:03] <sbryzak> so first of all, everyone should know that the logging api has been changed as part of SOLDER-102 [23:10:05] <jbossbot> jira [SOLDER-102] Change way in which JBoss Logging is embedded [Resolved (Done) Enhancement, Major, Ken Finnigan] https://issues.jboss.org/browse/SOLDER-102 [23:10:35] <sbryzak> what i'd like to do, is split the logging functionality out into its own module [23:11:00] <sbryzak> ken, sorry to make you type, but can you confirm that this change was for the benefit of typesafe logging? [23:11:42] <kenfinnigan> The main reason for that change was to alter the package naming of the imported jboss-logging [23:11:43] <jose_freitas> hmm, that's a great idea. [23:12:19] <kenfinnigan> And including logging was to prevent the need for dev's to include it [23:12:36] <kenfinnigan> Type safe logging is done in solder proper [23:12:44] <sbryzak> ok, so i think that to make it more intuitive for our users, we should move it into its own module and rename the package to org.jboss.seam.logging [23:13:00] *** hannelita_ has joined #seam-dev [23:13:06] <sbryzak> can we move the typesafe logging feature into the logging module? [23:13:09] <kenfinnigan> The type safe stuff or the jboss logging import? [23:13:14] <sbryzak> both [23:13:25] <sbryzak> anything to do with logging i'd like to split out [23:13:48] <kenfinnigan> You'd still need to two separate modules [23:14:07] <kenfinnigan> As you need to re brand the jboss import before u use it [23:14:24] <lightguard_jp> kenfinnigan: Couldn't we shade it like we're doing now in solder logging? [23:14:38] <sbryzak> i was about to ask that, can we shade it into the seam-logging jar? [23:14:55] <kenfinnigan> Yes, but the type safe stuff uses the logger being imported [23:15:03] <kenfinnigan> So for it to compile u need two jars [23:15:07] <kenfinnigan> The shaded one [23:15:17] <kenfinnigan> And then one with the type safe code [23:15:23] <lightguard_jp> Ah [23:15:30] <kenfinnigan> You could shade them together at that point [23:15:41] <kenfinnigan> But u need to start with two [23:15:59] <sbryzak> i don't quite understand the problem.. can we not just have jboss-logging as a compile time dependency? [23:16:14] <kenfinnigan> We wanted to avoid that dep [23:16:29] <sbryzak> it wouldn't need to be a dependency of the shaded jar though [23:17:02] <kenfinnigan> Now I'm confused [23:17:25] <kenfinnigan> Jboss logging is a dep of the shade module to enable it to shade [23:17:49] <kenfinnigan> But then it is no longer a dep to anything that uses solder, as it currently stands [23:18:15] <sbryzak> sorry i meant a transitive dependency [23:18:29] <kenfinnigan> So we wanted to avoid jboss logging being a trans dep of solder [23:18:52] <sbryzak> that's fine, it would still be our goal for seam-logging [23:18:56] <kenfinnigan> As we wanted solder to be the bottom of the dep tree [23:19:25] <kenfinnigan> Have no prob with pulling logging out of solder and have it dep on new module [23:19:25] <sbryzak> anyway, what i'll do is spend some time setting this up and trying to get the dependencies right [23:20:01] <sbryzak> if no-one else has any issues with this, let's move on to the next item [23:20:08] <kenfinnigan> Could have some time to help if needed [23:20:24] <lightguard_jp> Okay, everyone good with that? [23:20:26] <sbryzak> i'd rather have your help with the next topic ;) [23:20:27] <maschmid> We should also make it work somehow so we don't need to put stuff into our MANIFEST for AS7.... otherwise that is no better than a compile time dependency on logging... [23:20:31] <lightguard_jp> Trying to put something in the minutes about this :) [23:20:51] <sbryzak> maschmid: that's a good idea.. stuartdouglas, is this possible? [23:21:28] <stuartdouglas> I just woke up, what are we talking about? [23:21:35] <lightguard_jp> #info logging will be pulled out of solder, and into it's own module. [23:21:53] <sbryzak> having the Dependencies stuff automatically taken care of by a seam-logging module [23:22:13] <sbryzak> stuartdouglas: what maschmid said [23:22:31] <stuartdouglas> if the seam-logging module has a Dependencies: entry in the manifest it will still work [23:22:39] <stuartdouglas> you only need the entry in one jar [23:22:56] <sbryzak> awesome, that's good news [23:23:02] <johnament> sbryzak: that makes 20 modules [23:23:03] <sbryzak> it will save our users a lot of trouble [23:23:16] <lightguard_jp> Sounds like we could do an AS7, AS6, etc classifier on those and add the needed bits in the manifest. [23:23:18] <sbryzak> johnament: i know, i've been counting them slowly over the last week ;) [23:24:04] <sbryzak> so, i believe the next item was testing? [23:24:28] <lightguard_jp> Yes [23:24:30] <lightguard_jp> #info Testing [23:24:46] <lightguard_jp> We've certainly hit some issues with testing in the Beta1 release. [23:24:52] <sbryzak> ok, well before we go any further, i should let everyone know that we're not releasing Beta1 [23:25:11] <sbryzak> we're going to keep it a private release, and aim at releasing Beta2 as a public release [23:25:32] <kenfinnigan> Does that push back all releases by a week? [23:25:34] <sbryzak> beta1 has served to highlight that we have a lot of issues that need fixing [23:25:42] <sbryzak> i'd say closer to 2 weeks [23:25:50] <kenfinnigan> Ok [23:25:54] <sbryzak> it's unfortunate, but i want to get things right [23:26:09] <sbryzak> the biggest issue is the broken tests [23:26:22] <lightguard_jp> We need to focus on getting our testing correct for Beta2. Do our best at getting the new testing structure in place for modules. [23:26:32] <sbryzak> since we released seam 3.0.0.Final, arquillian and shrinkwrap have both undergone a number of changes [23:26:53] <sbryzak> and those changes have pretty much broken all of our tests [23:27:11] <sbryzak> so, i really like the way ken has set up the test suite in the international module [23:27:12] <lightguard_jp> Most of those changes are fairly easy to fix, some api relocations [23:27:17] <johnament> sbryzak: agreed [23:27:22] <johnament> lightguard_jp: disagreed [23:27:24] <lightguard_jp> the arquillian.xml has changed a little bit [23:27:34] <sbryzak> i want to use ken's work as inspiration to standardise all modules on the same testing structure [23:27:50] <sbryzak> the container boms will all be moved to seam-parent [23:28:03] <kenfinnigan> Cool [23:28:36] <sbryzak> or possibly into a separate, testing module.. the first choice is into parent though [23:28:50] <jose_freitas> so, how could we choose the container again in that structure?? [23:28:51] <sbryzak> so, we have a few tasks to achieve this [23:29:00] <jose_freitas> ops. twice ? was a typo [23:29:15] <sbryzak> jose_freitas: check out the international module [23:29:34] <sbryzak> https://github.com/seam/international/tree/develop/testsuite [23:29:49] <lightguard_jp> Catch is also using it. [23:29:58] <sbryzak> one thing i'd like to do is get rid of the intermediate poms [23:30:15] <sbryzak> e.g. internals/pom.xml [23:30:29] <jose_freitas> thanks sbryzak [23:30:40] <sbryzak> but i really like the layout [23:30:46] <sbryzak> so, tasks for this [23:30:59] <sbryzak> i need to update seam-parent and set up the new container boms [23:31:08] <kenfinnigan> And would testsuite refer to the underlying internals/jboss pom? [23:31:10] <sbryzak> we need someone to put together some documentation for testing [23:31:35] <sbryzak> kenfinnigan: yes [23:31:55] <sbryzak> we really need good documentation for this [23:32:07] <sbryzak> we need to document clearly how the test suite is structured and configured [23:32:20] <sbryzak> we need to document how a seam user can create their own tests [23:32:31] <sbryzak> in fact i think we need to include a chapter in the reference guide [23:32:38] <kenfinnigan> Is there a particular reason to remove that pom? [23:33:06] <kenfinnigan> In the future I would see other modules at internals level like cluster or API,etc [23:33:11] <sbryzak> kenfinnigan: it's just an aggregator pom, right? can't we just list the modules directly in testsuite/pom.xml? [23:33:33] <kenfinnigan> Having that pom means u could then run all the cluster tests for a module [23:33:46] <sbryzak> we can achieve that with profiles [23:33:57] <kenfinnigan> Yes, depends on how much control we want over running test types [23:34:01] <sbryzak> i.e. have a cluster profile, api profile etc [23:34:19] <sbryzak> i'd just really like to cut down on the number of poms we have, it means less maintenance [23:34:23] <lightguard_jp> You'd have to do multiple invocations to run all the tests with profiles. [23:34:45] <sbryzak> lightguard_jp: i'm sure you could run them all in one go [23:34:54] <kenfinnigan> Wouldn't that get just as messy as before in terms of having to include/exclude tests [23:35:05] <lightguard_jp> Depends on what servers are being used for arquillian. [23:35:21] <kenfinnigan> Ie sep tests would have to be written for a cluster [23:35:37] <sbryzak> let's not worry about the particulars for now, we can work out the details over the next week [23:35:50] <sbryzak> what i would like for though is a volunteer to work on the documentation for this [23:36:34] <lightguard_jp> If someone would like to migrate their module(s) to the new structure Ken and I can help. [23:36:43] <sbryzak> great [23:36:43] <lightguard_jp> That may be a better way to get ideas about what needs to be documented. [23:36:52] <sbryzak> i'm going to get QA to help with this also [23:36:59] <sbryzak> next week when ondrej is back from pto [23:36:59] <kenfinnigan> Good idea [23:37:13] <lightguard_jp> Going from a fresh start would uncover issues Ken and I forgot about when we did it. [23:37:25] <clerum> I'm definitily going to need help getting mail converted [23:37:50] <sbryzak> clerum: no problem, we're going to be doing all the modules [23:37:56] <kenfinnigan> Would also be different than what we did once container boms are in parent [23:38:12] <lightguard_jp> kenfinnigan: That's true. [23:38:35] <lightguard_jp> clerum: I think docs for mail should be done first, they take the most time :) [23:38:36] <sbryzak> i propose we use org.jboss.seam.test:container-bom-as7 as the artifact ids [23:39:13] <clerum> Should I refactor everything module wise before you do the test work? [23:39:20] <kenfinnigan> Would be good to have all modules move to tests with parent container boms soon [23:39:24] <sbryzak> and while we're talking about parent, i'm also going to be removing the dependency we have on weld-parent [23:39:39] <kenfinnigan> Then we could ensure parent is released with boms that don't have problems [23:39:56] <sbryzak> agreed [23:40:06] <sbryzak> i'm make that my number one priority [23:40:06] <kenfinnigan> There may be missing deps in boms from what catch and i18n use that need to be added [23:40:31] <kenfinnigan> Good call on the weld-parent removal [23:40:39] <kenfinnigan> Was thinking about that the other week [23:40:51] <kenfinnigan> Has a lot in that we don't need [23:40:56] <kenfinnigan> And it doesn't update often [23:41:00] <sbryzak> lightguard_jp: what did we have next on the agenda? [23:41:11] <sbryzak> kenfinnigan: true, and most of the plugins are out of date [23:41:35] <lightguard_jp> That's it, unless we want to bring up the dependency discussion here in IRC from the mailing list [23:41:37] <kenfinnigan> yep [23:42:03] <sbryzak> actually there's that and wicket [23:42:36] <lightguard_jp> Okay, we've got the time. [23:42:44] <sbryzak> so with the dependencies, i'm happy with having to tell our users they need to configure two dependencies for the api and impl [23:42:49] <lightguard_jp> #info weld parent will be removed [23:42:49] <sbryzak> but... [23:42:57] <sbryzak> i think we should then rename the implementation [23:43:00] <lightguard_jp> #info we'll be focusing on testing and getting modules up to date [23:43:11] <lightguard_jp> #info we need some documentation about testing in seam [23:43:15] <mojavelinux> rename the impl to....? [23:43:28] <sbryzak> one of the goals when we removed the shaded jar was to not break people's builds [23:43:34] <lightguard_jp> #topic dependency discussion from the mailing list [23:43:34] *** jbott changes topic to "dependency discussion from the mailing list" [23:43:37] <sbryzak> however we've done exactly that [23:43:48] <sbryzak> by making the implementation runtime scoped [23:43:53] <sbryzak> which i have no problem with at all [23:44:04] <sbryzak> but to avoid confusion, i think we should just rename the impls back to what they were [23:44:16] <sbryzak> so, seam-catch-api, and seam-catch-impl [23:45:05] <sbryzak> the previous idea of renaming the implementation to remove the suffix was to prevent breakage [23:45:13] <sbryzak> but since we're not preventing it, there's no point in the rename now [23:45:25] <sbryzak> anyone disagree? [23:46:03] <mojavelinux> well, I guess the counter argument is that they could still just add seam-catch [23:46:07] <mojavelinux> and it would do the right thing [23:46:08] <jose_freitas> and what about having a bom to import? [23:46:16] <mojavelinux> bom imports are horrible, I've tried it [23:46:22] <sbryzak> it wouldn't do the right thing, unless they override the scope [23:46:35] <mojavelinux> they just don't quite work how you would want them to, and it ends up just looking weird [23:46:42] <mojavelinux> I still dont' get why [23:46:49] <mojavelinux> consider this for a moment [23:46:53] *** tsurdilo has quit IRC [23:46:56] <sbryzak> because the impl is set to runtime scope in seam-bom [23:46:59] <mojavelinux> if you add seam-catch [23:47:11] <sbryzak> which means if you use the catch api classes in your app, you get a compiler error [23:47:13] <mojavelinux> seam-catch is runtime, but it has a dependency on seam-catch-api which is compile time [23:47:21] <sbryzak> no, it doesn't work that way [23:47:31] <mojavelinux> I think it does, if you have your dependency management correct [23:47:39] <sbryzak> if it's runtime, then its transitive dependencies are ignored at compile time [23:47:52] <mojavelinux> only if you manually set runtime in your build [23:48:01] <sbryzak> no, the runtime scope is inherited from the bom [23:48:05] <mojavelinux> dependency management should override that [23:48:14] <mojavelinux> right, but the api is set to compile scope [23:48:15] <sbryzak> you need to manually set it to compile [23:48:15] *** emmanuel has quit IRC [23:48:32] <mojavelinux> maven is just ignorant then, if it doesn't work that way (but I still hold out that it is supposed to work that way) [23:48:37] <sbryzak> yes, but it's ignored altogether because the dependency that it's a transitive of (the impl) is runtime [23:48:58] <sbryzak> it most definitely doesn't work that way, i've spent the last week proving it ;) [23:49:00] <mojavelinux> i'm so sick of maven, i swear it [23:49:06] <jose_freitas> hehee [23:49:29] <sbryzak> i agree, if we could get maven to do what we want instead of what it wants, it would make life easier [23:49:40] <lightguard_jp> haha [23:49:44] <lightguard_jp> Good luck with that :) [23:49:52] <mojavelinux> the fact that maven doesn't work this way proves to me that they simply don't understand software development [23:50:09] <sbryzak> so, in light of how much maven sucks, i'd like to rename the implementations to seam-foo-impl [23:50:12] <mojavelinux> fine [23:50:23] *** hannelita_ has quit IRC [23:50:39] <sbryzak> my dream is to still move all this stuff to gradle one day [23:50:50] <lightguard_jp> Actually, I'm okay with this change, we've done poorly with documentation anyway so whatever we tell people now they'll use. I think people that are using Seam 3 now are still "early adopters" [23:50:53] <sbryzak> although, we'll still be playing by maven's dependency rules i guess [23:51:25] <sbryzak> this will require a documentation change, but it should be minor [23:51:34] <hannelita> Maven sucks, but I think its the best option we have. [23:51:47] <sbryzak> i'm not sure if george got round to updating the docs [23:51:54] <lightguard_jp> I don't think he did. [23:52:03] <sbryzak> hmm, where is he.. i was wondering why it was quiet in here [23:52:12] <lightguard_jp> Are we going to do this for Beta2 as well? [23:52:17] <mojavelinux> i think gradle is the best option, because it does dep management right [23:52:18] <sbryzak> yes [23:52:30] <mojavelinux> or, at least, it allows you to set it the way you want it to work [23:52:41] <mojavelinux> but I acknowledge maven is a fact of life [23:52:43] <lightguard_jp> Okay, so the two tasks for Beta2 are testing and maven dep / rename change? [23:52:59] <sbryzak> and logging [23:53:02] <jose_freitas> mojavelinux: sbryzak on the way that maven does things. and I don't agree that it should resolve compile dependency from a runtime dependency. [23:53:03] <mojavelinux> it just makes me irritated that the rules by which the dep management works are simply ass backwards [23:53:29] <jose_freitas> IMHO [23:53:46] <lightguard_jp> #info Beta2 tasks: testing update / restructure, maven dep / rename change and logging change [23:53:56] <sbryzak> so the last hot topic of discussion on seam-dev was wicket [23:54:06] <lightguard_jp> #topic wicket discussion [23:54:06] *** jbott changes topic to "wicket discussion" [23:54:16] <sbryzak> i love the idea of cdi support moving to the wicket project [23:54:26] <sbryzak> if we could help to make that happen, i think it would be a win [23:54:44] <lightguard_jp> It certainly follows what we're doing internally with JBoss projects. [23:54:57] <mojavelinux> but I agree with ove that we should not lose the ability for the seam community to contribute ideas to it [23:55:14] <sbryzak> for sure, and it's actually one of our biggest goals with seam, to promote cdi everywhere [23:55:22] *** maschmid has quit IRC [23:55:42] <sbryzak> mojavelinux: i also agree with that, but i think we can address it with documentation [23:56:09] <oranheim> I agree with you on CDI everywhere, but wicket is a web framework and should be aligned with solder/servlet and promote a consent web "glue" layer [23:56:10] <sbryzak> so i don't know if anyone remembers, but one of the things we said we'd do in seam is include chapters in the reference documentation [23:56:18] <lightguard_jp> I think it needs to be more of a partnership, not a divorce of the module and the maintainers. [23:56:21] <sbryzak> for other cdi-integrated products [23:56:49] <jose_freitas> +1 on lightguard_jp statement [23:57:05] <sbryzak> oranheim: solder is certainly a useful set of utilities, but we can make it a requirement of every other cdi integration effort [23:57:13] <sbryzak> i'm pretty sure errai doesn't use it [23:57:38] <sbryzak> can't i mean [23:58:04] <lightguard_jp> Errai is a little different because of it's focus on client side [23:58:15] <oranheim> sbryzak: i see your point, but then solder eco-system will be 99% jsf oriented then [23:58:29] <sbryzak> errai was just an example, there's also drools, infinispan, etc [23:58:41] <sbryzak> more and more projects are taking on cdi integration [23:59:01] <sbryzak> solder isn't really oriented to any particular view platform [23:59:17] <mojavelinux> I do think their cdi integration should use solder and the conversation module [23:59:46] <sbryzak> definitely the conversation module, although that's a band-aid fix until cdi 1.1 comes out [23:59:48] <oranheim> so since solder isn't oriented on a particular platform, it should be promoted further than just cdi [23:59:56] <oranheim> same with servlet