Oh... yes. On Mon, Aug 8, 2011 at 12:48 PM, ChiaHung Lin <[email protected]> wrote: > > Starting bsp with new svn repos content, I notice there would have errors as > below. This seems because the lib within core/ directory is not copied from > core/target/lib. > > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/hadoop/conf/Configuration > Caused by: java.lang.ClassNotFoundException: > org.apache.hadoop.conf.Configuration > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:247) > Could not find the main class: org.apache.hama.zookeeper.ZKServerTool. > Program will exit. > starting bspmaster, logging to > hama-trunk/core/bin/../logs/hama-clin-bspmaster-lab01.out > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/hadoop/util/Tool > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) > at java.lang.ClassLoader.defineClass(ClassLoader.java:615) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) > at java.net.URLClassLoader.access$000(URLClassLoader.java:58) > at java.net.URLClassLoader$1.run(URLClassLoader.java:197) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > > > -----Original message----- > From:Hudson (JIRA) <[email protected]> > To:[email protected] > Date:Fri, 5 Aug 2011 08:34:27 +0000 (UTC) > Subject:[jira] [Commented] (HAMA-417) Refactoring of the Maven structure > > > [ > https://issues.apache.org/jira/browse/HAMA-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079827#comment-13079827 > ] > > Hudson commented on HAMA-417: > ----------------------------- > > Integrated in Hama-Nightly #275 (See > [https://builds.apache.org/job/Hama-Nightly/275/]) > [HAMA-417] - removed unnecessary files in source directory of site module > > tommaso : > Files : > * /incubator/hama/trunk/site/src/webapps > * /incubator/hama/trunk/site/src/test > * /incubator/hama/trunk/site/src/java > * /incubator/hama/trunk/site/src/examples > > >> Refactoring of the Maven structure >> ---------------------------------- >> >> Key: HAMA-417 >> URL: https://issues.apache.org/jira/browse/HAMA-417 >> Project: Hama >> Issue Type: Improvement >> Components: build >> Affects Versions: 0.3.0 >> Reporter: Tommaso Teofili >> Assignee: Tommaso Teofili >> Fix For: 0.4.0 >> >> Attachments: HAMA-417.patch, HAMA-417_2.patch, HAMA-417_3.patch, >> HAMA-417_4.patch, HAMA-417_5.patch >> >> >> The current structure of the project makes separate management/releasing of >> core and examples artifacts complicated as the source directory is selected >> upon profile activation. >> The proposed solution is to create a common parent POM (hama-parent) in the >> SVN top node, and then two modules 'core' and 'examples' which can be >> tested/managed/released separately (and better, hopefully). >> This will also allow further refactoring and additions of new modules. > > -- > This message is automatically generated by JIRA. > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > > > -- > ChiaHung Lin > Department of Information Management > National University of Kaohsiung > Taiwan >
-- Best Regards, Edward J. Yoon @eddieyoon
