Sample Eclipse classpath file

[asfimport]

tjsb (Bug 20555): It might be useful to have an Eclipse classpath file in CVS.

The file (to follow) has excludes for all the optional components such as JavaMail and SSL etc.

It is easier to use Eclipse to delete any unwanted excludes later, than to add new ones ...

It has the recent LDAP protocol additions, and all the libraries that are needed, as far as I can tell. Optional libraries (Mail etc) are not included.

[It will need updating from time to time when new libraries are released, etc]

I suggest it is stored as eclipse.classpath in the top level directory. [It should not be called .classpath]

Hope it proves useful.

OS: other

[asfimport]

tjsb (migrated from Bugzilla): Created attachment Eclipse.classpath: eclipse.classpath

Eclipse.classpath

```` ````

[asfimport]

Mike Stover (migrated from Bugzilla): I'm going to skip this for now - I'm not sure I really want my eclipse settings messed with like this.

[asfimport]

tjsb (migrated from Bugzilla): Sorry, my original posting was not clear: the idea was to store the file as "eclipse.classpath" not ".classpath".

As far as I can see, Eclipse takes any notice unless the file is called ".classpath", but if it does, it could be put into a subdirectory.

There is no requirement to use the file, but it is there if it is needed, as the project class is a bit tedious to set up correctly.

Even if the file is not copied to .classpath, it might be useful as a comparison base.

[asfimport]

tjsb (migrated from Bugzilla): I've discovered a feature in the Eclipse classpath I supplied - the images and resources files need to be excluded from the source, otherwise Eclipse copies them to the build directory, and they end up being present twice in the Jar - both with the same path name. Very confusing!

I'll post an amended version.

[asfimport]

tjsb (migrated from Bugzilla): Created attachment Eclipse2.classpath: Eclipse classpath with resource and image ignores

Eclipse2.classpath

```` ````