Hi,

I've just read the email chain :-) sorry that I've not been available for 
comment.

I don't have access to my laptop at this moment. So I guess if the changes need 
to happen now, I'm very happy if Paul or Brian make the change. They seem to be 
on top of the issue. 

Kind regards from Hamburg,
Tom. 
--
Thomas Bennett

SKA South Africa

Office: +2721 506 7341
Mobile: +2779 523 7105
Email: [email protected]


On 17 Jun 2012, at 7:11 AM, "Ramirez, Paul M (388J)" 
<[email protected]> wrote:

> I don't mind rolling a new one. 
> 
> --Paul
> 
> Sent from my iPhone
> 
> On Jun 16, 2012, at 11:58 AM, "Brian Foster" <[email protected]> wrote:
> 
>> 
>> Paul what do you think?
>> 
>> Begin forwarded message:
>> 
>>> From: "Chris A. Mattmann (JIRA)" <[email protected]>
>>> Date: June 16, 2012 9:08:42 AM PDT
>>> To: [email protected]
>>> Subject: [jira] [Commented] (OODT-454) Crawler command line bugs
>>> Reply-To: [email protected]
>>> 
>>> 
>>>  [ 
>>> https://issues.apache.org/jira/browse/OODT-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13296174#comment-13296174
>>>  ] 
>>> 
>>> Chris A. Mattmann commented on OODT-454:
>>> ----------------------------------------
>>> 
>>> Hrm -- should we respin? Good question -- I'm thinking we can always wrap 
>>> this up on an quick 0.5 that wraps everything else up that's still 
>>> lingering. Feel free to ask Paul what he thinks since he is the RM.
>>> 
>>>> Crawler command line bugs
>>>> -------------------------
>>>> 
>>>>              Key: OODT-454
>>>>              URL: https://issues.apache.org/jira/browse/OODT-454
>>>>          Project: OODT
>>>>       Issue Type: Bug
>>>>       Components: crawler
>>>> Affects Versions: 0.4
>>>>         Reporter: Thomas Bennett
>>>>         Assignee: Thomas Bennett
>>>>         Priority: Minor
>>>>           Labels: patch
>>>>          Fix For: 0.5
>>>> 
>>>> 
>>>> I've think I've flushed out a few crawler command line bugs:
>>>> 1) --actionIds can currently fails when more than 1 actionId is specified
>>>> 2) ActionId Unique fails because the filemgrUrl is not set.
>>>> 3) ActionId TriggerPostIngestWorkflow is not configured correctly.
>>> 
>>> --
>>> This message is automatically generated by JIRA.
>>> If you think it was sent incorrectly, please contact your JIRA 
>>> administrators: 
>>> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>> 
>>> 

Reply via email to