You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2007/08/18 05:38:31 UTC
[jira] Created: (OPENEJB-636) doc: deploy-tool.html
doc: deploy-tool.html
---------------------
Key: OPENEJB-636
URL: https://issues.apache.org/jira/browse/OPENEJB-636
Project: OpenEJB
Issue Type: Sub-task
Reporter: David Blevins
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENEJB-636) doc: deploy-tool.html
Posted by "David Blevins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521583 ]
David Blevins commented on OPENEJB-636:
---------------------------------------
Thanks, Manu!
I noticed my notes weren't quite complete and the page as far more
outdated that I had commented, so I went ahead and did some more
updates to this page.
Great job on these new docs!
-David
> doc: deploy-tool.html
> ---------------------
>
> Key: OPENEJB-636
> URL: https://issues.apache.org/jira/browse/OPENEJB-636
> Project: OpenEJB
> Issue Type: Sub-task
> Reporter: David Blevins
> Assignee: Manu T George
> Priority: Blocker
> Fix For: 3.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENEJB-636) doc: deploy-tool.html
Posted by "David Blevins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins updated OPENEJB-636:
----------------------------------
Priority: Blocker (was: Major)
> doc: deploy-tool.html
> ---------------------
>
> Key: OPENEJB-636
> URL: https://issues.apache.org/jira/browse/OPENEJB-636
> Project: OpenEJB
> Issue Type: Sub-task
> Reporter: David Blevins
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENEJB-636) doc: deploy-tool.html
Posted by "David Blevins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520780 ]
David Blevins commented on OPENEJB-636:
---------------------------------------
High priority. Needs to be updated. New page does not need to contain all the options. Should show the output of the deploy tool.
All the options are wrong. The new options are documented in the tool itself. That info could be placed here.
The examples are outdated and should be deleted.
> doc: deploy-tool.html
> ---------------------
>
> Key: OPENEJB-636
> URL: https://issues.apache.org/jira/browse/OPENEJB-636
> Project: OpenEJB
> Issue Type: Sub-task
> Reporter: David Blevins
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OPENEJB-636) doc: deploy-tool.html
Posted by "Manu T George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manu T George reassigned OPENEJB-636:
-------------------------------------
Assignee: Manu T George
> doc: deploy-tool.html
> ---------------------
>
> Key: OPENEJB-636
> URL: https://issues.apache.org/jira/browse/OPENEJB-636
> Project: OpenEJB
> Issue Type: Sub-task
> Reporter: David Blevins
> Assignee: Manu T George
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Resolved: (OPENEJB-636) doc: deploy-tool.html
Posted by Karan Malhi <ka...@gmail.com>.
Maybe some sort of an email filter on dev@openejb.apache.org might be
able to forward it to jira@apache.org on receipt of an email with the
relevant jira subject
On 8/23/07, David Blevins <da...@visi.com> wrote:
>
> On Aug 22, 2007, at 3:34 PM, David Blevins wrote:
>
> >
> > On Aug 22, 2007, at 1:49 PM, Karan Malhi wrote:
> >
> >> On 8/21/07, David Blevins <da...@visi.com> wrote:
> >>> On a different note.... I cc'ed the jira@apache.org list and it
> >>> totally added a comment on the issue with my email text and the
> >>> prior
> >>> content trimmed out. Very cool!
> >>>
> >>> We should totally use that more often!
> >>
> >> I just tried it and this is a really awesome feature. So, do I just
> >> need the JIRA issue number in my subject? Is that what jira is
> >> looking
> >> for in the email?
> >
> > Not sure. Feel free to create a test issue and send a bunch of
> > emails to jira@apache.org till you figure it out. There might be
> > docs too, but that doesn't sound like nearly as much fun....
>
> I couldn't resist. Here are my findings
>
> http://issues.apache.org/jira/browse/OPENEJB-670
>
> Short answer, if you put "[jira] OPENEJB-123" anywhere in your
> subject line and cc jira@apache.org our email gets added as a comment
> with all '> quoted' text stripped out.
>
> If only we could get it to work without having to cc the
> jira@apache.org address :)
>
> -David
>
>
--
Karan Singh Malhi
Re: [jira] Resolved: (OPENEJB-636) doc: deploy-tool.html
Posted by Karan Malhi <ka...@gmail.com>.
pretty cool !!
On 8/23/07, David Blevins <da...@visi.com> wrote:
>
> On Aug 22, 2007, at 3:34 PM, David Blevins wrote:
>
> >
> > On Aug 22, 2007, at 1:49 PM, Karan Malhi wrote:
> >
> >> On 8/21/07, David Blevins <da...@visi.com> wrote:
> >>> On a different note.... I cc'ed the jira@apache.org list and it
> >>> totally added a comment on the issue with my email text and the
> >>> prior
> >>> content trimmed out. Very cool!
> >>>
> >>> We should totally use that more often!
> >>
> >> I just tried it and this is a really awesome feature. So, do I just
> >> need the JIRA issue number in my subject? Is that what jira is
> >> looking
> >> for in the email?
> >
> > Not sure. Feel free to create a test issue and send a bunch of
> > emails to jira@apache.org till you figure it out. There might be
> > docs too, but that doesn't sound like nearly as much fun....
>
> I couldn't resist. Here are my findings
>
> http://issues.apache.org/jira/browse/OPENEJB-670
>
> Short answer, if you put "[jira] OPENEJB-123" anywhere in your
> subject line and cc jira@apache.org our email gets added as a comment
> with all '> quoted' text stripped out.
>
> If only we could get it to work without having to cc the
> jira@apache.org address :)
>
> -David
>
>
--
Karan Singh Malhi
Re: [jira] Resolved: (OPENEJB-636) doc: deploy-tool.html
Posted by David Blevins <da...@visi.com>.
On Aug 24, 2007, at 1:39 PM, Mohammad Nour El-Din wrote:
> On 8/23/07, David Blevins <da...@visi.com> wrote:
>>>> If only we could get it to work without having to cc the
>>>> jira@apache.org address :)
>
> What a lazy man :P
>
Absolutely :) The endless pursuit of productive laziness .... The
true dream of any programmer.
-David
Re: [jira] Resolved: (OPENEJB-636) doc: deploy-tool.html
Posted by Karan Malhi <ka...@gmail.com>.
;) I was actually going to suggest something like
[JIRA] OPENEJB-xxx [CREATE][IMPROVEMENT][CORE]
and then enter a message, no need to go to JIRA and create an issue,
just create it through email.
Similarly,
[JIRA]OPENEJB-xxx [CLOSE]
and the message goes here and that closes the issue.
Do I get the title of laziest man now? ;)
On 8/24/07, Mohammad Nour El-Din <no...@gmail.com> wrote:
> What a lazy man :P
>
> On 8/23/07, David Blevins <da...@visi.com> wrote:
> >
> >
> > On Aug 22, 2007, at 3:34 PM, David Blevins wrote:
> >
> > >
> > > On Aug 22, 2007, at 1:49 PM, Karan Malhi wrote:
> > >
> > >> On 8/21/07, David Blevins <da...@visi.com> wrote:
> > >>> On a different note.... I cc'ed the jira@apache.org list and it
> > >>> totally added a comment on the issue with my email text and the
> > >>> prior
> > >>> content trimmed out. Very cool!
> > >>>
> > >>> We should totally use that more often!
> > >>
> > >> I just tried it and this is a really awesome feature. So, do I just
> > >> need the JIRA issue number in my subject? Is that what jira is
> > >> looking
> > >> for in the email?
> > >
> > > Not sure. Feel free to create a test issue and send a bunch of
> > > emails to jira@apache.org till you figure it out. There might be
> > > docs too, but that doesn't sound like nearly as much fun....
> >
> > I couldn't resist. Here are my findings
> >
> > http://issues.apache.org/jira/browse/OPENEJB-670
> >
> > Short answer, if you put "[jira] OPENEJB-123" anywhere in your
> > subject line and cc jira@apache.org our email gets added as a comment
> > with all '> quoted' text stripped out.
> >
> > If only we could get it to work without having to cc the
> > jira@apache.org address :)
> >
> > -David
> >
> >
>
>
> --
> Thanks
> - Mohammad Nour
>
--
Karan Singh Malhi
Re: [jira] Resolved: (OPENEJB-636) doc: deploy-tool.html
Posted by Mohammad Nour El-Din <no...@gmail.com>.
What a lazy man :P
On 8/23/07, David Blevins <da...@visi.com> wrote:
>
>
> On Aug 22, 2007, at 3:34 PM, David Blevins wrote:
>
> >
> > On Aug 22, 2007, at 1:49 PM, Karan Malhi wrote:
> >
> >> On 8/21/07, David Blevins <da...@visi.com> wrote:
> >>> On a different note.... I cc'ed the jira@apache.org list and it
> >>> totally added a comment on the issue with my email text and the
> >>> prior
> >>> content trimmed out. Very cool!
> >>>
> >>> We should totally use that more often!
> >>
> >> I just tried it and this is a really awesome feature. So, do I just
> >> need the JIRA issue number in my subject? Is that what jira is
> >> looking
> >> for in the email?
> >
> > Not sure. Feel free to create a test issue and send a bunch of
> > emails to jira@apache.org till you figure it out. There might be
> > docs too, but that doesn't sound like nearly as much fun....
>
> I couldn't resist. Here are my findings
>
> http://issues.apache.org/jira/browse/OPENEJB-670
>
> Short answer, if you put "[jira] OPENEJB-123" anywhere in your
> subject line and cc jira@apache.org our email gets added as a comment
> with all '> quoted' text stripped out.
>
> If only we could get it to work without having to cc the
> jira@apache.org address :)
>
> -David
>
>
--
Thanks
- Mohammad Nour
Re: [jira] Resolved: (OPENEJB-636) doc: deploy-tool.html
Posted by David Blevins <da...@visi.com>.
On Aug 22, 2007, at 3:34 PM, David Blevins wrote:
>
> On Aug 22, 2007, at 1:49 PM, Karan Malhi wrote:
>
>> On 8/21/07, David Blevins <da...@visi.com> wrote:
>>> On a different note.... I cc'ed the jira@apache.org list and it
>>> totally added a comment on the issue with my email text and the
>>> prior
>>> content trimmed out. Very cool!
>>>
>>> We should totally use that more often!
>>
>> I just tried it and this is a really awesome feature. So, do I just
>> need the JIRA issue number in my subject? Is that what jira is
>> looking
>> for in the email?
>
> Not sure. Feel free to create a test issue and send a bunch of
> emails to jira@apache.org till you figure it out. There might be
> docs too, but that doesn't sound like nearly as much fun....
I couldn't resist. Here are my findings
http://issues.apache.org/jira/browse/OPENEJB-670
Short answer, if you put "[jira] OPENEJB-123" anywhere in your
subject line and cc jira@apache.org our email gets added as a comment
with all '> quoted' text stripped out.
If only we could get it to work without having to cc the
jira@apache.org address :)
-David
Re: [jira] Resolved: (OPENEJB-636) doc: deploy-tool.html
Posted by David Blevins <da...@visi.com>.
On Aug 22, 2007, at 1:49 PM, Karan Malhi wrote:
> On 8/21/07, David Blevins <da...@visi.com> wrote:
>> On a different note.... I cc'ed the jira@apache.org list and it
>> totally added a comment on the issue with my email text and the prior
>> content trimmed out. Very cool!
>>
>> We should totally use that more often!
>
> I just tried it and this is a really awesome feature. So, do I just
> need the JIRA issue number in my subject? Is that what jira is looking
> for in the email?
Not sure. Feel free to create a test issue and send a bunch of
emails to jira@apache.org till you figure it out. There might be
docs too, but that doesn't sound like nearly as much fun....
-David
Re: [jira] Resolved: (OPENEJB-636) doc: deploy-tool.html
Posted by Karan Malhi <ka...@gmail.com>.
On 8/21/07, David Blevins <da...@visi.com> wrote:
> On a different note.... I cc'ed the jira@apache.org list and it
> totally added a comment on the issue with my email text and the prior
> content trimmed out. Very cool!
>
> We should totally use that more often!
I just tried it and this is a really awesome feature. So, do I just
need the JIRA issue number in my subject? Is that what jira is looking
for in the email?
--
Karan Singh Malhi
Re: [jira] Resolved: (OPENEJB-636) doc: deploy-tool.html
Posted by David Blevins <da...@visi.com>.
On a different note.... I cc'ed the jira@apache.org list and it
totally added a comment on the issue with my email text and the prior
content trimmed out. Very cool!
We should totally use that more often!
-David
On Aug 21, 2007, at 1:50 PM, David Blevins wrote:
> Thanks, Manu!
>
> I noticed my notes weren't quite complete and the page as far more
> outdated that I had commented, so I went ahead and did some more
> updates to this page.
>
> Great job on these new docs!
>
> -David
>
>
> On Aug 19, 2007, at 9:13 PM, Manu T George (JIRA) wrote:
>
>>
>> [ https://issues.apache.org/jira/browse/OPENEJB-636?
>> page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>
>> Manu T George resolved OPENEJB-636.
>> -----------------------------------
>>
>> Resolution: Fixed
>> Fix Version/s: 3.0
>>
>>> doc: deploy-tool.html
>>> ---------------------
>>>
>>> Key: OPENEJB-636
>>> URL: https://issues.apache.org/jira/browse/
>>> OPENEJB-636
>>> Project: OpenEJB
>>> Issue Type: Sub-task
>>> Reporter: David Blevins
>>> Assignee: Manu T George
>>> Priority: Blocker
>>> Fix For: 3.0
>>>
>>>
>>
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>
>
Re: [jira] Resolved: (OPENEJB-636) doc: deploy-tool.html
Posted by David Blevins <da...@visi.com>.
Thanks, Manu!
I noticed my notes weren't quite complete and the page as far more
outdated that I had commented, so I went ahead and did some more
updates to this page.
Great job on these new docs!
-David
On Aug 19, 2007, at 9:13 PM, Manu T George (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/OPENEJB-636?
> page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Manu T George resolved OPENEJB-636.
> -----------------------------------
>
> Resolution: Fixed
> Fix Version/s: 3.0
>
>> doc: deploy-tool.html
>> ---------------------
>>
>> Key: OPENEJB-636
>> URL: https://issues.apache.org/jira/browse/
>> OPENEJB-636
>> Project: OpenEJB
>> Issue Type: Sub-task
>> Reporter: David Blevins
>> Assignee: Manu T George
>> Priority: Blocker
>> Fix For: 3.0
>>
>>
>
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[jira] Resolved: (OPENEJB-636) doc: deploy-tool.html
Posted by "Manu T George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manu T George resolved OPENEJB-636.
-----------------------------------
Resolution: Fixed
Fix Version/s: 3.0
> doc: deploy-tool.html
> ---------------------
>
> Key: OPENEJB-636
> URL: https://issues.apache.org/jira/browse/OPENEJB-636
> Project: OpenEJB
> Issue Type: Sub-task
> Reporter: David Blevins
> Assignee: Manu T George
> Priority: Blocker
> Fix For: 3.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.