|
Hi Sal, Setting the maven.junit.jvmargs with right
values got me the sweet success whereas turning off the fork option was junit
made matters only worse. In any case, thanks a lot for your
patience in helping me out. Hopefully, I would be able to submit a BUILD.txt document
patch for this (and perhaps others). /Pankaj. From: Campana Jr.,
Salvatore J Not sure if this will help but you can try
setting the proxy for the the junit plugin... Add this line in project.properties: maven.junit.jvmargs=-DproxySet=true
-Dhttp.proxyHost=your_proxy_host -Dhttp.proxyPort=your_proxy_port see if that helps...As a test I ran on
mine with bogus entries and everything still worked, so I don't have the
highest confidence in this....At least we got past one problem, your last
output definately wasn't load SushiProperties.xsd because that dir wasn't being
created....This message is new.... -S From: Kumar,
Pankaj Well, I still get the error, but I noticed
something else which may be relevant: test:test: [junit] Running
org.apache.ws.resource.properties.impl.XmlBeansResourcePrope rtySetMetaDataTestCase [junit] Loading schema
file C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ws.apache.org \apollo\SushiProperties.xsd [junit] C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ws.apache.org\apollo\SushiPropert ies.xsd:0: error:
java.net.ConnectException: Connection refused: connect [junit]
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ws.apache.org\apollo\SushiPropert ies.xsd:0: error: Element [EMAIL PROTECTED]://docs.oasis-open.org/wsrf/2004/06/ws rf-WS-ResourceLifetime-1.2-draft-01.xsd
not found. [junit]
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ws.apache.org\apollo\SushiPropert ies.xsd:0: error: Element
[EMAIL PROTECTED]://docs.oasis-open.org/wsrf/2004/0 6/wsrf-WS-ResourceLifetime-1.2-draft-01.xsd
not found. [junit]
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ws.apache.org\apollo\SushiPropert ies.xsd:0: error: Element
[EMAIL PROTECTED]://docs.oasis-open.org/wsrf/2004/06/ws rf-WS-ResourceLifetime-1.2-draft-01.xsd
not found. [junit]
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ws.apache.org\apollo\SushiPropert ies.xsd:0: error: Element
[EMAIL PROTECTED]://docs.oasis-open.org/wsrf/2004/0 6/wsrf-WS-ResourceLifetime-1.2-draft-01.xsd
not found. [junit] Time to build schema
type system: 2.644 seconds [junit] BUILD FAILED [junit]
java.lang.ExceptionInInitializerError
[junit] at java.lang.Class.forName0(Native Method) [junit]
at java.lang.Class.forName(Class.java:141) Looks
like that the junit test is not able to retrieve a XSD file from OASIS site. I
recall setting my web proxy host and port in Maven (that is how it is able to
download the jars). But do I need to set these somewhere else also? /Pankaj. From: 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 Hi Sal, Here is the output of “maven clean
dist –X” as an attachement. /Pankaj From: 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 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: 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: 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 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 |
- RE: Sweet success (was RE: Few questions on build... Kumar, Pankaj
- RE: Sweet success (was RE: Few questions on ... Campana Jr., Salvatore J
