Nadav, Thanks for the info! I think I tried mvn eclipse:eclipse, but maybe I misinterpreted the output. There were some exclusions that didn't make sense to me in the resulting .classpath file. I'll give it another try. I like a clean pom.xml file! Sounds like you have everything well organized for maven.
mike Mike Rheinheimer (512) 838-0086 t/l 678-0086 WebSphere WebService Core Engine Team |------------> | From: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |"Fischer, Nadav" <[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | To: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |"[email protected]" <[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Date: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |06/11/2009 12:37 AM | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Subject: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |FW: [Wink] eclipse .classpath for Symphony | >--------------------------------------------------------------------------------------------------------------------------------------------------| Hi, Maven has a great plugin for automatically creating eclipse projects from all the pom.xml files, with dependencies between the generated projects. To create eclipse projects for Symphony, run "mvn eclipse:eclipse" from the root of the HP_REST_SDK folder (you first have to build Symphony by running "mvn install"). Maven will download the eclipse plugin and generate a .classpath and .project files for all the runtime modules and example modules in Symphony. Now all you have to do is import the projects to eclipse (File->Import...->Existing Projects into Workspace). You should be able to import all of the projects in one go by selecting the HP_REST_SDK root folder. Before you import the projects, you should: 1. Create a classpath variable named M2_REPO that points to the maven repository (instead of the HP_REPO variable mentioned below) 2. Enable use of exclusion patterns in source folders (Preferences-> Java->Compiler->Building->General->check the checkbox) One last thing - the WebDAV example depends on the QADefect example, but for some reason the maven eclipse plugin doesn't set the WebDAV example project to depend on the QADefect example project, so there are errors after importing into eclipse. You have to manually set the WebDAV example project to depend on the QADefect example to fix this (Project-> Properties->Java Build Path->Projects tab) Thanks, Nadav From: Michael Rheinheimer [mailto:[email protected]] Sent: Wednesday, June 10, 2009 19:01 To: [email protected] Subject: Re: [Wink] eclipse .classpath for Symphony Oops, should have known attachments would be filtered out. So instead I've opened a Jira and attached the file there to share it: https://issues.apache.org/jira/browse/WINK-3 Thanks.. mike [cid:[email protected]]Michael Rheinheimer---06/10/2009 09:28:05 AM---Hi team, Some folks here at IBM were asking about getting Symphony set up in Eclipse. I took a pass From: Michael Rheinheimer/Austin/IBM To: [email protected] Date: 06/10/2009 09:28 AM Subject: [Wink] eclipse .classpath for Symphony ________________________________ Hi team, Some folks here at IBM were asking about getting Symphony set up in Eclipse. I took a pass at creating a .classpath for the project, and got it as good as it'll get. Some of the classes in some of the samples source directories overlap, so you'll see "class already defined" compile errors in the Eclipse UI, but that's ok. You can browse around now in the Eclipse IDE. See attached .classpath. I configured an environment variable like so: Window -> Preferences -> Java -> Build Path -> Classpath Variables -> New -> (Name: HP_REPO, Folder: <path to your maven repository root>) You can unzip the HP_REST_SDK.zip into your Eclipse workspace, copy the attached .classpath into your HP_REST_SDK folder, and create new project: File -> New -> Java Project -> (type in HP_REST_SDK and you'll see that Eclipse panel switch over to say "The wizard will automatically configure the jre...") [attachment ".classpath" deleted by Michael Rheinheimer/Austin/IBM] Let me know if you have any questions. mike Mike Rheinheimer (512) 838-0086 t/l 678-0086 WebSphere WebService Core Engine Team
