[00:19:48] *** balunasj has quit IRC
[00:20:10] *** balunasj has joined #seam-dev
[00:22:28] *** balunasj has quit IRC
[01:02:29] *** lightguard_jp has quit IRC
[01:04:40] *** maxandersen1 has quit IRC
[01:44:25] <jbossbot> git [forge] push master 4885282.. Lincoln Baxter, III Merge branch 'master' of http://github.com/mikebrock/seam-forge
[01:44:26] <jbossbot> git [forge] push master e4394dc.. Lincoln Baxter, III ListFacetsPlugin now displays when facets are no longer available, but are registered. ConstraintEnforcer now takes into account when facets are registered but in an inconsistent state - plugins depending on such facets will not be available.
[01:44:26] <jbossbot> git [forge] push master URL: http://github.com/seam/forge/compare/0bb7a79...e4394dc
[01:47:48] *** sannegrinovero has quit IRC
[01:48:58] *** mbg has joined #seam-dev
[01:48:59] *** mbg has quit IRC
[01:48:59] *** mbg has joined #seam-dev
[01:54:40] *** mbg has quit IRC
[01:55:22] *** mbg has joined #seam-dev
[01:55:22] *** mbg has quit IRC
[01:55:22] *** mbg has joined #seam-dev
[02:00:23] *** mbg has quit IRC
[02:14:22] *** tsurdilo has quit IRC
[02:16:18] *** aslak has quit IRC
[02:17:06] *** cbrock has quit IRC
[03:11:16] *** kenfinnigan has joined #seam-dev
[03:13:43] *** jganoff has joined #seam-dev
[03:17:34] <jganoff> Is there any way to register an ObserverMethod outside of an extension?
[03:18:04] <jganoff> or rather, outside of any of the callback events, e.g. AfterBeanDiscovery
[03:20:30] *** alesj has quit IRC
[03:31:42] *** jganoff has quit IRC
[03:40:11] *** johnament has joined #seam-dev
[03:46:08] *** alesj has joined #seam-dev
[03:57:35] *** johnament has quit IRC
[04:09:43] *** kenfinnigan has left #seam-dev
[04:58:35] *** bleathem has joined #seam-dev
[05:11:07] *** cbrock has joined #seam-dev
[05:14:29] <bleathem> I went OCD on the Seam Faces logo, I think it's ready for upload.
[05:14:39] <bleathem> Too bad sfwk.org isn't responding...
[05:14:43] <bleathem> too many requests
[05:15:08] <bleathem> sweet, I'm in!
[05:25:13] <bleathem> D'oh, I don't have permissions to upload the Seam Faces emblem...
[06:09:53] *** alesj has quit IRC
[06:11:11] *** alesj has joined #seam-dev
[06:20:39] *** tsurdilo has joined #seam-dev
[06:24:24] *** bleathem has quit IRC
[06:38:41] *** lincolnthree has quit IRC
[06:53:42] *** lightguard_jp has joined #seam-dev
[07:05:36] *** cbrock has quit IRC
[07:30:22] *** lightguard_jp has quit IRC
[07:34:51] *** alesj has left #seam-dev
[07:34:54] *** alesj has quit IRC
[07:40:10] *** oskutka has joined #seam-dev
[07:40:52] *** lightguard_jp has joined #seam-dev
[07:50:39] *** oskutka has quit IRC
[07:51:30] *** oskutka has joined #seam-dev
[07:59:03] *** tsurdilo has quit IRC
[08:01:19] *** lightguard_jp has quit IRC
[08:10:51] *** clerum has quit IRC
[08:21:02] *** lukaszlenart has joined #seam-dev
[08:23:30] *** amitev has quit IRC
[08:39:21] *** koentsje has joined #seam-dev
[08:54:28] *** mgencur has joined #seam-dev
[08:57:12] *** jharting has joined #seam-dev
[09:06:41] *** maxandersen has joined #seam-dev
[09:15:56] *** kpiwko has joined #seam-dev
[09:15:59] *** amitev has joined #seam-dev
[09:28:38] *** shervin_a has joined #seam-dev
[09:34:19] <shervin_a> Whatever happened to the patch by stuartdouglas to implement REQUIRES_NEW on @Transactional? http://old.nabble.com/Implementing-REQUIRES_NEW-for-seam-transaction-management-td25219048.html
[09:52:58] *** marekn has joined #seam-dev
[09:52:58] *** marekn has left #seam-dev
[09:54:23] *** marekn has joined #seam-dev
[09:57:06] *** amitev has quit IRC
[10:14:15] *** aslak has joined #seam-dev
[10:14:15] *** aslak has quit IRC
[10:15:45] *** amitev has joined #seam-dev
[10:18:15] *** aslak has joined #seam-dev
[10:18:15] *** aslak has quit IRC
[10:18:15] *** aslak has joined #seam-dev
[10:33:09] *** emmanuel has joined #seam-dev
[10:36:31] *** nickarls has quit IRC
[10:37:51] *** nickarls has joined #seam-dev
[11:02:22] *** akazakov has joined #seam-dev
[11:38:59] *** sannegrinovero has joined #seam-dev
[11:59:52] *** sannegrinovero has quit IRC
[12:06:15] *** emmanuel has quit IRC
[12:27:13] *** maxandersen has quit IRC
[12:28:54] *** maxandersen has joined #seam-dev
[12:35:10] *** adamw1pl has joined #seam-dev
[12:47:49] *** sannegrinovero has joined #seam-dev
[13:09:27] *** aslak has quit IRC
[13:10:16] *** aslak has joined #seam-dev
[13:13:21] *** aslak has quit IRC
[13:18:49] *** akazakov has quit IRC
[13:20:01] *** akazakov has joined #seam-dev
[13:29:58] *** aslak has joined #seam-dev
[13:34:09] *** epbernard has joined #seam-dev
[13:34:09] *** epbernard is now known as emmanuel
[13:40:56] *** jdlee has quit IRC
[13:48:38] *** sannegrinovero has quit IRC
[13:50:59] *** balunasj has joined #seam-dev
[13:56:55] *** maxandersen is now known as max_movingsnow
[14:42:09] *** lincolnthree has joined #seam-dev
[14:50:09] *** nickarls has quit IRC
[14:52:48] *** jose_freitas has quit IRC
[14:53:54] *** balunasj is now known as balunasj_focused
[14:54:11] *** jose_freitas has joined #seam-dev
[15:01:31] *** max_movingsnow is now known as maxandersen
[15:01:52] <jbossbot> git [rest] push master 37b8caf.. Jozef Hartinger Show correct project version in ref docs
[15:01:52] <jbossbot> git [rest] push master 4aee95d.. Jozef Hartinger Minor docs changes
[15:01:53] <jbossbot> git [rest] push master 2e5a394.. Jozef Hartinger Add release notes for alpha3
[15:01:53] <jbossbot> git [rest] push master URL: http://github.com/seam/rest/compare/3af74d4...2e5a394
[15:10:44] <jbossbot> git [rest] push master 5c65917.. Jozef Hartinger Oops
[15:10:44] <jbossbot> git [rest] push master URL: http://github.com/seam/rest/compare/2e5a394...5c65917
[15:10:57] <lincolnthree> jharting: "Oops
[15:11:01] <lincolnthree> is my favorite commit message
[15:11:03] *** sannegrinovero has joined #seam-dev
[15:11:13] <jharting> lincolnthree: :-)
[15:15:11] *** clerum has joined #seam-dev
[15:16:33] *** pmuir has joined #seam-dev
[15:45:41] <jbossbot> git [rest] push master c0462ed.. Jozef Hartinger Add the jaxrs-exceptions example to the dist
[15:45:41] <jbossbot> git [rest] push master URL: http://github.com/seam/rest/compare/5c65917...c0462ed
[15:47:18] *** jharting has quit IRC
[15:51:02] *** kpiwko has quit IRC
[15:59:45] *** pmuir has quit IRC
[16:00:36] *** jdlee has joined #seam-dev
[16:00:36] *** jdlee has joined #seam-dev
[16:00:57] *** balunasj_focused is now known as balunasj_mtg
[16:02:02] *** oskutka has quit IRC
[16:06:13] *** bdlink has joined #seam-dev
[16:06:32] *** oskutka has joined #seam-dev
[16:09:17] *** jharting has joined #seam-dev
[16:37:24] *** lightguard_jp has joined #seam-dev
[16:37:37] *** adamw1pl has quit IRC
[16:49:38] *** jganoff has joined #seam-dev
[16:53:06] *** sannegrinovero has quit IRC
[16:57:21] <jbossbot> git [rest] push master debd532.. Jozef Hartinger [maven-release-plugin] prepare release 3.0.0.Alpha3
[16:57:21] <jbossbot> git [rest] push master 0a05080.. Jozef Hartinger [maven-release-plugin] rollback the release of 3.0.0.Alpha3
[16:57:22] <jbossbot> git [rest] push master URL: http://github.com/seam/rest/compare/c0462ed...0a05080
[16:57:24] *** tsurdilo has joined #seam-dev
[16:57:38] *** bdlink has quit IRC
[17:01:52] *** mbg has joined #seam-dev
[17:02:39] *** sannegrinovero has joined #seam-dev
[17:05:05] <jbossbot> git [rest] push master a767305.. Jozef Hartinger [maven-release-plugin] prepare release 3.0.0.Alpha3
[17:05:05] <jbossbot> git [rest] push master URL: http://github.com/seam/rest/compare/0a05080...a767305
[17:05:05] <jbossbot> git [rest] push master 682d3d4.. Jozef Hartinger [maven-release-plugin] prepare for next development iteration
[17:05:05] <jbossbot> git [rest] push master URL: http://github.com/seam/rest/compare/a767305...682d3d4
[17:06:41] *** oskutka has quit IRC
[17:07:09] *** kpiwko has joined #seam-dev
[17:07:38] *** koentsje has quit IRC
[17:11:32] *** bleathem has joined #seam-dev
[17:11:53] *** kpiwko has quit IRC
[17:21:03] *** marekn has left #seam-dev
[17:28:45] *** wdrai has joined #seam-dev
[17:39:11] *** mgencur has quit IRC
[17:40:53] *** pmuir has joined #seam-dev
[17:45:59] *** lukaszlenart has quit IRC
[17:50:25] <wdrai> hi all. I have a quick question about CDI interceptors. Is it possible to have access to the currently processed Bean object in an interceptor implementation. The invocation context contains only a reference to the target bean instance but not to the Bean. In Seam 2 there was a getComponent() method in AbstractInterceptor.
[17:50:54] <lightguard_jp> I don't think there's a portable way to get to it
[17:52:33] <wdrai> Thanks for your quick answer. Do you think there would be some Weld specific way to get it ?
[17:53:22] <pmuir> no
[17:54:54] <pmuir> I added it as something to consider for CDI 1.1 :-)
[17:54:54] <pmuir> https://issues.jboss.org/browse/CDI-42
[17:54:56] <jbossbot> jira [CDI-42] Allow you to inject the intercepted bean into an Interceptor [Open, Major, Unassigned] https://issues.jboss.org/browse/CDI-42
[17:55:58] <wdrai> Cool, thanks.
[17:56:40] *** lukaszlenart has joined #seam-dev
[18:01:06] *** pmuir has quit IRC
[18:03:21] *** clerum has quit IRC
[18:04:16] *** lukaszlenart has quit IRC
[18:06:34] *** maxandersen is now known as maxandersen_phon
[18:06:40] *** maxandersen_phon is now known as maxandersen_call
[18:18:04] *** sannegrinovero has quit IRC
[18:20:24] *** amitev has quit IRC
[18:34:58] <jose_freitas> I'm tracking down the s:validateForm cause it was not injecting the inputfields right. Stepping inside FormValidationFieldProducer.java I found that it does find the components to inject, it seems to lost its track in weld, though.
[18:35:09] <jose_freitas> does anyone had a similar issue?
[18:36:55] <lightguard_jp> jose_freitas: I think your go to people are going to be lincolnthree and bleathem
[18:37:00] <lightguard_jp> For Faces stuff
[18:41:08] <jose_freitas> thanks lightguard_jp
[18:42:39] *** maxandersen_call is now known as maxandersen
[18:43:49] *** wdrai has left #seam-dev
[19:14:28] *** koentsje has joined #seam-dev
[19:19:50] *** akazakov has quit IRC
[19:24:53] <jganoff> Anyone know if it's possible to register observermethods after initial start up (specifically outside of an Extension) ?
[19:25:09] <lightguard_jp> jose_freitas: np
[19:25:27] <lightguard_jp> jganoff: I doubt it
[19:25:49] <jganoff> lightguard_jp, yea I don't think there's a way.  I want to be able to dynamically add/remove observer methods without re-coding all that logic
[19:26:02] <jganoff> I wonder if I can hold on to the AfterBeanDiscovery reference ;)
[19:26:28] <lightguard_jp> jganoff: Maybe, but changing it probably wouldn't do anything
[19:26:59] <jganoff> Ya, I assume that's not the intended use anyway.  What I want to do is be able to create a new observer at any time.
[19:27:17] <jganoff> without having to recode the scaffolding for doing that - since the cdi impl handles it so well already...
[19:30:25] <lightguard_jp> Probably not :(
[19:30:43] *** jharting has quit IRC
[19:39:48] <jganoff> lightguard_jp, that, unfortunately, makes doing something like: EventBridge.addRoute() a huge pita
[19:40:07] <jganoff> lightguard_jp, since a route is part ObserverMethod, part JMS destination listener
[19:40:13] <lightguard_jp> Right
[19:41:27] <lightguard_jp> Can you have just a generic observer that catches everything and delegate at programattically that way?
[19:42:04] <lincolnthree> I really need to finish my event bus bridge
[19:42:06] <jganoff> lightguard_jp, I could, which is what recoding all the scaffolding of routing events would be.
[19:42:19] <lincolnthree> I think it would help with most of these types of issues with event routing and control
[19:42:19] <lightguard_jp> :(
[19:42:21] <lightguard_jp> Ouch
[19:42:29] <jganoff> lincolnthree, I'd be interesting in chatting about that :)
[19:42:36] <lincolnthree> it's coming up on my agenda soon
[19:42:44] <lincolnthree> jganoff it's in forge atm
[19:42:47] <lincolnthree> very raw though
[19:42:56] <jganoff> lincolnthree, link? :)
[19:43:10] <lincolnthree> most of the harder R&D is done, in terms of getting it to relinquish control from the normal eventing system
[19:43:13] <lincolnthree> incoming
[19:43:26] <lincolnthree> jason hates when i talk about this because it's really just a prototype ;)
[19:43:46] <lincolnthree> https://github.com/seam/forge/tree/master/event-bus
[19:46:39] <lincolnthree> jganoff: I suggest looking at the tests, that's the only place to really see the behavior ATM
[19:46:57] <lincolnthree> if you're interested.. there's plenty to do
[19:48:34] <lightguard_jp> lincolnthree: I understand it, that was most of why I didn't like it. :)
[19:48:41] <lightguard_jp> Implementing it is completely different :)
[19:48:54] <jganoff> lincolnthree, i'll have a look.  Sounds like it would be awfully useful for seam-jms
[19:52:40] <jganoff> lincolnthree, looks nice but I don't see you testing adding new observer methods
[19:52:54] <jganoff> lincolnthree, nor does the extension look like it's doing that - from my 20 second scan :P
[19:53:36] <lincolnthree> ah it doesn't add new observer methods
[19:53:46] <lincolnthree> but it controls existing ones and how they are called
[19:53:47] <lincolnthree> sorry
[19:53:49] <lincolnthree> i misunderstood
[19:54:00] <lightguard_jp> jganoff: Yeah, it workes with the extensions methods
[19:54:07] <lightguard_jp> Not at runtime
[19:55:41] <lightguard_jp> Does Faces Beta2 have the catch integration?
[20:05:49] *** balunasj_mtg is now known as balunasj_away
[20:10:03] *** rruss has joined #seam-dev
[20:13:35] *** emmanuel has quit IRC
[20:34:05] *** epbernard has joined #seam-dev
[20:34:05] *** epbernard is now known as emmanuel
[20:34:56] *** emmanuel has quit IRC
[20:58:37] *** jose_freitas is now known as jose_freitas_afk
[21:02:22] *** tsurdilo has quit IRC
[21:02:48] *** tsurdilo has joined #seam-dev
[21:11:24] *** maxandersen has quit IRC
[21:11:27] *** maxandersen1 has joined #seam-dev
[21:13:41] *** koentsje has quit IRC
[21:19:47] *** cbrock has joined #seam-dev
[21:20:20] *** rruss has quit IRC
[21:20:47] *** rruss has joined #seam-dev
[21:22:30] *** lukaszlenart has joined #seam-dev
[21:56:41] *** lukaszlenart has quit IRC
[22:05:42] *** cbrock has quit IRC
[22:07:41] *** nickarls has joined #seam-dev
[22:13:48] *** cbrock has joined #seam-dev
[22:16:52] *** balunasj_away is now known as balunasj
[22:43:37] *** alesj has joined #seam-dev
[22:43:39] *** cbrock has quit IRC
[22:50:36] *** akazakov has joined #seam-dev
[22:53:17] *** clerum has joined #seam-dev
[23:01:06] *** maxandersen1 has quit IRC
[23:02:25] *** maxandersen has joined #seam-dev
[23:03:38] *** jharting has joined #seam-dev
[23:06:04] *** mojavelinux has joined #seam-dev
[23:06:10] <mojavelinux> hello folks
[23:06:19] <lightguard_jp> Hi all
[23:06:37] <lincolnthree> hola
[23:07:59] <mojavelinux> I'm moving a bit slowly...but hey, maybe that will reduce my lines of chat ;)
[23:08:27] <mojavelinux> a few announcements, as always
[23:08:28] *** mbg has quit IRC
[23:08:44] <lincolnthree> I.. am a computer.
[23:08:44] <mojavelinux> first, welcome brian leathem as module lead for Seam Faces, as you've likely seen already
[23:09:14] <lincolnthree> points at bleathem :)
[23:09:45] <clerum> appears forge is now posting to irc in addtion to pushing to git
[23:10:06] <lincolnthree> [clerum] said "forge" - how can I help you?
[23:10:15] <mojavelinux> oh geez
[23:10:38] <mojavelinux> as you may know, we have an issue with Solder, which we'll discuss shortly
[23:10:39] <lightguard_jp> Moving on ... :P
[23:10:47] <lincolnthree> yes please...
[23:11:00] <mojavelinux> first some smaller stuff
[23:11:33] <mojavelinux> by the first Seam stack release, we've decide to change the code formatting
[23:11:42] <mojavelinux> actually, it's more than just a change, it's an alignment
[23:11:59] <mojavelinux> we are going to use the Java convention, which a few small tweaks that can be considered improvements
[23:12:11] <mojavelinux> which is in fact the code formatting used by AS 7
[23:12:17] <mojavelinux> one of JBoss' newest projects
[23:12:33] <lightguard_jp> Interesting.  Why the change?
[23:12:41] *** maxandersen has quit IRC
[23:12:43] <mojavelinux> the change is for a few reasons
[23:12:52] <lightguard_jp> We should put out a checkstyle format (or just use the sun based one)
[23:13:05] <mojavelinux> we've been asked a number of times, particularly conferences, why we use such a strange format
[23:13:18] <mojavelinux> and we have no answer...meaning no one even knows how we got here
[23:13:55] <mojavelinux> it's different than what most people are used to...particularly a key project in the jboss community
[23:14:03] <mojavelinux> which is AS
[23:14:40] <mojavelinux> and it makes it hard to switch between projects, because you have to adopt this very different style for seam...with so many community members, it makes a lot of sense to go with something most familiar
[23:15:06] <mojavelinux> and the excessive use of endlines in the current scheme makes documentation go long
[23:15:21] <mojavelinux> not to mention I have to reformat all my presentation slides every time I import code
[23:15:50] <mojavelinux> so, if it's not too much of a bother for anyway, we asked that you gradually migrate...but it's not critical atm
[23:15:53] <mojavelinux> just a heads up
[23:16:10] <mojavelinux> I'll import the new profile later on
[23:16:17] <mojavelinux> into git
[23:16:23] <mojavelinux> java 5 vs java 6
[23:16:47] <mojavelinux> we've decided that it's time to get with the program
[23:16:54] <mojavelinux> and reset the baseline to java 6
[23:17:40] <mojavelinux> i've heard the technical argument for why not to use it, and it's just a bunch of excuses
[23:17:43] <mojavelinux> java 5 is eol
[23:17:58] <mojavelinux> so a *new* platform should be based on what is currently supported
[23:18:06] <mojavelinux> and java 6 is the minimum supported model
[23:18:34] <mojavelinux> but there do happen to be technical reasons
[23:18:44] <mojavelinux> annotation processors are not in java 5
[23:18:57] <mojavelinux> there is a nasty cross compile problem in Maven between java 5 and java 6
[23:19:15] <mojavelinux> so you end up breaking things anyway if you try to run on java 5
[23:20:01] <mojavelinux> the service loader, which cdi is based on, isn't even in java 5...so we have to emulate a core JDK feature and that's just ridiculous
[23:20:43] *** jose_freitas has joined #seam-dev
[23:20:46] <mojavelinux> and finally
[23:22:03] <mojavelinux> migrating from java ee 5 to java ee 6 is much more difficult than switching the jdk 6, so if we are expecting shops to go through that migration, it's just make no sense to say, "we'll, it's okay to stay on jdk 5"
[23:22:11] <mojavelinux> anyway, again, unless there are major complaints, let's just move on
[23:22:23] <mojavelinux> something for module leads
[23:22:52] <mojavelinux> when you put @author tags in code, we are now recommending using your jboss community url instead of, or in addition to, your e-mail
[23:23:28] <mojavelinux> first, it will save you from having to put your e-mail address all over the place, though likely you've already been spammed to death so that doesn't matter
[23:24:12] <mojavelinux> but more importantly, it connects your contribution back to the community where people can get in touch with you...it just makes more sense as a link because more information, and updated information, can be stored there
[23:25:39] <mojavelinux> finally, as we near the Seam stack release, I ask module leads to please review your roadmap and at least have a high level overview of where you see your module heading...and which releases you anticipate
[23:25:58] <mojavelinux> this helps us know how to help you...again, if you need help in that regard, please ask
[23:26:10] <mojavelinux> but it should be as straightforward as just updating the table on your module page
[23:26:15] <mojavelinux> or jira
[23:26:32] <mojavelinux> in fact, better is to just scheduled issues for a target release
[23:27:03] <mojavelinux> if you just want to do that and cut down on the use of the roadmap on the module page, I'm open to that idea
[23:27:09] <mojavelinux> whatever is easiest
[23:27:39] <mojavelinux> speaking of the stack release, enough announcements, lets get into chat here (guess I'm not drowsy enough)
[23:27:58] <mojavelinux> the Seam stack beta got put on hold because we have a problem in solder
[23:28:04] <mojavelinux> that problem is that the tests doesn't pass on GlassFish
[23:28:24] <mojavelinux> so, we are all hands on deck the next couple of work days to make that happen
[23:28:51] <lightguard_jp> Hope we can figure that out quickly
[23:28:52] <mojavelinux> the reason for the failures is documented in SOLDER-47 and also CDITCK-205 and CDITCK-206
[23:28:53] <jbossbot> jira [SOLDER-47] Cannot use Solder in Glassfish 3.1 [Open, Blocker, Shane Bryzak] https://issues.jboss.org/browse/SOLDER-47
[23:28:55] <jbossbot> jira [CDITCK-205] Add test to verify extensions in non-bean archives are loaded [Open, Minor, Unassigned] https://issues.jboss.org/browse/CDITCK-205
[23:28:55] <jbossbot> jira [CDITCK-206] Add test to verify visibly of beans registered explicitly through an extension in non-bean archives [Open, Major, Unassigned] https://issues.jboss.org/browse/CDITCK-206
[23:29:06] <mojavelinux> the first steps are as follows
[23:29:28] <mojavelinux> 1. move api classes back into impl/ (perhaps keep api for just the bare minimum annotations)
[23:29:50] <mojavelinux> if that is still causing problems, everything gets moved to impl/
[23:30:07] <mojavelinux> 2. get the tests working on GlassFish
[23:30:13] <lightguard_jp> I'd say just move it all into impl
[23:30:33] <mojavelinux> how about we move them all, then move them back gradually once the tests are passing
[23:30:36] <mojavelinux> if we can do it at all
[23:30:43] <mojavelinux> like for instance, @Veto makes sense in the api
[23:30:45] <lightguard_jp> 1a. Should be to include the beans.xml and remove the extension additions, yes?
[23:30:48] <mojavelinux> as it's just a type
[23:30:56] <mojavelinux> we just can't have beans in api
[23:30:58] <mojavelinux> for now
[23:31:08] <mojavelinux> in other words
[23:31:10] <mojavelinux> api can be annotations
[23:31:20] <mojavelinux> and other non-bean types
[23:31:34] <mojavelinux> but let's start super simple and just say the core annotations
[23:31:45] <mojavelinux> but yes, priority is getting the tests to pass
[23:32:08] <lightguard_jp> Are we going to look at Resin and OWB for this too, or tackle those later?
[23:32:09] <mojavelinux> no, I think we can stick with not using a beans.xml
[23:32:16] <mojavelinux> because that works now on glassfish 3.1-b37
[23:32:23] <mojavelinux> for now, that's our target minimum version
[23:32:27] <lightguard_jp> Resin needs the beans.xml
[23:32:29] <mojavelinux> let's work in steps
[23:32:30] <mojavelinux> ah
[23:32:33] <mojavelinux> shoot
[23:32:38] <mojavelinux> okay, then fine, we can add beans.xml
[23:32:48] <lightguard_jp> I bet we can get them to fix their stuuf easier than Oracle though
[23:32:48] <mojavelinux> but, the question is
[23:32:52] <mojavelinux> do we have a resin profile for testing?
[23:33:00] <lightguard_jp> s/uuf/uff/
[23:33:06] <lightguard_jp> I don't think so
[23:33:12] <mojavelinux> hmmm, let's go in steps then
[23:33:16] <mojavelinux> let's start with no beans.xml
[23:33:17] <lightguard_jp> I don't think there's a container for them yet
[23:33:34] <mojavelinux> esp since Pete so strongly stated that there should have been no misunderstanding about that
[23:33:36] <lightguard_jp> arquillian container*
[23:33:43] <lightguard_jp> lol
[23:33:58] <mojavelinux> there is an arq container for resin, just not in arquillian proper
[23:34:09] <lightguard_jp> Ah
[23:34:10] <mojavelinux> it may be in an opentck repo
[23:34:16] <lightguard_jp> Like the GF 3.1 one :)
[23:34:17] <mojavelinux> we just need to migrate it before arq beta
[23:34:31] <lightguard_jp> We'll have to migrate all the containers before the beta
[23:34:41] <lightguard_jp> The APIs changed
[23:34:46] <mojavelinux> we are going to setup a new git project in arquillian called containers
[23:34:52] <mojavelinux> actually, likely we will have containers-jboss
[23:34:54] <mojavelinux> and containers-thirdparty
[23:35:16] <lightguard_jp> The jboss one will only contain JBoss AS containers?
[23:35:20] <mojavelinux> but we have to touch base w/ aslak about that
[23:35:21] <jose_freitas> mojavelinux, the big challenge to release a version now is the glassfish? or do you still gonna change/add stuff in sea
[23:35:22] <jose_freitas> m
[23:35:42] <mojavelinux> jose we have a fix for the messages that you need for booking coming very soon
[23:35:43] <jose_freitas> by you I mean, the whole team
[23:35:52] <mojavelinux> in fact, ken sent a pull request that's the first step
[23:36:17] <mojavelinux> so we are still adding stuff, it's just that we can't add stuff and not fix the glassfish compatibility
[23:36:23] <lightguard_jp> jose_freitas: The Seam stack release should be anything that's currently beta (may be a few exceptions)
[23:36:24] <jose_freitas> ok
[23:36:32] <lightguard_jp> So it really depends on what the modules have scoped out.
[23:36:35] <mojavelinux> right
[23:36:40] <mojavelinux> thanks, that was a more direct answer :)
[23:36:44] <jose_freitas> =)
[23:36:45] *** nickarls has quit IRC
[23:37:32] <mojavelinux> anyway, I think an action item is to list the tests that are failing in an e-mail to seam-dev
[23:37:50] <lightguard_jp> Yeah, we haven't done that yet
[23:37:51] <mojavelinux> so people can communicate which problem they are resolving
[23:38:06] <mojavelinux> lightguard_jp or stuartdouglas do you have a list of the tests that are failing
[23:38:14] <lightguard_jp> mojavelinux: We also need to get the GF 3.1 container were people can use it.
[23:38:19] <lightguard_jp> the jar, not just the code.
[23:38:44] <lightguard_jp> ElTest, Log test, Resource test
[23:38:51] <lightguard_jp> And I think you said Core was failing too
[23:39:06] <mojavelinux> can you fork arquillian and put it in a pull request
[23:39:13] <mojavelinux> I'll grab it and push a snapshot to the jboss repo
[23:39:27] <mojavelinux> but it needs to be in the same packaging structure as the other containers
[23:39:33] <mojavelinux> org.jboss.arqullian.containers...etc
[23:39:47] <lightguard_jp> I did a few days ago
[23:39:54] <mojavelinux> okay, so it's on me then
[23:40:06] <mojavelinux> I need to push out a snapshot...I need to try it anyway, so that's a part of the same process ;)
[23:40:11] <lightguard_jp> It's in the correct structure according to what aslak said to do
[23:40:51] <mojavelinux> perfect, thank you! (I'm just catching up, as always)
[23:41:58] <mojavelinux> and please, for the other modules, let's make sure that we start getting arquillian profiles in place for jbossas-remote and glassfish-remote
[23:42:05] <mojavelinux> because we dont' want to get stuck here again
[23:42:16] <mojavelinux> we'll figure out how to get Hudson to run this after Arquillian Beta is out
[23:42:24] <mojavelinux> I don't want to spend cycles yet since it's going to change
[23:42:36] <mojavelinux> but you can at least do manual launching of the test profile
[23:42:46] <mojavelinux> (or if you have gradle, you can run them all at once) :)
[23:42:57] <lightguard_jp> All of those should be IN_CONTAINER tests, correct?
[23:43:03] <lightguard_jp> Which is the default for arquillian
[23:43:09] <mojavelinux> btw, good job clerum for getting integration tests setup for mail
[23:43:20] <clerum> np
[23:43:21] <mojavelinux> yes
[23:43:31] <mojavelinux> though, with catch, jason
[23:43:40] <mojavelinux> we should look to get some in_client tests
[23:43:51] <mojavelinux> but again, let's wait for arquillian beta on that
[23:44:00] <mojavelinux> since it just makes it a lot simpler
[23:44:10] <lightguard_jp> Which, according to aslak should be around the end of the month (for those who don't know)
[23:44:36] <mojavelinux> yes, thank you for mentioning that...beta of arquillian is targetted at beginning of Feburary, or jFokus at the latest (mid feb)
[23:44:56] <mojavelinux> please feel free to jump in and lend a hand on arquillian :)
[23:45:14] <lightguard_jp> I'm not sure if it changes how the tests are written though
[23:45:15] <mojavelinux> you know, on those snowy days (or in the outback, rainy days)
[23:45:20] <mojavelinux> it may
[23:45:32] <lightguard_jp> But the shrinkwrap archive creation changes
[23:45:59] <mojavelinux> yeah, but any migration we do in seam will be beneficial for posting on the arquillian forums or in the repo
[23:46:01] <mojavelinux> as scripts
[23:46:26] <mojavelinux> ah, another important announcement I forgot
[23:46:37] <mojavelinux> I pushed out a new version of the jboss javaee6 webapp archetype
[23:46:56] <mojavelinux> so you have two options for spawning a new project to play around with seam from the developer's perspective
[23:47:07] <mojavelinux> org.jboss.weld.archetypes:jboss-javaee6-webapp:1.0.1.Beta2 or forge
[23:47:31] <mojavelinux> while we are steering towards forge, there is still a gap that the archetypes fill in the short-term
[23:47:42] <mojavelinux> plus, we needed it for a jboss tools webinar that burr is giving
[23:48:42] <mojavelinux> we are looking for the following feedback atm:
[23:48:59] <mojavelinux> 1. feedback for the stack trace filtering in seam catch SEAMCATCH-4
[23:49:00] <jbossbot> jira [SEAMCATCH-4] Include the ability to filter stack traces [Coding In Progress, Major, Jason Porter] https://issues.jboss.org/browse/SEAMCATCH-4
[23:49:20] <mojavelinux> 2. review of Ken's merge of jboss logging into solder to create Solder Logging
[23:49:24] <lightguard_jp> That's also out on the Seam 3 forum
[23:49:31] <lightguard_jp> For those who would like to provide feedback
[23:50:26] <mojavelinux> https://github.com/kenfinnigan/solder/commit/f81035c29d95e68d4b55da43247cd88411d8c70f
[23:50:27] <jbossbot> git [solder] f81035c.. Ken Finnigan Import jboss-logging-3.0.0.Beta4
[23:50:29] <mojavelinux> and review of the mail module
[23:50:39] <mojavelinux> so cody can do a release :)
[23:50:47] <mojavelinux> oh cool!
[23:50:53] <mojavelinux> jboss bot picks up git commits
[23:50:56] <mojavelinux> that's awesome
[23:51:18] <mojavelinux> oh, one more important thing
[23:51:29] <mojavelinux> andy gibson e-mailed me and said he wants to do a blog entry about seam 3
[23:51:40] <mojavelinux> if you have any features you want highlighted, please let me know (just e-mail me)
[23:51:50] <mojavelinux> I've got a list, but in case I miss something
[23:52:08] <mojavelinux> lightguard_jp: I've got you covered. I want to highlight mail for sure, since that's never been covered
[23:53:04] <lightguard_jp> I think we should target things that others have tried or implemented in other ways, like things that CODI also covers.  Helps get the word out that there are other ways of doing things
[23:53:36] <mojavelinux> yep, I agree, i'll pass that on to him
[23:53:49] <lightguard_jp> Stuff like faces, persistence, i18n
[23:53:52] <mojavelinux> he'll likely consolidate the info, he just wants to know what to look for
[23:53:52] <lightguard_jp> security
[23:54:05] <lightguard_jp> rest
[23:56:10] <mojavelinux> does anyone want to discuss a topic before the meeting is concluded?
[23:58:23] <mojavelinux> if it's cool, I'm going to take a break and skip out on office hours, which would normally follow this meeting
[23:58:31] <mojavelinux> i'm not feeling all that great
[23:58:38] <mojavelinux> perhaps lincoln and lightguard_jp can take the reigns :)
[23:59:18] <lightguard_jp> Oh, speaking of office hours
[23:59:25] <mojavelinux> yep, what's up?
[23:59:33] <lightguard_jp> When are those, I haven't seen anything saying when they are for anyone
[23:59:44] <mojavelinux> oh, sorry, I wasn't very clear about that
[23:59:48] <mojavelinux> I posted it on the ProjectMeetings page





top