Home » Eclipse Projects » Plugin Development Environment (PDE) » Rebuild complete workspace on change in MANIFEST
| Rebuild complete workspace on change in MANIFEST [message #56467] |
Thu, 16 April 2009 23:27  |
 Markward Schubert
Messages: 15
Registered: July 2009 |
Junior Member |
|
|
Hi!
Within the last weeks we experienced in our team, that developing our
project kept getting worse every day, because of the many delays we
suffer, when eclipse rebuilds the workspace.
We have a pretty complex situation to figure out, what actually is causing
the delays though. We use different plugins like Subclipse, SpringIDE and
Maven-integration (also for creating some plugin-projects), etc. But most
of them are in use since about a year without causing any trouble. The
other fact is, that our workspace has about 40 to 50+ projects now,
growing every week.
I now have been investigating the issue for some days without getting any
closer.
Is it possible, that with about 20 plugin-projects in the workspace it is
just "normal" to wait about 2 to 5 minutes to build the complete workspace
on every little change to a plugin-project's MANIFEST.MF? Even if the
change to be saved is simply an added or removed whitespace? I tried
several times and every time I save the MANIFEST, eclipse builds the
workspace and indeed compiles all the plugin-projects again.
Any help is very much appreciated.
Regards,
Mark
|
|
|
| Re: Rebuild complete workspace on change in MANIFEST [message #56800 is a reply to message #56467] |
Fri, 17 April 2009 19:42  |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
On 4/16/2009 7:27 PM, Markward Schubert wrote:
> Is it possible, that with about 20 plugin-projects in the workspace it
> is just "normal" to wait about 2 to 5 minutes to build the complete
> workspace on every little change to a plugin-project's MANIFEST.MF? Even
> if the change to be saved is simply an added or removed whitespace? I
> tried several times and every time I save the MANIFEST, eclipse builds
> the workspace and indeed compiles all the plugin-projects again.
Is it the case that the manifest begin edited is depended on by many, if
not all, of the other projects? The dependency could be direct or
indirect: for example you're editing PluginA, which is depended on by
PluginB which is, in turn, depended on by PluginC and PluginD. So
changing PluginA's manifest triggers a re-build of PluginB as well as
PluginC and PluginD.
Is that your case?
Eric
|
|
|
| Re: Rebuild complete workspace on change in MANIFEST [message #57093 is a reply to message #56800] |
Mon, 20 April 2009 09:49 |
Markward Schubert
Messages: 15
Registered: July 2009 |
Junior Member |
|
|
I made some experiments with some of our plugins an found out the following:
There are four plugins.
P-Callee
P-Caller1
P-Caller2
P-Caller3
P-Callee is called by P-Caller1, P-Caller2 and P-Caller3.
What I would expect is, that the Caller-1,2,3 plugins need a rebuild, as
their ability to call the Callee might have changed due to modifications in
P-Callee's MANIFEST, like a removed export statement for example.
In fact some other, more general plugins are also rebuilt, which are not
callers, but callees of P-Callee.
If one of these more general plugins is rebuilt, of course it triggers many
others with it.
Are there other aspects which influence the build-dependencies? Like
Extensionpoints or buddy-classloading?
"Eric Rizzo" <eclipse-news@rizzoweb.com> schrieb im Newsbeitrag
news:gsam00$icj$2@build.eclipse.org...
> On 4/16/2009 7:27 PM, Markward Schubert wrote:
>> Is it possible, that with about 20 plugin-projects in the workspace it
>> is just "normal" to wait about 2 to 5 minutes to build the complete
>> workspace on every little change to a plugin-project's MANIFEST.MF? Even
>> if the change to be saved is simply an added or removed whitespace? I
>> tried several times and every time I save the MANIFEST, eclipse builds
>> the workspace and indeed compiles all the plugin-projects again.
>
> Is it the case that the manifest begin edited is depended on by many, if
> not all, of the other projects? The dependency could be direct or
> indirect: for example you're editing PluginA, which is depended on by
> PluginB which is, in turn, depended on by PluginC and PluginD. So changing
> PluginA's manifest triggers a re-build of PluginB as well as PluginC and
> PluginD.
> Is that your case?
>
> Eric
|
|
| |
| Re: Rebuild complete workspace on change in MANIFEST [message #595889 is a reply to message #56800] |
Mon, 20 April 2009 09:49 |
Markward Schubert
Messages: 15
Registered: July 2009 |
Junior Member |
|
|
I made some experiments with some of our plugins an found out the following:
There are four plugins.
P-Callee
P-Caller1
P-Caller2
P-Caller3
P-Callee is called by P-Caller1, P-Caller2 and P-Caller3.
What I would expect is, that the Caller-1,2,3 plugins need a rebuild, as
their ability to call the Callee might have changed due to modifications in
P-Callee's MANIFEST, like a removed export statement for example.
In fact some other, more general plugins are also rebuilt, which are not
callers, but callees of P-Callee.
If one of these more general plugins is rebuilt, of course it triggers many
others with it.
Are there other aspects which influence the build-dependencies? Like
Extensionpoints or buddy-classloading?
"Eric Rizzo" <eclipse-news@rizzoweb.com> schrieb im Newsbeitrag
news:gsam00$icj$2@build.eclipse.org...
> On 4/16/2009 7:27 PM, Markward Schubert wrote:
>> Is it possible, that with about 20 plugin-projects in the workspace it
>> is just "normal" to wait about 2 to 5 minutes to build the complete
>> workspace on every little change to a plugin-project's MANIFEST.MF? Even
>> if the change to be saved is simply an added or removed whitespace? I
>> tried several times and every time I save the MANIFEST, eclipse builds
>> the workspace and indeed compiles all the plugin-projects again.
>
> Is it the case that the manifest begin edited is depended on by many, if
> not all, of the other projects? The dependency could be direct or
> indirect: for example you're editing PluginA, which is depended on by
> PluginB which is, in turn, depended on by PluginC and PluginD. So changing
> PluginA's manifest triggers a re-build of PluginB as well as PluginC and
> PluginD.
> Is that your case?
>
> Eric
|
|
|
Goto Forum:
Current Time: Thu Apr 25 19:56:48 GMT 2024
Powered by FUDForum. Page generated in 0.03038 seconds |
] 
Search
Help
Register
Login
Home
