Hi professor, Yes. I filed a bug report. https://issues.apache.org/jira/browse/OODT-823
— aditya Aditya Dhulipala USC Viterbi adhul...@usc.edu > On Feb 22, 2015, at 4:58 PM, Mattmann, Chris A (3980) > <chris.a.mattm...@jpl.nasa.gov> wrote: > > Yep this is a JDK8 issue. Can you file a bug report? > > https://issues.apache.org/jira/browse/OODT > > Thank you we’ll take a look. > > Cheers, > Chris > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Chief Architect > Instrument Software and Science Data Systems Section (398) > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 168-519, Mailstop: 168-527 > Email: chris.a.mattm...@nasa.gov > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Associate Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > > > -----Original Message----- > From: Aditya Dhulipala <adhul...@usc.edu> > Reply-To: "dev@oodt.apache.org" <dev@oodt.apache.org> > Date: Sunday, February 22, 2015 at 4:37 PM > To: "dev@oodt.apache.org" <dev@oodt.apache.org> > Subject: Re: OODT ./filemgr start gives me a error -- Can't load log > handler "java.util.logging.FileHandler"` > >> Yes, I just checked. I'm on jdk8. >> >> Also I ran the install using mvn3 on another manchine with jdk7. That >> works >> fine. >> >> >> -- >> Aditya >> >> >> >> adi >> >> On Sun, Feb 22, 2015 at 3:15 PM, Tyler Palsulich <tpalsul...@gmail.com> >> wrote: >> >>> Java 8 is just a problem child with Maven + testing. So, definitely >>> worth a >>> shot. >>> >>> Tyler >>> >>> >>> >>> On Sun, Feb 22, 2015 at 6:03 PM, Mattmann, Chris A (3980) < >>> chris.a.mattm...@jpl.nasa.gov> wrote: >>> >>>> Not sure this is a Maven2 versus Maven3 issue. It may be an issue >>>> with your JDK8. Do you happen to be using JDK8? It seems javadoc >>>> has grown quite strict: >>>> >>>> >>> >>> http://stackoverflow.com/questions/22528767/jdk8-and-javadoc-has-become-v >>> er >>>> y-strict >>>> >>>> >>>> My wonder is if Maven2 (being older) uses older Jar files and thus >>>> forces an older compatibility mode with Javadoc; whereas Maven3 >>>> happily accepts the strict JDK8 issue. >>>> >>>> Can you please confirm? >>>> >>>> Cheers, >>>> Chris >>>> >>>> >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>> Chris Mattmann, Ph.D. >>>> Chief Architect >>>> Instrument Software and Science Data Systems Section (398) >>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >>>> Office: 168-519, Mailstop: 168-527 >>>> Email: chris.a.mattm...@nasa.gov >>>> WWW: http://sunset.usc.edu/~mattmann/ >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>> Adjunct Associate Professor, Computer Science Department >>>> University of Southern California, Los Angeles, CA 90089 USA >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>> >>>> >>>> >>>> >>>> >>>> >>>> -----Original Message----- >>>> From: Aditya Dhulipala <adhul...@usc.edu> >>>> Reply-To: "dev@oodt.apache.org" <dev@oodt.apache.org> >>>> Date: Tuesday, February 17, 2015 at 11:20 AM >>>> To: "dev@oodt.apache.org" <dev@oodt.apache.org> >>>> Subject: Re: OODT ./filemgr start gives me a error -- Can't load log >>>> handler "java.util.logging.FileHandler"` >>>> >>>>> Here’s a link to the console output. >>>>> http://pastebin.com/WzRjKHH5 >>>>> >>>>> Its the result of using mvn3 in the beginning, then followed by my >>>>> time-consuming attempt at getting mvn2 >>>>> and then the build-result of using mvn2 >>>>> >>>>> >>>>> >>>>> here’s a gist of the output from the above link >>>>> [INFO] >>>> >>>> ------------------------------------------------------------------------ >>>>> [INFO] Reactor Summary: >>>>> [INFO] >>>>> [INFO] OODT Core .......................................... SUCCESS [ >>>>> 17.063 s] >>>>> [INFO] Common Utilities ................................... FAILURE [ >>>>> 14.560 s] >>>>> [INFO] CAS Command Line Interface ......................... SKIPPED >>>>> [INFO] Process Control System Input Data Package .......... SKIPPED >>>>> [INFO] Catalog and Archive Service Generic Multi-valued Metadata >>>>> Container SKIPPED >>>>> [INFO] CAS Protocol ....................................... SKIPPED >>>>> [INFO] CAS Protocol FTP Implementation .................... SKIPPED >>>>> [INFO] CAS Protocol HTTP Implementation ................... SKIPPED >>>>> [INFO] CAS Protocol IMAPS Implementation .................. SKIPPED >>>>> [INFO] CAS Protocol SFTP Implementation ................... SKIPPED >>>>> [INFO] Query Expression ................................... SKIPPED >>>>> [INFO] OODT Single Sign On Security Package ............... SKIPPED >>>>> [INFO] Catalog and Archive File Management Component ...... SKIPPED >>>>> [INFO] OODT CAS Virtual Catalog and Integration Service. .. SKIPPED >>>>> [INFO] Catalog and Archive Resource Management Component .. SKIPPED >>>>> [INFO] Catalog and Archive Workflow Management Component .. SKIPPED >>>>> [INFO] Catalog and Archive Crawling Framework ............. SKIPPED >>>>> [INFO] CAS Curation Interface ............................. SKIPPED >>>>> [INFO] CAS PGE Adaptor Framework .......................... SKIPPED >>>>> [INFO] CAS Installer Maven Mojo ........................... SKIPPED >>>>> [INFO] OODT :: Archetypes :: OpsUI ........................ SKIPPED >>>>> [INFO] OODT :: Archetypes :: RADiX ........................ SKIPPED >>>>> [INFO] OODT :: Archetypes ................................. SKIPPED >>>>> [INFO] CAS Push-Pull-Framework ............................ SKIPPED >>>>> [INFO] Product Service .................................... SKIPPED >>>>> [INFO] Profile Service .................................... SKIPPED >>>>> [INFO] OODT Web Grid ...................................... SKIPPED >>>>> [INFO] XML-configured, DBMS-based Product and Profile Server SKIPPED >>>>> [INFO] Apache OODT Configurable OPeNDAP Profile Server .... SKIPPED >>>>> [INFO] Process Control System Core Package ................ SKIPPED >>>>> [INFO] OODT Wicket Web Components ......................... SKIPPED >>>>> [INFO] CAS File Manager Browser Web App ................... SKIPPED >>>>> [INFO] CAS Product Server Web Application ................. SKIPPED >>>>> [INFO] CAS Workflow Manager Monitor Web App ............... SKIPPED >>>>> [INFO] Catalog and Archive File Management Browser ........ SKIPPED >>>>> [INFO] Catalog and Archive Workflow Management GUI Editor . SKIPPED >>>>> [INFO] Process Control System Operator Interface Webapp ... SKIPPED >>>>> [INFO] OODT Process Control System JAX-RS service layer ... SKIPPED >>>>> [INFO] Apache OODT ........................................ SKIPPED >>>>> [INFO] >>>> >>>> ------------------------------------------------------------------------ >>>>> [INFO] BUILD FAILURE >>>>> [INFO] >>>> >>>> ------------------------------------------------------------------------ >>>>> [INFO] Total time: 33.047 s >>>>> [INFO] Finished at: 2015-02-16T20:36:45-08:00 >>>>> [INFO] Final Memory: 35M/351M >>>>> [INFO] >>>> >>>> ------------------------------------------------------------------------ >>>>> [ERROR] Failed to execute goal >>>>> org.apache.maven.plugins:maven-javadoc-plugin:2.9:javadoc >>>>> (attach-javadocs) on project oodt-commons: An error has occurred in >>>>> JavaDocs report generation: >>>>> [ERROR] Exit code: 1 - >>>> >>> >>>> /Users/Aditya/Projects/apache-oodt-0.8.1/commons/src/main/java/org/apach >>>> e/ >>>>> oodt/commons/activity/SQLDatabaseRetrieval.java:66: error: unexpected >>> end >>>>> tag: </p> >>>>> [ERROR] </p> >>>>> [ERROR] ^ >>>>> [ERROR] >>>> >>> >>>> /Users/Aditya/Projects/apache-oodt-0.8.1/commons/src/main/java/org/apach >>>> e/ >>>>> oodt/commons/activity/SQLDatabaseRetrieval.java:78: error: unexpected >>> end >>>>> tag: </p> >>>>> [ERROR] </p> >>>>> [ERROR] ^ >>>>> >>>>> >>>>> The link also has the output from using mvn2 (after scrolling more >>> than >>>>> half-way) >>>>> >>>>> Thnaks! >>>>> >>>>> >>>>> — >>>>> aditya >>>>> >>>>> Aditya Dhulipala >>>>> USC Viterbi >>>>> adhul...@usc.edu >>>>> >>>>> >>>>> >>>>> >>>>>> On Feb 17, 2015, at 9:02 AM, Chris Mattmann <mattm...@apache.org> >>>> wrote: >>>>>> >>>>>> Hmm builds fine with maven3 for me: >>>>>> >>>>>> [dhcp-137-79-202-145:~] mattmann% java -version >>>>>> java version "1.7.0_60" >>>>>> Java(TM) SE Runtime Environment (build 1.7.0_60-b19) >>>>>> Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode) >>>>>> [dhcp-137-79-202-145:~] mattmann% uname -a >>>>>> Darwin dhcp-137-79-202-145.jpl.nasa.gov 13.4.0 Darwin Kernel >>> Version >>>>>> 13.4.0: Sun Aug 17 19:50:11 PDT 2014; >>>>>> root:xnu-2422.115.4~1/RELEASE_X86_64 >>>>>> x86_64 >>>>>> [dhcp-137-79-202-145:~] mattmann% mvn -version >>>>>> Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; >>>>>> 2014-08-11T13:58:10-07:00) >>>>>> Maven home: /usr/local/Cellar/maven/3.2.3/libexec >>>>>> Java version: 1.7.0_60, vendor: Oracle Corporation >>>>>> Java home: >>>>>> /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home/jre >>>>>> Default locale: en_US, platform encoding: UTF-8 >>>>>> OS name: "mac os x", version: "10.9.5", arch: "x86_64", family: >>> "mac" >>>>>> [dhcp-137-79-202-145:~] mattmann% >>>>>> >>>>>> >>>>>> >>>>>> -----Original Message----- >>>>>> From: Michael Joyce <jo...@apache.org> >>>>>> Reply-To: <dev@oodt.apache.org> >>>>>> Date: Tuesday, February 17, 2015 at 8:25 AM >>>>>> To: "dev@oodt.apache.org" <dev@oodt.apache.org> >>>>>> Subject: Re: OODT ./filemgr start gives me a error -- Can't load >>> log >>>>>> handler "java.util.logging.FileHandler"` >>>>>> >>>>>>> Strange that it was failing with maven 3. I thought that had been >>>>>>> resolved. >>>>>>> Maybe I'm mixing issues together in my mind. If it's still >>> breaking >>> for >>>>>>> you >>>>>>> then we should definitely open up a new ticket >>>>>>> >>>>>>> >>>>>>> -- Joyce >>>>>>> >>>>>>> On Mon, Feb 16, 2015 at 10:42 PM, Aditya Dhulipala >>> <adhul...@usc.edu >>>> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Micheal, >>>>>>>> >>>>>>>> Thanks for your response! >>>>>>>> >>>>>>>> OK. I’ll try that. I’ll create ../logs >>>>>>>> >>>>>>>> Yeah there were some issues I ran into while building oodt. It >>> failed >>>>>>>> the >>>>>>>> first time i tired mvn install. But that happened because I was >>> using >>>>>>>> mvn >>>>>>>> version3. I installed mvn2 and it worked fine. This is probably a >>>>>>>> minor >>>>>>>> issue but maybe we can raise an issue for support for mvn3… >>>>>>>> >>>>>>>> So far I’ve not run into any other issues. I’ll shoot a message >>> if I >>>>>>>> do. >>>>>>>> Thanks for helping me out! >>>>>>>> >>>>>>>> — >>>>>>>> adi >>>>>>>> >>>>>>>> Aditya Dhulipala >>>>>>>> USC Viterbi >>>>>>>> adhul...@usc.edu >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On Feb 16, 2015, at 9:38 PM, Michael Starch <starc...@umich.edu> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Aditya, >>>>>>>>> >>>>>>>>> Did you create a logs directory? It is missing the directory, >>> so >>> it >>>>>>>> cannot >>>>>>>>> create your log files. Otherwise, it looks ok. It seems to >>> have >>>>>>>> started, >>>>>>>>> any other issues? >>>>>>>>> >>>>>>>>> Michael >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Feb 16, 2015 at 9:30 PM, Aditya Dhulipala < >>> adhul...@usc.edu> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> I'm trying to run filmgr component of oodt >>>>>>>>>> >>>>>>>>>> I'm running steps off from this guide - >>>>>>>>>> >>>>>>>> >>>>>>>> >>>> >>> https://cwiki.apache.org/confluence/display/OODT/OODT+Filemgr+User+Guid >>>>>>>> e >>>>>>>>>> >>>>>>>>>> On executing ./filemgr start I get the following error:- >>>>>>>>>> http://pastebin.com/cudQPmAa >>>>>>>>>> >>>>>>>>>> Can anybody take a look and help me out? >>>>>>>>>> >>>>>>>>>> Thanks! >>>>>>>>>> -- >>>>>>>>>> Aditya >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> adi >>>>>>>>>> >>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >
