Hi, Sorry for the late reply. I'm at isc12 in Hamburg and have been traveling with no Internet access.
I'm okay to push to 0.5 - its a really minor issue. Thanks for the reply. Chuss, Tom. -- Thomas Bennett SKA South Africa Office: +2721 506 7341 Mobile: +2779 523 7105 Email: [email protected] On 15 Jun 2012, at 5:45 AM, "Chris A. Mattmann (JIRA)" <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/OODT-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295440#comment-13295440 > ] > > Chris A. Mattmann commented on OODT-454: > ---------------------------------------- > > Hey Tom! > > bq. I've just realised this issues is still open. Sorry! > > No worries! > > bq. An annoying question - do I keep the TriggerPostIngestWorkflow or use the > UpdateWorkflowStatusToIngest? > > I would prefer that (for back compat perspective) we leave it as it was > (UpdateWorkflowStatusToIngest). > > bq. Is there still time to close this issue before 0.4 release? Issue 1) has > fallen away and I need to commit to resolve issue 2) and 3) (see the 3 issues > in the Description). > > I would just set it for 0.5 unless you think this is critical for a respin. > If you think so, just let pramirez know on the dev list and we can DISCUSS a > respin. No worries if that's the case! > > Thanks man. > > > >> 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.4 >> >> >> 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 > >
