[news.eclipse.platform.pde] Mixed workspace dependencies

[Roland Tepp <roland@xxxxxxxxxxxx>]

Hey,

I asked this question here before, but I guess, the question was poorly 
formulated as I got no answers, so I'll try it again...

I am wandering, what is the best practice of handling inter project 
dependencies where I have a set of plain old java projects and plug-in 
projects in the workspace and some of the plug-in projects depend on 
some of the "POJO projects".

At the moment we have a system where pojo projects have ANT build 
scripts that generate jar files that are then copied to their respective 
plug-ins. It worked fine for a while, but as the complexity of the 
project has grown, so has the overhead this process incurs.

It also seems a little heavy on the IDE side, as there are multiple 
variants of the same class floating around in the workspace and copying 
jar files around, also causes massive workspace rebuilds where much less 
could be achieved, where the dependencies much more declarative.

So the question I would like to pose is following: what would be the 
best way to organize this type of "java project" to "plug-in project" 
dependencies and have them built same way on the eclipse workspace and 
on CI server (for which we are currently using CruiseControl)