Thanks Damian. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Krzeminski, Damian (BL60:9D30) Sent: Thursday, October 15, 2009 12:03 PM To: [email protected] Subject: Re: [sipX-dev] .project and .classpath file for sipviewer - Try 2
Thomas Suchecki wrote: > Hello again, > > I was using MS Outlook and accidently sent the email below on the > wrong thread. So am resending as a new original thread. > > Also adding some clarification below. > > Tom > > -----Original Message----- > From: [email protected] > [_mailto:[email protected]_] On Behalf Of Suchecki, > Thomas (CAR:9D80) > > Sent: Wednesday, October 14, 2009 2:36 PM > To: [email protected] > Subject: [sipX-dev] .project and .classpath file for sipviewer > > Hello, > > I'm working on some sipviewer improvement issues and one thing that > came up was the Eclipse design environment for this component. I got > it compiling and liking in Eclipse just fine but because of the way > packaging in Java works and how Eclipse works the .project and > .classpath files are located in /main/sipXtools/src/sipviewer/src. > Also importing the project user should do it from the > /main/sipXtools/src/sipviewer/src directory for it to be imported properly. > > Question: In the root /main/sipXtools directory there are already > pre-xisting .project and .classpath files. Importing the whole > /main/sipXtools dir uses these files. When imported Eclipse Project > explorer shows all the directories housed by sipXtools. However > selecting the sipviewer subdir in Eclipse Project explorer and trying > to run it only shows python run options. I attempted to add the Java > Application run configuration for sipviewer directory only in the > Eclipse Project explorer but it did not work. Not sure if I'm doing > something wrong here. My question is, is the intention to have one > .project and .classpath file for each component (eg. sipXtools, > sipXconfig, ...) and for these two files to be sitting in the these "root" > directories. If so does anyone know how to configure Eclipse for this > type of setup (in the case of sipXtools, if I import from the > /main/sipXtools directory how can I compile sipviewer or configure it > so that it compiles)? If this is not the convention the I would like > to submit my .project and .classpath files for sipviewer in the > /main/sipXtools/src/sipviewer/src. > > Thoughts? > Last time I checked Eclipse could not deal well with nested project. I would think that if sipXtools is a collection of projects (sometimes written in different languages) each one of them should have a separate Eclipse project: for example in sipXconfig agent, neoconf, gwt, web and each plug-in have separate projects. Most likely similar things needs to be done in sipXtools. You should be able to just close current sipXtools project in Eclipse and configure a new one in sipviewer directory. D. Try closing sipXtools project and creating a new one just for sipXviewer. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
