I just made the mistake of performing a svn update in the
apacheds/trunk folder and discovered the structure changes that were
I know that Emmanuel is on vacation, but when you get back I would be very interested in update .project and .classpath files for this part of the source tree. I took a quick stab at performing this task myself, but being new to the project I immediately got lost on the interdependencies, so I ended up reverting to a revision before those changes were put into place :-)
I am not sure I tried that target, there was another eclipse maven target that generated .project and .classpath files, but they were very base and did not have the classpath entries based on the maven repository jars. I am actually intrigued by Emmanuel's .classpath and .project that he sent me since he has a .project and .classpath for all of the sub-projects within apacheds for instance.
Anyway, I appreciate the amount of support that is already present in the build environment for Eclipse, hopefully it can be kept up-to-date with newer versions of jars.
-Lyndon-On 11/1/05, Trustin Lee < firstname.lastname@example.org> wrote:Hi Lyndon,2005/11/2, Lyndon Washington <email@example.com >:--I have referred to the great notes on the wiki @ http://wiki.apache.org/directory/IdeHome for setting up the Eclipse environment to build the various pieces. I was wondering if someone had an up-to-date .classpath and .project file that incorporated the latest jars from the maven registry/repository.
I thought I modified maven.properties so that anyone can generate Eclipse project file by running 'maven eclipse:eclipse'. Was there any problem?
what we call human nature is actually human habit