M
Matt Baker
Guest
The builder (any builder really) in Eclipse is single threaded. Workspace resources (files on disk) can be read, but not modified outside the thread that owns the workspace lock while the builder is running. But what can happen is that a class can get compiled to multiple locations in PDSOE. This has been talked about before, and the multi-compile option doesn't address it. The parent class writing can become a problem if you have multiple PDSOE projects, each with their own compile destination directory. When a class in one project (project a), references a class in another project (project b), any referenced classes get compiled twice. Once by the builder for where the class "lives", and once by the builder where it is referenced. This leads to cases where a class is compiled twice to different locations. The one that "wins" at runtime is totally based on PROPATH setting. Your suggestion dbeavon to request that the compiler only write out exactly what was referenced could assist with this scenario. And it is not just the parent class. Any class referenced that isn't compiled, will get written out.
Continue reading...
Continue reading...