- This topic has 11 replies, 7 voices, and was last updated 18 years, 11 months ago by
.
-
Posts
-
Quite often you end up with temp / doc / scratch dirs where you really don’t need the otherwise useful Structured Document Model Builder to moan at you…
➡ So, it’d be nice to ‘include/exclude’ folders for such builds
I believe we are focusing on offering “filtering” of certain files to not go through validation, so this should provide the functionality you need.
Yes, but I am not sure if just filtering of files is sufficient for us. I would like to exclude directories as well. My build tree structure includes build and dist directories that are created by an Ant script. When I refresh my project in MyEclipse, it sees those directories and indicates problems for some of the JSP files in there. I am not sure why it is even looking in those folders at all. Shouldn’t it ignore JSP files that are outside of the WebRoot directory? Anyway, I can filter those directories so they don’t show up in the Package Explorer, but my project still shows an error indicator because MyEclipse is still looking in them.
canthes, the “not ignoring files outside of webroot” actually has its roots set in the fact that we support full JSP development in plain Java Projects (well mostly full development, even though its a royal PIA to support it)… so we just don’t “stupid the editor up” in Web Projects, so it still pays attention to everything. We are aware of this annoyance and should correct it soon.
Is it possible to give an indication of when this ‘annoyance’ might be fixed? I am currently suffering from it for exactly the same reason – using Ant with various build, delivery etc directories
You know it would be nice if the webroot was treated like a java source folder, then in the project properties you can take advantage of the source included/excluded filters as well as specifying your output directory (e.g. doesn’t have to be WEB-INF/classes). (The beauty of this is no exceptional case in how it is treated in eclipse – the only difference is .jsp is substitued for .java)
For instance one problem we have is we use subversion as our VCS and the .svn folders and files get copied over as resources into WEB-INF/classes and just like others have mentioned in this thread you get myeclipse validating and processing all those files and moaning about them.
files as ant byproducts is also a problem for us as well. So filters would be good, but it would be even better if it matched eclipse ways of doing things.
Cheers,
EricEric,
First thank you for the feedback and suggestion, but I have some comments/questions:1) Output dir is by default WEB-INF/classes, you can change it to whatever you want in your Java Build Path properites for your project.
2) The copying of the .svn folders into the output dir is handled by the Eclispe build mechanism, not MyEclispe. The only part of building that is MyEclipse is the JSP compilation, and XML-file validation.Any update on this?
I have a ‘target’ (or build) directory that i basically have ant build and copy all files to. Some of these files have missing dependencies, etc or
missing dtds (becaues i don’t want to distdistribute them with my app).I don’t want eclipse (or myeclipse) to even look at anything under the ‘target’ directory. But right now i’m getting things listed in my problems tab because of that stuff (and it drives me nuts to see it there).
thanks,
kenNo update as of yet, but we are aware of this… its a symptom of a bigger problem that will not be a small change. We are looking at adding filtering based on worksets to work around this for the time being, but no ETA yet.
It has been more than a year since this thread was last updated. Is there any news about excluding build directories from the validation path? I’ve been looking for it in version 4.0.3 and it doesn’t look like it’s there.
Thanks!
DaveDave,
Work never stops around here, neither do requests. Unfortunately there has not been a huge demand for this, so in light of all the new designers, RAD tool, enhanced editors, and features going into MyEclipse we have not worked on this. Although last week we did refine what is needed for this feature specifically and have filed it and it will be researched for 4.1.1, although there is not a hard and fast commitment yet from management.
