A few days ago I wrote about importing an EJB client project into Eclipse from Subversion. Unfortunately it’s not as easy as I thought. My goal was to import both the EJB project and the EJB client jar project and create an ear file from the two. While it’s possible to to check out both projects from Subversion getting them to work together in my workspace is not straight forward. With the client project checked out it is not possible to create an EJB client jar project via the Eclipse interface because a project with that name already exists. If I specify a different name during client jar creation then it’s a different client project associated with the EJB project than the one in Subversion. Since it’s not the one in Subversion then it’s not worth creating an EJB client jar from the Eclipse interface. On the other hand if I check out the EJB client project from Subversion then it’s not associated with the EJB project as a client jar. I’m not sure how else to proceed with attaining the desired outcome here. If anyone has any suggestions please let me know.  I have updated my wiki page on this as well.

This weekend I updated the javadoc comments in the IP address locator project. I also started a build.xml file to automate building the project outside of an Eclipse IDE. This is the first time I have used Ant’s manifest nested element of a jar element to create the manifest file inline. Since I only needed two lines in my manifest file creating it inline works great. At this point I would only change back to an external manifest file when I need it explicitly versioned in Subversion and/or when it becomes too large to manage in a build.xml file. The next tasks for my build.xml file are to put a JUnit tag in to run the unit tests and to run the javadoc tag before the jar file is created. In order to run JUnit from within Ant I have to create a classpath element that has the junit.jar file in it. Please download the IPAddressLocatorEAR.ear file and review my work. I’m always interested in questions and comments.

I wasted an incredible amount of time this weekend trying to get my Fedora Core 5 VMWare image to use NIS for account logins to no avail. The output of ypcat passwd.byname shows my database of users but when I su - to a different user I get “incorrect password” as the resposne. As root I can su - to a user listed in the NIS passwd file but not as my user account. I found a post staying that it might be because my user account was not part of the wheel group, but even after adding it the NIS login still doesn’t work. At this point I don’t care, especially since I can’t get those 4 hours of my life back. I’m glad I do most of my “experimental work” in VMWare images that have backups. I rm’d my /etc/passwd file ensuring that no users existed in the instance hoping it would be forced to go to the NIS server. What really happened was that I couldn’t sudo or log in as root to put the file back. The quick fix was blowing away that writable instance and replacing it with a backup taken last week. The funny thing is that hosts are picked up from the NIS server without a problem. Does anyone have some advice on how to get NIS remote logins to work?