[jira] [Comment Edited] (DELTASPIKE-684) No OSGi headers in deltaspike-partial-bean-module-api
[ https://issues.apache.org/jira/browse/DELTASPIKE-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096011#comment-14096011 ] Ioan Eugen Stan edited comment on DELTASPIKE-684 at 8/13/14 7:52 PM: - With the patch, I've installed the bundles in Karaf and they resolve and activate. Haven't used them with actual code yet. If you have a working project, please give them a try. was (Author: ieugen): I've installed the bundles in Karaf and they resolve and activate. Haven't used them with actual code yet. If you have a working project, please give them a try. > No OSGi headers in deltaspike-partial-bean-module-api > - > > Key: DELTASPIKE-684 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-684 > Project: DeltaSpike > Issue Type: Bug > Components: PartialBean >Affects Versions: 1.0.1 >Reporter: Ioan Eugen Stan > Attachments: DELTASPIKE-684.patch > > > Console output: > org.osgi.framework.BundleException: Jar is not a bundle, no > Bundle-SymbolicName > mvn:org.apache.deltaspike.modules/deltaspike-partial-bean-module-api/1.0.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (DELTASPIKE-684) No OSGi headers in deltaspike-partial-bean-module-api
[ https://issues.apache.org/jira/browse/DELTASPIKE-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ioan Eugen Stan updated DELTASPIKE-684: --- Attachment: DELTASPIKE-684.patch I've installed the bundles in Karaf and they resolve and activate. Haven't used them with actual code yet. If you have a working project, please give them a try. > No OSGi headers in deltaspike-partial-bean-module-api > - > > Key: DELTASPIKE-684 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-684 > Project: DeltaSpike > Issue Type: Bug > Components: PartialBean >Affects Versions: 1.0.1 >Reporter: Ioan Eugen Stan > Attachments: DELTASPIKE-684.patch > > > Console output: > org.osgi.framework.BundleException: Jar is not a bundle, no > Bundle-SymbolicName > mvn:org.apache.deltaspike.modules/deltaspike-partial-bean-module-api/1.0.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (DELTASPIKE-685) Guard against null FacesContext in Exception Handler Bridge
[ https://issues.apache.org/jira/browse/DELTASPIKE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cody Lerum closed DELTASPIKE-685. - Resolution: Fixed > Guard against null FacesContext in Exception Handler Bridge > --- > > Key: DELTASPIKE-685 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-685 > Project: DeltaSpike > Issue Type: Bug > Components: JSF-Module >Affects Versions: 1.0.1 >Reporter: Cody Lerum >Assignee: Cody Lerum > Fix For: 1.0.2 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (DELTASPIKE-685) Guard against null FacesContext in Exception Handler Bridge
[ https://issues.apache.org/jira/browse/DELTASPIKE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096003#comment-14096003 ] Cody Lerum commented on DELTASPIKE-685: --- [~tandraschko] This is happening on Wildfly 8.1 when requesting a non-existent resource that results in a 404 > Guard against null FacesContext in Exception Handler Bridge > --- > > Key: DELTASPIKE-685 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-685 > Project: DeltaSpike > Issue Type: Bug > Components: JSF-Module >Affects Versions: 1.0.1 >Reporter: Cody Lerum >Assignee: Cody Lerum > Fix For: 1.0.2 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (DELTASPIKE-685) Guard against null FacesContext in Exception Handler Bridge
[ https://issues.apache.org/jira/browse/DELTASPIKE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095991#comment-14095991 ] Thomas Andraschko commented on DELTASPIKE-685: -- how can it be null? > Guard against null FacesContext in Exception Handler Bridge > --- > > Key: DELTASPIKE-685 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-685 > Project: DeltaSpike > Issue Type: Bug > Components: JSF-Module >Affects Versions: 1.0.1 >Reporter: Cody Lerum >Assignee: Cody Lerum > Fix For: 1.0.2 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (DELTASPIKE-685) Guard against null FacesContext in Exception Handler Bridge
Cody Lerum created DELTASPIKE-685: - Summary: Guard against null FacesContext in Exception Handler Bridge Key: DELTASPIKE-685 URL: https://issues.apache.org/jira/browse/DELTASPIKE-685 Project: DeltaSpike Issue Type: Bug Components: JSF-Module Affects Versions: 1.0.1 Reporter: Cody Lerum Assignee: Cody Lerum Fix For: 1.0.2 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (DELTASPIKE-684) No OSGi headers in deltaspike-partial-bean-module-api
Ioan Eugen Stan created DELTASPIKE-684: -- Summary: No OSGi headers in deltaspike-partial-bean-module-api Key: DELTASPIKE-684 URL: https://issues.apache.org/jira/browse/DELTASPIKE-684 Project: DeltaSpike Issue Type: Bug Components: PartialBean Affects Versions: 1.0.1 Reporter: Ioan Eugen Stan Console output: org.osgi.framework.BundleException: Jar is not a bundle, no Bundle-SymbolicName mvn:org.apache.deltaspike.modules/deltaspike-partial-bean-module-api/1.0.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: First steps for DeltaSpike docs contribution
I just think that the ref #2 ( adding docs content ), we don't need/want to take the .md files there. We can keep them on the old repo. Besides that, +1 for this workflow. Em 8/12/14, 18:14, Michelle Murray escreveu: I'll file the form and I'll ask Suz who will also be doing the reorg to file one too. As I see it, we would complete the reorg/rework by: 1) forking the DeltaSpike github repo - be that repo https://github.com/apache/deltaspike with a documentation folder or another DeltaSpike github repo specifically for the website docs (like JBoss Tools or AeroGear) 2) adding docs content (taking md, reorganising, editing, making into asciidoc) 3) submit regular PRs back to that original DeltaSpike repo 4) some one will review and merge those PRs and then you'll have a source to build and play with to get it to where it needs to go for the Apache svn repo or whatever and eventually up onto the live website. Are there any logistical issues with that plan in terms of us getting the reorg docs to DeltaSpike? Thanks, Michelle - Original Message - From: "Gerhard Petracek" To: dev@deltaspike.apache.org Cc: "Michelle Murray" , "Suzanne Dorfield" Sent: Tuesday, 12 August, 2014 7:00:50 PM Subject: Re: First steps for DeltaSpike docs contribution @michelle: please file an icla (see [1]). regards, gerhard [1] http://deltaspike.apache.org/community.html#contributors 2014-08-12 19:51 GMT+02:00 John D. Ament < john.d.am...@gmail.com > : No restrictions - but it limits how quickly we can pull into our repo. Since it's basically a code donation, we have to follow some IP clearance rules. On Tue, Aug 12, 2014 at 1:41 PM, Rafael Benevides < benevi...@redhat.com > wrote: Nope. She will work on a cloned DeltaSpike github repo. Is that right, Michelle ? I'll just push the changes ;) I'm not sure if is there any restrictions on any Apache policies on doing that. I think this way is simple than having her team as commiters, right ? Em 8/12/14, 14:26, John D. Ament escreveu: Rafael, So wait, will all commits show your ID coming over? On Tue, Aug 12, 2014 at 10:33 AM, Rafael Benevides < benevi...@redhat.com wrote: $REPO_ROOT/documentation seems more logical to me! Thanks Gerhard. Ref to public github repo, I'll be responsible for getting the docs from Michelle repos and pushing it at DeltaSpike repo. Ok ? This way we can give/get continuous feedback on it. Thanks again John for your help on that. Em 8/12/14, 10:04, John D. Ament escreveu: Personally, we can figure out where the final resting place is when the docs are in. we will end up doing an iP Clearance as well, Michelle mostly for your information. See [1], I'll take care of filling out the forms. [1]: http://incubator.apache.org/ip-clearance/ On Tue, Aug 12, 2014 at 8:55 AM, Gerhard Petracek < gerhard.petra...@gmail.com > wrote: @rafael: basically +1 about the path: afaik the original plan was to host the documentation e.g. in: $REPO_ROOT/documentation mark created the folder deltaspike in $REPO_ROOT - so he can provide details about his idea back then. regards, gerhard 2014-08-12 14:01 GMT+02:00 Rafael Benevides < benevi...@redhat.com >: Thanks, Michelle. I though Aug 18 and typed Aug 11 :) Em 8/11/14, 19:05, Michelle Murray escreveu: Just to clarify, we would be looking to start next Monday, 18-Aug, if everything is in place. -- *From: *"Rafael Benevides" < benevi...@redhat.com > < benevi...@redhat.com *To: * dev@deltaspike.apache.org , "Michelle Murray" < mmur...@redhat.com > < mmur...@redhat.com > *Sent: *Monday, 11 August, 2014 10:48:11 PM *Subject: *First steps for DeltaSpike docs contribution Hi all, I talked with Michelle (copied on this email thread) and it's everything ready so her team's job can be started Monday, (08/11). If there are no objections, the plan proposed here: https://docs.google.com/document/d/186f_ amQ9XuREq8FcO7orxvOjQZtvEEYa7W Pj1e8p8bM/edit#heading=h.4sqhyz68wgg2 will be implemented using the asciidoc format and it will be host together with the DeltaSpike sources ( https://git-wip-us.apache.org/ repos/asf/deltaspike.git < https://git-wip-us.apache.org/repos/asf?p=deltaspike.git >). The path will be $REPO_ROOT/ deltaspike/documentation/ (as proposed by John Ament PoC) While the documentation work is being made, we will have time to work on Apache CMS -- *Rafael Benevides | Senior Software Engineer* JBoss Developer M: +55-61-9269-6576 [image: Red Hat] Better technology. Faster innovation. Powered by community collaboration. See how it works at www.redhat.com [image: LinkedIn] < http://www.linkedin.com/company/3258288 > [image: Youtube] < https://www.youtube.com/redhatlatam >
Re: First steps for DeltaSpike docs contribution
@john: no - as i said mark created the folder deltaspike and afaik the initial intention was e.g.: repo-root |_ deltaspike |_ documentation or something like repo-root |_ deltaspike |_ deltaspike-cms (that was no comment that we should do it that way). regards, gerhard 2014-08-13 11:50 GMT+02:00 John D. Ament : > Gerhard, > > So, based on your prior message, do you want to eliminate the deltaspike > folder currently in the repo so that the top level has a pom file? Is this > something to tackle before 1.0.2? I think the timing got a little messed up > due to the expected release & doc team. > > Michelle, > > Are you thinking that this is a pre-req for your team's work? Or just > creating that documentation folder and we can move it later? > > > On Tue, Aug 12, 2014 at 5:14 PM, Michelle Murray > wrote: > >> I'll file the form and I'll ask Suz who will also be doing the reorg to >> file one too. >> >> As I see it, we would complete the reorg/rework by: >> 1) forking the DeltaSpike github repo - be that repo >> https://github.com/apache/deltaspike with a documentation folder or >> another DeltaSpike github repo specifically for the website docs (like >> JBoss Tools or AeroGear) >> 2) adding docs content (taking md, reorganising, editing, making into >> asciidoc) >> 3) submit regular PRs back to that original DeltaSpike repo >> 4) some one will review and merge those PRs and then you'll have a source >> to build and play with to get it to where it needs to go for the Apache svn >> repo or whatever and eventually up onto the live website. >> >> Are there any logistical issues with that plan in terms of us getting the >> reorg docs to DeltaSpike? >> >> Thanks, >> Michelle >> >> - Original Message - >> >> > From: "Gerhard Petracek" >> > To: dev@deltaspike.apache.org >> > Cc: "Michelle Murray" , "Suzanne Dorfield" >> > >> > Sent: Tuesday, 12 August, 2014 7:00:50 PM >> > Subject: Re: First steps for DeltaSpike docs contribution >> >> > @michelle: >> > please file an icla (see [1]). >> >> > regards, >> > gerhard >> >> > [1] http://deltaspike.apache.org/community.html#contributors >> >> > 2014-08-12 19:51 GMT+02:00 John D. Ament < john.d.am...@gmail.com > : >> >> > > No restrictions - but it limits how quickly we can pull into our repo. >> > >> > > Since it's basically a code donation, we have to follow some IP >> clearance >> > >> > > rules. >> > >> >> > > On Tue, Aug 12, 2014 at 1:41 PM, Rafael Benevides < >> benevi...@redhat.com > >> > >> > > wrote: >> > >> >> > > > Nope. She will work on a cloned DeltaSpike github repo. Is that >> right, >> > >> > > > Michelle ? >> > >> > > > I'll just push the changes ;) >> > >> > > > >> > >> > > > I'm not sure if is there any restrictions on any Apache policies on >> doing >> > >> > > > that. I think this way is simple than having her team as commiters, >> right >> > > > ? >> > >> > > > >> > >> > > > >> > >> > > > Em 8/12/14, 14:26, John D. Ament escreveu: >> > >> > > > >> > >> > > > Rafael, >> > >> > > >> >> > >> > > >> So wait, will all commits show your ID coming over? >> > >> > > >> >> > >> > > >> >> > >> > > >> On Tue, Aug 12, 2014 at 10:33 AM, Rafael Benevides < >> > > >> benevi...@redhat.com >> > > >> > >> > >> > > >> wrote: >> > >> > > >> >> > >> > > >> $REPO_ROOT/documentation seems more logical to me! Thanks Gerhard. >> > >> > > >>> >> > >> > > >>> Ref to public github repo, I'll be responsible for getting the >> docs >> > > >>> from >> > >> > > >>> Michelle repos and pushing it at DeltaSpike repo. Ok ? This way >> we can >> > >> > > >>> give/get continuous feedback on it. >> > >> > > >>> >> > >> > > >>> Thanks again John for your help on that. >> > >> > > >>> >> > >> > > >>> Em 8/12/14, 10:04, John D. Ament escreveu: >> > >> > > >>> >> > >> > > >>> Personally, we can figure out where the final resting place is >> when the >> > >> > > docs are in. >> > >> > > >> > >> > > we will end up doing an iP Clearance as well, Michelle mostly >> for your >> > >> > > information. See [1], I'll take care of filling out the forms. >> > >> > > >> > >> > > [1]: http://incubator.apache.org/ip-clearance/ >> > >> > > >> > >> > > >> > >> > > On Tue, Aug 12, 2014 at 8:55 AM, Gerhard Petracek < >> > >> > > gerhard.petra...@gmail.com > wrote: >> > >> > > >> > >> > > @rafael: >> > >> > > >> > >> > > > basically +1 >> > >> > > > about the path: afaik the original plan was to host the >> documentation >> > >> > > > e.g. >> > >> > > > in: $REPO_ROOT/documentation >> > >> > > > mark created the folder deltaspike in $REPO_ROOT - so he can >> provide >> > >> > > > details about his idea back then. >> > >> > > > >> > >> > > > regards, >> > >> > > > gerhard >> > >> > > > >> > >> > > > >> > >> > > > >> > >> > > > 2014-08-12 14:01 GMT+02:00 Rafael Benevides < >> benevi...@redhat.com >: >> > >> > > > >> > >> > > > Thanks, Michelle. >> > >> > > > >> > >>
Re: First steps for DeltaSpike docs contribution
Gerhard, So, based on your prior message, do you want to eliminate the deltaspike folder currently in the repo so that the top level has a pom file? Is this something to tackle before 1.0.2? I think the timing got a little messed up due to the expected release & doc team. Michelle, Are you thinking that this is a pre-req for your team's work? Or just creating that documentation folder and we can move it later? On Tue, Aug 12, 2014 at 5:14 PM, Michelle Murray wrote: > I'll file the form and I'll ask Suz who will also be doing the reorg to > file one too. > > As I see it, we would complete the reorg/rework by: > 1) forking the DeltaSpike github repo - be that repo > https://github.com/apache/deltaspike with a documentation folder or > another DeltaSpike github repo specifically for the website docs (like > JBoss Tools or AeroGear) > 2) adding docs content (taking md, reorganising, editing, making into > asciidoc) > 3) submit regular PRs back to that original DeltaSpike repo > 4) some one will review and merge those PRs and then you'll have a source > to build and play with to get it to where it needs to go for the Apache svn > repo or whatever and eventually up onto the live website. > > Are there any logistical issues with that plan in terms of us getting the > reorg docs to DeltaSpike? > > Thanks, > Michelle > > - Original Message - > > > From: "Gerhard Petracek" > > To: dev@deltaspike.apache.org > > Cc: "Michelle Murray" , "Suzanne Dorfield" > > > > Sent: Tuesday, 12 August, 2014 7:00:50 PM > > Subject: Re: First steps for DeltaSpike docs contribution > > > @michelle: > > please file an icla (see [1]). > > > regards, > > gerhard > > > [1] http://deltaspike.apache.org/community.html#contributors > > > 2014-08-12 19:51 GMT+02:00 John D. Ament < john.d.am...@gmail.com > : > > > > No restrictions - but it limits how quickly we can pull into our repo. > > > > > Since it's basically a code donation, we have to follow some IP > clearance > > > > > rules. > > > > > > On Tue, Aug 12, 2014 at 1:41 PM, Rafael Benevides < > benevi...@redhat.com > > > > > > wrote: > > > > > > > Nope. She will work on a cloned DeltaSpike github repo. Is that > right, > > > > > > Michelle ? > > > > > > I'll just push the changes ;) > > > > > > > > > > > > I'm not sure if is there any restrictions on any Apache policies on > doing > > > > > > that. I think this way is simple than having her team as commiters, > right > > > > ? > > > > > > > > > > > > > > > > > > Em 8/12/14, 14:26, John D. Ament escreveu: > > > > > > > > > > > > Rafael, > > > > > >> > > > > > >> So wait, will all commits show your ID coming over? > > > > > >> > > > > > >> > > > > > >> On Tue, Aug 12, 2014 at 10:33 AM, Rafael Benevides < > > > >> benevi...@redhat.com > > > >> > > > > > > >> wrote: > > > > > >> > > > > > >> $REPO_ROOT/documentation seems more logical to me! Thanks Gerhard. > > > > > >>> > > > > > >>> Ref to public github repo, I'll be responsible for getting the docs > > > >>> from > > > > > >>> Michelle repos and pushing it at DeltaSpike repo. Ok ? This way we > can > > > > > >>> give/get continuous feedback on it. > > > > > >>> > > > > > >>> Thanks again John for your help on that. > > > > > >>> > > > > > >>> Em 8/12/14, 10:04, John D. Ament escreveu: > > > > > >>> > > > > > >>> Personally, we can figure out where the final resting place is > when the > > > > > docs are in. > > > > > > > > > > we will end up doing an iP Clearance as well, Michelle mostly for > your > > > > > information. See [1], I'll take care of filling out the forms. > > > > > > > > > > [1]: http://incubator.apache.org/ip-clearance/ > > > > > > > > > > > > > > > On Tue, Aug 12, 2014 at 8:55 AM, Gerhard Petracek < > > > > > gerhard.petra...@gmail.com > wrote: > > > > > > > > > > @rafael: > > > > > > > > > > > basically +1 > > > > > > about the path: afaik the original plan was to host the > documentation > > > > > > e.g. > > > > > > in: $REPO_ROOT/documentation > > > > > > mark created the folder deltaspike in $REPO_ROOT - so he can > provide > > > > > > details about his idea back then. > > > > > > > > > > > > regards, > > > > > > gerhard > > > > > > > > > > > > > > > > > > > > > > > > 2014-08-12 14:01 GMT+02:00 Rafael Benevides < > benevi...@redhat.com >: > > > > > > > > > > > > Thanks, Michelle. > > > > > > > > > > > > I though Aug 18 and typed Aug 11 :) > > > > > >> > > > > > >> Em 8/11/14, 19:05, Michelle Murray escreveu: > > > > > >> > > > > > >> Just to clarify, we would be looking to start next Monday, > 18-Aug, > > > > > >> if > > > > > >> everything is in place. > > > > > >> > > > > > >> -- > > > > > >> > > > > > >> *From: *"Rafael Benevides" < benevi...@redhat.com > < > > > > > >> benevi...@redhat.com > > > > > >> *To: * dev@deltaspike.apache.org , "Mi
Re: First steps for DeltaSpike docs contribution
I'll file the form and I'll ask Suz who will also be doing the reorg to file one too. As I see it, we would complete the reorg/rework by: 1) forking the DeltaSpike github repo - be that repo https://github.com/apache/deltaspike with a documentation folder or another DeltaSpike github repo specifically for the website docs (like JBoss Tools or AeroGear) 2) adding docs content (taking md, reorganising, editing, making into asciidoc) 3) submit regular PRs back to that original DeltaSpike repo 4) some one will review and merge those PRs and then you'll have a source to build and play with to get it to where it needs to go for the Apache svn repo or whatever and eventually up onto the live website. Are there any logistical issues with that plan in terms of us getting the reorg docs to DeltaSpike? Thanks, Michelle - Original Message - > From: "Gerhard Petracek" > To: dev@deltaspike.apache.org > Cc: "Michelle Murray" , "Suzanne Dorfield" > > Sent: Tuesday, 12 August, 2014 7:00:50 PM > Subject: Re: First steps for DeltaSpike docs contribution > @michelle: > please file an icla (see [1]). > regards, > gerhard > [1] http://deltaspike.apache.org/community.html#contributors > 2014-08-12 19:51 GMT+02:00 John D. Ament < john.d.am...@gmail.com > : > > No restrictions - but it limits how quickly we can pull into our repo. > > > Since it's basically a code donation, we have to follow some IP clearance > > > rules. > > > On Tue, Aug 12, 2014 at 1:41 PM, Rafael Benevides < benevi...@redhat.com > > > > wrote: > > > > Nope. She will work on a cloned DeltaSpike github repo. Is that right, > > > > Michelle ? > > > > I'll just push the changes ;) > > > > > > > > I'm not sure if is there any restrictions on any Apache policies on doing > > > > that. I think this way is simple than having her team as commiters, right > > > ? > > > > > > > > > > > > Em 8/12/14, 14:26, John D. Ament escreveu: > > > > > > > > Rafael, > > > >> > > > >> So wait, will all commits show your ID coming over? > > > >> > > > >> > > > >> On Tue, Aug 12, 2014 at 10:33 AM, Rafael Benevides < > > >> benevi...@redhat.com > > >> > > > > >> wrote: > > > >> > > > >> $REPO_ROOT/documentation seems more logical to me! Thanks Gerhard. > > > >>> > > > >>> Ref to public github repo, I'll be responsible for getting the docs > > >>> from > > > >>> Michelle repos and pushing it at DeltaSpike repo. Ok ? This way we can > > > >>> give/get continuous feedback on it. > > > >>> > > > >>> Thanks again John for your help on that. > > > >>> > > > >>> Em 8/12/14, 10:04, John D. Ament escreveu: > > > >>> > > > >>> Personally, we can figure out where the final resting place is when the > > > docs are in. > > > > > > we will end up doing an iP Clearance as well, Michelle mostly for your > > > information. See [1], I'll take care of filling out the forms. > > > > > > [1]: http://incubator.apache.org/ip-clearance/ > > > > > > > > > On Tue, Aug 12, 2014 at 8:55 AM, Gerhard Petracek < > > > gerhard.petra...@gmail.com > wrote: > > > > > > @rafael: > > > > > > > basically +1 > > > > about the path: afaik the original plan was to host the documentation > > > > e.g. > > > > in: $REPO_ROOT/documentation > > > > mark created the folder deltaspike in $REPO_ROOT - so he can provide > > > > details about his idea back then. > > > > > > > > regards, > > > > gerhard > > > > > > > > > > > > > > > > 2014-08-12 14:01 GMT+02:00 Rafael Benevides < benevi...@redhat.com >: > > > > > > > > Thanks, Michelle. > > > > > > > > I though Aug 18 and typed Aug 11 :) > > > >> > > > >> Em 8/11/14, 19:05, Michelle Murray escreveu: > > > >> > > > >> Just to clarify, we would be looking to start next Monday, 18-Aug, > > > >> if > > > >> everything is in place. > > > >> > > > >> -- > > > >> > > > >> *From: *"Rafael Benevides" < benevi...@redhat.com > < > > > >> benevi...@redhat.com > > > >> *To: * dev@deltaspike.apache.org , "Michelle Murray" < > > > >> mmur...@redhat.com > > > > >> < mmur...@redhat.com > > > > >> *Sent: *Monday, 11 August, 2014 10:48:11 PM > > > >> *Subject: *First steps for DeltaSpike docs contribution > > > >> > > > >> > > > >> > > > >> Hi all, > > > >> > > > >> I talked with Michelle (copied on this email thread) and it's > > > >> everything > > > >> ready so her team's job can be started Monday, (08/11). > > > >> > > > >> If there are no objections, the plan proposed here: > > > >> https://docs.google.com/document/d/186f_ > > > >> amQ9XuREq8FcO7orxvOjQZtvEEYa7W > > > >> Pj1e8p8bM/edit#heading=h.4sqhyz68wgg2 > > > >> will be implemented using the asciidoc format and it will be host > > > >> to
