Jeremy, Your step (2) is:
> 2) same as you but import the woden/java directory not the > woden directory. This will give you a .classpath file as well The problem is that you removed the .project file under the woden/java directory [1]. Eclipse won't list this directory as a target for importing if it can't find a .project file. I worked around this by copying the .project file from woden/tags/M5_20060611 and changing the <name> element. Given that you can't really have a .project file in SVN that works for everybody, all I can suggest is a default 'project-rename-me' file along with instructions to 'mv project-name-me .project' the first time you setup Woden. - gp [1] http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200607.mbox/%3cadb [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Jeremy Hughes > Sent: Tuesday, August 01, 2006 1:10 AM > To: [email protected] > Subject: Fwd: Many JUnit tests failing due incorrect namespace URI > > Whoops forgot to cc the list > > ---------- Forwarded message ---------- > From: Jeremy Hughes <[EMAIL PROTECTED]> > Date: Aug 1, 2006 9:08 AM > Subject: Re: Many JUnit tests failing due incorrect namespace URI > To: Gilbert Pilz <[EMAIL PROTECTED]> > > > Hi Gilbert, > > On 8/1/06, Gilbert Pilz <[EMAIL PROTECTED]> wrote: > > Jeremy, > > > > I'm a bit confused. What are the steps for downloading and building > > Woden? I have been doing the following: > > > > 1.) cd c:/apache > > > > 1.) svn co http://svn.apache.org/repos/asf/incubator/woden/ > > > > 2.) From Eclipse: "File->Import"; select "Existing Projects into > > Workspace"; select "C:/apache/woden" as the root directory. > From there > > it gives me the choice of importing either "Site" (by which > it means > > C:/apache/woden/Site/.project), "java" > > (C:/apache/woden/tags/M2_20051207/.project), "java" > > (C:/apache/woden/tags/M4_20060313/.project), or "java" > > (C:/apache/woden/tags/M5_20060611/.project). > > > > I don't see any easy of importing C:/apache/woden/java/.. > into Eclipse. > > Am I missing something? > > I use the subclipse plugin [1] which does for Subversion what > the CVS plugin (built into Eclipse) does for CVS. Using > subclipse I don't need to go to the command line to extract > from subversion. > > Anyway for now if you do: > > 1) svn co http://svn.apache.org/repos/asf/incubator/woden/java > > (our trunk is currently in the .../woden/java directory - we > have a JIRA to move it to .../woden/trunk/java). > > 2) same as you but import the woden/java directory not the > woden directory. This will give you a .classpath file as well > > 3) you need to drag down the dependencies Woden has ... > either using the command line (cd java; ant) - make sure you > have ant installed an on the PATH. Or you can use ant built > into eclipse to run the default target of the woden > build.xml. This will download the relevant jars Woden depends > on. Then you will to refresh the eclipse view of the > filesystem to get it to see the dependent jars. > > btw: By checking out .../woden instead of .../woden/java you > have checked out all of the branches, tagged levels, web site > - everything!! Probably not what you wanted. > > Clearly our developer instructions aren't good enough. I > shall fix - or at least open a JIRA to fix :-) > > [1] http://subclipse.tigris.org > > HTH, > Jeremy > > > > > - gp > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of > > > Jeremy Hughes > > > Sent: Friday, July 28, 2006 12:37 AM > > > To: [email protected] > > > Subject: Re: Many JUnit tests failing due incorrect namespace URI > > > > > > Gilbert, the structure of our code in SVN is a bit unusual. > > > Our 'trunk' is actually here: > > > http://svn.apache.org/repos/asf/incubator/woden/java .. > we do have a > > > JIRA to changes this - move to ....woden/trunk/java - and > there are > > > now 281 tests or thereabouts :-) > > > > > > Regards, > > > Jeremy > > > > > > On 7/28/06, Gilbert Pilz <[EMAIL PROTECTED]> wrote: > > > > Sorry. The problem occurred when I imported Woden into > > > Eclipse. I told > > > > it to import from "woden" and it gave me 4 choices > "Site", "java", > > > > "java", and "java"; naturally I picked the first 'java' and > > > ended up > > > > building and testing M2_20051207. > > > > > > > > I've since imported M5_20060611 and all 160 tests completed > > > > successfully. > > > > > > > > - gp > > > > > > > > > -----Original Message----- > > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > > Behalf Of > > > > > Jeremy Hughes > > > > > Sent: Thursday, July 27, 2006 3:17 AM > > > > > To: [email protected] > > > > > Subject: Re: Many JUnit tests failing due incorrect namespace > > > > > URI > > > > > > > > > > Hi, > > > > > > > > > > I just did a fresh svn checkout, set classpath for JUNIT then > > > > > ant runTests. All tests pass. > > > > > > > > > > From the error you're seeing, you probably have an > old level of > > > > > woden (from January). > > > > > > > > > > The spec moved from the 2005/08 to the 2006/01 level in > > > January and > > > > > we changed Woden accordingly to expect namespaces > with 2006/01. > > > > > > > > > > You could either re-checkout woden and build and run the > > > tests or if > > > > > you only want binaries, you could download from here: > > > > > > > > > > > > > > http://people.apache.org/dist/ws/woden/milestones/1.0.0M5-incubating > > > > > / > > > > > > > > > > Cheers, > > > > > Jeremy > > > > > > > > > > On 7/26/06, Gilbert Pilz <[EMAIL PROTECTED]> wrote: > > > > > > Apologies if this has already been discussed on the list > > > > > but I noticed > > > > > > that a large number of JUnit test cases seem to be > > > failing. Some > > > > > > of the cases that are failing look they are > supposed to fail, > > > > > but I don't > > > > > > think they are failing for the correct reason. > > > > > > > > > > > > For example: > > > > > > > > > org.apache.woden.tests.wsdl20.W3CTestSuiteTest.testImportIB. The > > > > > > documentation in the WSDL says: > > > > > > > > > > > > This test shows an invalid use of an XML schema > import. The > > > > > > xs:import element MUST be a child of the wsdl:types > > > element. The > > > > > > references to the elements name:SIN and name:Name > > > will fail to > > > > > > resolve. > > > > > > > > > > > > But the Junit trace shows: > > > > > > > > > > > > junit.framework.AssertionFailedError: Unable to read > > > WSDL document > > > > > > because of WSDLException: faultCode=INVALID_WSDL: Fatal > > > WSDL error: > > > > > > 0:0,WSDL004,Expected a > > > "{http://www.w3.org/2005/08/wsdl}description"; > > > > > > element, but found a > > > "{http://www.w3.org/2006/01/wsdl}description"; > > > > > > element instead.,: > > > > > > > > > > > > All in all there are 26 cases that fail due to use of the > > > > > "2006/01" URI. > > > > > > Some of them (like > > > > > > > > > > > > > > > org.apache.woden.tests.wsdl20.W3CTestSuiteTest.testCreditCardFaults1 > > > > > G) > > > > > > don't look like they are supposed to fail at all. > > > > > > > > > > > > - gp > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > > > - > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
