>
Eclipse allows you to use the GUI to specify library dependencies, or you can save time by editing an Eclipse file called.classpath. The.classpath file is in XML format. Sometimes when I make a minor change it tells me that my changes are "not valid XML". I can't for the life of me figure out why. They sure look valid to me.
Eclipse has the concept of "views", which are visual panels. There is a "package explorer" view, which you use to browse your Java packages. Eclipse seems have two different notions of directories: "Folders" and "Source Folders". I had problems because my main Java directory was defined as a "folder" instead of a "source folder". It's easy to change it to a "source folder" once you figure out what the problem is, but you don't get any kind of useful error message - it just doesn't work.
I use Eclipse for J2EE development, so I bought the MyEclipse plugin. It's only $30, but that's $30 PER YEAR. I was using JRE 1.4.1, but MyEclipse required 1.4.2 so I have to go get that and point Eclipse to it.
MyEclipse can handle JSP comments like but it can't seem to handle html comments like . Every time I use HTML comments, it appears that everything from that point down has an error. I can't imagine there could be such a major hole in the product, so I suspect that it's something about the way I have things configured. But what?
Also, all of the JSP includes are appearing as errors, and I'll be damned if I can figure out why.
It always seemed lame to me that MySQL users had to concern themselves with with "storage engine" gets used under the covers. The obvious answer from MySQL's perspective is to build their own storage engine as an integrated part of MySQL.
Slashdot Mirror
No problem... asshat. ;-)
> Eclipse allows you to use the GUI to specify library dependencies, or you can save time by editing an Eclipse file called .classpath. The .classpath file is in XML format. Sometimes when I make a minor change it tells me that my changes are "not valid XML". I can't for the life of me figure out why. They sure look valid to me.
Eclipse has the concept of "views", which are visual panels. There is a "package explorer" view, which you use to browse your Java packages. Eclipse seems have two different notions of directories: "Folders" and "Source Folders". I had problems because my main Java directory was defined as a "folder" instead of a "source folder". It's easy to change it to a "source folder" once you figure out what the problem is, but you don't get any kind of useful error message - it just doesn't work.
I use Eclipse for J2EE development, so I bought the MyEclipse plugin. It's only $30, but that's $30 PER YEAR. I was using JRE 1.4.1, but MyEclipse required 1.4.2 so I have to go get that and point Eclipse to it.
MyEclipse can handle JSP comments like but it can't seem to handle html comments like . Every time I use HTML comments, it appears that everything from that point down has an error. I can't imagine there could be such a major hole in the product, so I suspect that it's something about the way I have things configured. But what?
Also, all of the JSP includes are appearing as errors, and I'll be damned if I can figure out why.
It always seemed lame to me that MySQL users had to concern themselves with with "storage engine" gets used under the covers. The obvious answer from MySQL's perspective is to build their own storage engine as an integrated part of MySQL.