RE: [Vif-devel] Project in Eclipse

Dear Leena

The notation displayed on the SourceForge cvs is confusing insofar as the
SourceForge project name is vif (therefore the cvs path to /cvsroot/vif)
containing the project's code in the folders (= Eclipse projecs) VIF (for
the application), VIF Framework (for the application's framework), VIF Test
and VIF Framework Test (for the JUnit tests), vifapp (the Tomcat project,
i.e. the html- and xsl-files) and scripts (for the database scripts).
In the Eclipse workbench, therefore, I have five Java projects: VIF, VIF
Test, VIF Framework, VIF Framework Test and vifapp, and one additional
project for the scripts.

A note to the Eclipse workspace: It's a good idea to use a workspace
separate of your Eclipse installation. You can access this separate
workspace using the Eclipse -data runtime option. For example, you can start
Eclipse by submitting the following command:
C:\programs\eclipse\eclipse.exe -data "D:\Data\path\to\my\vif\workspace".

Having a VIF project in your workspace is ok. Instead of importing the
vif_source.jar I would suggest that you download the project structure
directly from the SourceForge CVS. You can do this using the Eclipse CVS
Repository perspective.
To access the CVS, add a new CVS Repository in the "CVS Repositories" tab
and provide the following information:
Host: cvs.sourceforge.net
Repository path: /cvsroot/vif
User: anonymous
Password: (none)

With this information you can connect to the projects CVS repository.
Change to the Java perspective and select Team -> Share project... A wizzard
starts guiding you through the next steps: (1) Use the repository location
you defined before, (2) Select an existing module, i.g. VIF, (3) Select HEAD
to get the code from, (4) click Finish. You're asked to commit changes now.
Click 'No' because you can't commit as Anonymous. After this step you'll
find nothing changed.
However, if you look at the 'Team' entry in the project's context menu, you
see that you have much more options now. In particular you're able now to
update your project, i.e. to load the code from the CVS repository. Select
the Update... action and you'll see how Eclipse loads the code from the CVS.
During the update step, Eclipse tries to compile the code. However, because
of missing ressources, it will fail most of the time. Therefore, after
you've checked out all the code in the 6 projects, you have to set the
references right for that Eclipse can compile.
You can configure the references in the project's properties -> Java Build
Path. You have to set the following references:
VIF (and VIF Framework Test) on VIF Framework, VIF Test on VIF.
In addition, you have to reference External JARs, i.e. javax.servlet,
javax.mail etc.
You can use the jar files in vifapp\WEB-INF\lib.

Please contact me if you have further questions,
Benno

> -----Original Message-----
> From: vif...@li...
> [mailto:vif...@li...]On Behalf Of Leena
> Kulkarni
> Sent: Montag, 11. Oktober 2004 12:47
> To: vif...@li...
> Subject: [Vif-devel] Project in Eclipse
>
>
> Hello Benno,
>
> Till now I found Eclipse much on the similar lines of
> WSAD(Websphere Studio Application Developer). Im going
> through the docs quickly so as to spend less time on
> interacting with you for small things here and there
> about the IDE. Also, I had worked on a machine of an
> ex-employee where the IDE and the project and paths
> etc all setup was already there.
>
> I have created a project called VIF in the workspace.
> And have added the source files under the VIF
> workspace through 'Import' on the vif_source.jar.
>
> After that when I tried to 'Import' the
> viffw_source.jar and it asked me for overwriting.
>
> I cancelled it. And checked the structure in the 'VIF
> CVS' on the site.
>
> I have workspace/Vif/METAINF and workspace/Vif/org
> kind of structure right now.
>
> In the CVS it is like - 'workspace/Vif/Vif/METAINF'
> and 'workspace/Vif/Vif/org'. And then
> 'workspace/Vif/Vif Framework'. We have a folder VIF
> which in turn contains the main source files, the
> framework related source files and so on..
> So that workspace remains one for all these source
> files.
>
>
> So I should be creating a folder VIF under the vif
> workspace and import the jars in the folder. Pls
> confirm this.
>
> Regards,
> Leena
>
>
>
> _______________________________
> Do you Yahoo!?
> Declare Yourself - Register online to vote today!
> http://vote.yahoo.com
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on
> ITManagersJournal
> Use IT products in your business? Tell us what you think of
> them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Vif-devel mailing list
> Vif...@li...
> https://lists.sourceforge.net/lists/listinfo/vif-devel