- This topic has 12 replies, 2 voices, and was last updated 18 years, 7 months ago by
.
-
Posts
-
When MyEclipse is building the web application, it takes quite a while. When I check the progress, it seems to be building files that are outside of my build path. Is there a way I can configure it to ignore files outside my build path?
Thanks,
KyKy,
Can you be more specific? MyEclipse will build everything under the webroot and in your build path, do you have JSPs elsewhere in the project that are getting built that you want ignored? If you do, right click on the dir, go to properties, and mark it as dervied. That should help.The problem is with the Document and Model Builder.
It was taking a long time at the “Invoking Structured Document and Model Builder” step of the build. After It marked some directories as Derived, that step seemed to be quicker. This could just be because of some caching such that the second time is faster.
During the “Structured Document and Model Builder building <file>” step, it seems to be building the xml, html, css, jsp, etc. files from some directories outside my build path (e.g. third_party, build output from Ant, etc.). Marking the directories as Derived did NOT help. I marked the top level directory, down to the direct parent directories containing the xml that should be ignored, but it still didn’t help. It seems to skip directories that were explicitly excluded from my build path, but not some others that were not explicitly excluded.
Any other ideas?
KyActually, now it doesn’t seem like marking the directories and derived helped speed up the initial “Invoking Structured Docmument and Model Builder” step. I also tried to add the some directories in my build path so that I could explicitly exclude them. That did not help either. How is the Document and Model Builder is choosing the directories to build? Can I control it somehow?
Ky
Can you copy paste the result of MyEclipse > About > COnfiguration SUmmary for me? I wonder if this is a bug that was fixed in a later release.
Here’s the configuration summary:
*** Date: Mon Apr 10 11:20:44 PDT 2006
*** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_06*** MyEclipse details:
MyEclipse Enterprise WorkbenchVersion: 4.1.0 GA
Build id: 20060122-4.1-GA*** Eclipse details:
Eclipse SDKVersion: 3.1.2
Build id: M20060118-1600Eclipse Platform
Version: 3.1.2
Build id: M20060118-1600Eclipse RCP
Version: 3.1.2
Build id: M20060118-1600Eclipse Java Development Tools
Version: 3.1.2
Build id: M20060118-1600Eclipse Plug-in Development Environment
Version: 3.1.2
Build id: M20060118-1600Eclipse Project SDK
Version: 3.1.2
Build id: M20060118-1600Eclipse startup command=-data
D:\Documents and Settings\kvong\vf3_workspace
-os
win32
-ws
win32
-arch
x86
-launcher
D:\eclipse3.1.2\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
ba0_64
-vm
C:\WINNT\system32\javaw.exeCan you try and upgrade to MyEclipse 4.1.1 (use the update manager) then restart using the -clean command line argument? I’m not sure why the builders/validators are ignoring the derived setting.
I upgraded to 4.1.1 and it’s still building the unwanted files. Would the derived setting be affected by the fact that my project is on a networked drive?
Ky
Would the derived setting be affected by the fact that my project is on a networked drive?
Oh wow, no it shouldn’t be, but if your directory and especially your workspace is on a networked drive your build times are going to be unbearable. I would strongly encourage you to simply put your work under source control and get it onto your local drive.
It is actually because of the source control that I have my project directory is on a networked drive, don’t ask me why. I have a gigabit ethernet connection and the filer is quite fast, so performance is not so bad. My workspace is on a local disk however.
I created a new workspace, created a new project, and the problem is not there. I’m not sure what the difference is though. If I find the difference, I’ll let you know.
Ky
Ok I was more worried your workspace was on the network drive, given how much little file activity there is during builds in the workspace that can really be a nightmare.
Just to follow up and clarify. I still had to mark the directories as Derived to get MyEclipse to not build them, but at least that worked. I encountered the problem again, but after I had added the Web Capabilities, removed the Web Capabilities, and then added it back again. When I did that, the Derived settings were ignored. I re-created the project and the Derived setting worked again.
Ky
