Hi Brian, On Jan 30, 2012, at 3:27 PM, Brian Foster wrote:
> Hey Chris, > > Sorry I kinda fell of the grid there for a bit... Google got busy and I got > tonsillitis... don't ever get that! It really sucks!... Ugh sorry dude, feel better. > basically the command line flags/options which existed before which set > properties on CrawlerActions would not exist anymore... they would just be > configurable via Java properties... the other option is to just leave it > working the same way and those flags will always show up as optional... > basically help will not give you any analysis on how those flags are used... > however when you run the crawler and use those flags they will still be > analyzed. I don't think I explained that well at all... Haha that's OK the bottom part I think did the trick for me. > basically the current trunk crawler's help is not accurate when dealing with > flags used to set properties of CrawleActions... it only enforces their rules > when actually running the crawler. OK, then I'd be +1 for the command line to remain the same even if the cmd line option analysis from the help menu isn't accurate. We can work to improve the accuracy but I'd rather not break the interface. My 2c. Feel better dude! Cheers, Chris > "Mattmann, Chris A (388J)" <chris.a.mattm...@jpl.nasa.gov> wrote: > >> Hey Brian, >> >> On Jan 18, 2012, at 3:02 PM, Brian Foster wrote: >> >>> Hey guys... I've been slowly chuggin away at integrating cas-cli into >>> cas-crawler... busy few weeks at work... but I'm also kinda stuck on >>> something... currently the crawler supports command line options which >>> configure crawler actions (not command line actions), however there is no >>> way to display the help for these (i.e. whether they are required or >>> not)... this is because they become required only if another option (i.e. >>> -ais) is specified with their action id... new cas-cli doesn't support this >>> either and I initially thought about adding this feature to cas-cli but >>> didn't for simplicity sake (cas-cli is complex enough)... so I'm think of >>> just make crawler action configurable via java properties... this will not >>> change the currently implemented classes at all or the way actions are >>> written in the future... basically spring will just set its properties for >>> these actions by using java properties instead... what u guys thing? >> >> I'd be +1 for this if the command line for the crawler worked the same way. >> Are you proposing >> that CrawlerLauncher would now simply read command line actions and then >> have the >> Crawler's CommandLine actions set Spring java properties which would then be >> ready by the >> CrawlerActions? >> >> Cheers, >> Chris >> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Chris Mattmann, Ph.D. >> Senior Computer Scientist >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> Office: 171-266B, Mailstop: 171-246 >> Email: chris.a.mattm...@nasa.gov >> WWW: http://sunset.usc.edu/~mattmann/ >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Adjunct Assistant Professor, Computer Science Department >> University of Southern California, Los Angeles, CA 90089 USA >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
