RE: Few questions on building apollo from source

[Campana Jr., Salvatore J]

I just checked in a change to that unit test...The code did not call mkdirs()...so I'm assuming that is why you had the issue...Please update and try again, if you still have a problem let me know...     -S From: Kumar, Pankaj Sent: Tuesday, March 29, 2005 4:46 PM To: apollo-dev@ws.apache.org Subject: RE: Few questions on building apollo from source Hi Sal,   Here is the output of “maven clean dist –X” as an attachement.   /Pankaj   From: Campana Jr., Salvatore J Sent: Tuesday, March 29, 2005 12:03 PM To: apollo-dev@ws.apache.org Subject: RE: Few questions on building apollo from source   Pankaj,   Can you try running "maven dist -X" and send the output to a file?  The -X will force maven to be more verbose and maybe we can see what is going on...My local maven dist ran fine...   You can also do a "maven clean dist -X"...though I assume you have nothing to "clean" from past attempts....   I am noticing delays in the maven script which I assume are due to maintenance at Apache...It's been happening quite a bit recently and affects our maven scripts because maven attempts to pull some depencies during the dist (not the ones in the beginning, this is later on..)....   As for working straight from source there are quite a few "points" since you would need to: generate the webapp, deploy it, point to it, and then run the ant scripts to generate,compille and deploy....Allot of that is easier, at least initially, to start from a dist....Then once you have that all working, it is much easier to work straight from the src distro....   -S   From: Kumar, Pankaj Sent: Tuesday, March 29, 2005 1:22 PM To: apollo-dev@ws.apache.org Subject: RE: Few questions on building apollo from source Thanks Sal. I did “svn update” and the downloads go through fine now. However, I do get the following exception during junit test execution:   …. test:compile:     [javac] Compiling 19 source files to C:\review\apollo\target\test-classes     [copy] Copying 3 files to C:\review\apollo\target\test-classes     [copy] Copied 1 empty directory to C:\review\apollo\target\test-classes   test:test:     [junit] Running org.apache.ws.resource.properties.impl.XmlBeansResourcePrope rtySetMetaDataTestCase     [junit] java.lang.ExceptionInInitializerError [junit]     at java.lang.Class.forName0(Native Method) ….   Suspecting that this is a JDK problem (I have had horros with xmlbeans and JDK1.5 in the past), went back to JDK1.4.2_03 but the problem persists. Is this something known? Should I just comment out the test execution?   You suggest that I should do a “maven dist” and then install from the zip for running examples. This will do for the time being. But eventually, I will be writing my programs and I have a feeling that I may have to change the Apollo sources. I guess, by that time I will figure out how to work with Apollo sources directly. Still, I think it will good to have some points in BUILD.txt for “ambitious developers”.   /Pankaj.       From: Campana Jr., Salvatore J Sent: Tuesday, March 29, 2005 8:35 AM To: apollo-dev@ws.apache.org Subject: RE: Few questions on building apollo from source   Pankaj,   The repo has been updated....Make sure to update Apollo from svn to get the new project.properties AND project.xml files to ensure you'll get the jars...   -Sal   From: Campana Jr., Salvatore J Sent: Tuesday, March 29, 2005 10:48 AM To: apollo-dev@ws.apache.org Subject: RE: Few questions on building apollo from source Pankaj,   The build.txt was meant to get project developers building quickly, you want a dist for running examples....   Please run "maven dist"...then look in the target/distributions for a dist to be built....Unzip the generated dist zip file to a directory and then follow the included tutorial...you can get there by starting with the README.html file in the root of the distribution....   "maven jar" is for simply building the jar itself, but you are not meant to "work" out of the src dir, only out of a distribution....   As for the naming-* files, the Apache directory project just got out of incubation and the jars have moved...Ian will add them to his repository when he gets in....Please do another update in Apollo to pull the updated project.properties file...There was a change to this file due to some Apache maintenance...   -S   From: Kumar, Pankaj Sent: Monday, March 28, 2005 7:17 PM To: apollo-dev@ws.apache.org Subject: Few questions on building apollo from source Hi,   I did an anon. SVN checkout of the Apollo sources, did Maven install and fired “maven jar” (as per the BUILD.txt).   The build failed with following messages:   The build cannot continue because of the following unsatisfied dependencies:   naming-core-0.8.jar (try downloading from http://incubator.apache.org/directory/subprojects/naming/) naming-factory-0.8.jar (try downloading from http://incubator.apache.org/directory/subprojects/naming/) naming-java-0.8.jar (try downloading from http://incubator.apache.org/directory/subprojects/naming/)   How do I get around this?   Also, I noticed that BUILD.txt doesn’t say what to do after “maven jar” succeeds. It would be nice to have a pointer to build/run examples or to the tutorial.   Another thing I want to mention is that I have subscribed to only Apollo-dev mailing list but keep getting all the SVN commit messages sent to Apollo-cvs mailing list.   Thanks in advance, Pankaj Kumar