Yesterday I spent a little time setting up Classpath as a project in Eclipse. After some tweaking, I was able to come up with the appended patch. This just adds a couple files that enable Classpath as an Eclipse project.
If you try this out, you will have to make a "Configuration.java" by hand. I did this by copying Configuration.java.in and editing the result to be valid Java source. It is probably possible to teach Eclipse to run autogen.sh and configure, but I haven't tried this. I'd like to check this in but thought I'd first see if anybody has strong objections to it. mjw was down on the idea on irc, but I'm hoping that was just lack of food :-). Tom Index: .classpath =================================================================== RCS file: .classpath diff -N .classpath --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ .classpath 22 Apr 2004 04:49:30 -0000 @@ -0,0 +1,9 @@ +<?xml version="1.0" encoding="UTF-8"?> +<classpath> + <classpathentry + excluding="external/jaxp/source/|vm/reference/|compat/|test/|external/jaxp/tests/|testsuite/|**/Test.java|**/TestAWT.java|gnu/javax/swing/|**/SliderTest.java" + kind="src" path=""/> + <classpathentry kind="src" path="external/jaxp/source"/> + <classpathentry kind="src" path="vm/reference"/> + <classpathentry kind="output" path="bin"/> +</classpath> Index: .project =================================================================== RCS file: .project diff -N .project --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ .project 22 Apr 2004 04:49:30 -0000 @@ -0,0 +1,17 @@ +<?xml version="1.0" encoding="UTF-8"?> +<projectDescription> + <name>classpath</name> + <comment></comment> + <projects> + </projects> + <buildSpec> + <buildCommand> + <name>org.eclipse.jdt.core.javabuilder</name> + <arguments> + </arguments> + </buildCommand> + </buildSpec> + <natures> + <nature>org.eclipse.jdt.core.javanature</nature> + </natures> +</projectDescription> _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
